Dominik Wilkowski
@dominik-wilkowski.com
CTO The Working Party, Ex Eng lead of Polaris Design System at Shopify.
Tabs indenter, light mode user.
Likes to wear a suit when it’s inappropriate to wear a suit, organizer of Design System Meetup 🇦🇺 Australia, Code Heart Design conf, he/him
Tabs indenter, light mode user.
Likes to wear a suit when it’s inappropriate to wear a suit, organizer of Design System Meetup 🇦🇺 Australia, Code Heart Design conf, he/him
Are there good examples of community standards for a rust community that specifically addresses the all-too-common talking-down to C and other languages?
I heard @steveklabnik.com talk about how the early rust community used to be very good about this on one of the oxide and friends episodes.
I heard @steveklabnik.com talk about how the early rust community used to be very good about this on one of the oxide and friends episodes.
October 20, 2025 at 3:31 AM
Are there good examples of community standards for a rust community that specifically addresses the all-too-common talking-down to C and other languages?
I heard @steveklabnik.com talk about how the early rust community used to be very good about this on one of the oxide and friends episodes.
I heard @steveklabnik.com talk about how the early rust community used to be very good about this on one of the oxide and friends episodes.
October 18, 2025 at 10:15 PM
We, at The Working Party, just released a package to parse the doc blocks. We use this package to automatically generate documentation and test our files to make sure every snippet and block has those blocks for type safety and auto completion in the editor #shopify #rust
github.com/the-working-...
github.com/the-working-...
GitHub - the-working-party/liquid-docs: A parser for Shopify liquid doc tags.
A parser for Shopify liquid doc tags. Contribute to the-working-party/liquid-docs development by creating an account on GitHub.
github.com
August 21, 2025 at 7:14 PM
We, at The Working Party, just released a package to parse the doc blocks. We use this package to automatically generate documentation and test our files to make sure every snippet and block has those blocks for type safety and auto completion in the editor #shopify #rust
github.com/the-working-...
github.com/the-working-...
Hey folks. Looking for an awesome front end dev for the Shopify ecosystem in Australia or New Zealand for full time employment. We have a bunch of things cooking and would love to hear from you.
www.linkedin.com/jobs/view/42...
www.linkedin.com/jobs/view/42...
The Working Party — Shopify Platinum Partner agency hiring Senior Frontend Developer in Australia and New Zealand | LinkedIn
Posted 10:13:39 AM. Are you a Senior Front-End Developer looking to work on complex and interesting projects for high…See this and similar jobs on LinkedIn.
www.linkedin.com
July 16, 2025 at 12:17 AM
Hey folks. Looking for an awesome front end dev for the Shopify ecosystem in Australia or New Zealand for full time employment. We have a bunch of things cooking and would love to hear from you.
www.linkedin.com/jobs/view/42...
www.linkedin.com/jobs/view/42...
I’ve written up a tutorial I’ve given to a couple friends and colleges #teaching them #Rust and it’s been a lot of fun.
It’s 4 parts and starts here:
dominik-wilkowski.com/posts/learni...
It’s 4 parts and starts here:
dominik-wilkowski.com/posts/learni...
Learning Rust By Building The Old Terminal Game Beast From 1984, Part 1
We are building the terminal game BEAST together to learn to apply Rust to a project. This is the first part in which we setup our board and learn how to move our player.
dominik-wilkowski.com
July 7, 2025 at 7:40 AM
I’ve written up a tutorial I’ve given to a couple friends and colleges #teaching them #Rust and it’s been a lot of fun.
It’s 4 parts and starts here:
dominik-wilkowski.com/posts/learni...
It’s 4 parts and starts here:
dominik-wilkowski.com/posts/learni...
Reposted by Dominik Wilkowski
📝 First blog in a long time!
I always like “flow-based” programming, and it’s a very powerful paradigm. LangGraph lets you codify complex workflows as graphs, and also integrates really well with LangChain, if your workflow is LLM-driven.
surma.dev/things/langg...
I always like “flow-based” programming, and it’s a very powerful paradigm. LangGraph lets you codify complex workflows as graphs, and also integrates really well with LangChain, if your workflow is LLM-driven.
surma.dev/things/langg...
LangGraph for complex workflows — surma.dev
I may be late to the party, but LangGraph lets you build complex workflow architectures and codify them as powerful automations. Also LLMs, if you want. But you don’t have to!
surma.dev
June 17, 2025 at 4:19 PM
📝 First blog in a long time!
I always like “flow-based” programming, and it’s a very powerful paradigm. LangGraph lets you codify complex workflows as graphs, and also integrates really well with LangChain, if your workflow is LLM-driven.
surma.dev/things/langg...
I always like “flow-based” programming, and it’s a very powerful paradigm. LangGraph lets you codify complex workflows as graphs, and also integrates really well with LangChain, if your workflow is LLM-driven.
surma.dev/things/langg...
Reposted by Dominik Wilkowski
🌈 Ever wanted to get the accessible color contrast from a given color using only CSS? Well, here's how:
blog.damato.design/posts/css-on...
blog.damato.design/posts/css-on...
CSS Only Contrast
We've always wanted it, now it looks like we can have it.
blog.damato.design
June 4, 2025 at 5:18 PM
🌈 Ever wanted to get the accessible color contrast from a given color using only CSS? Well, here's how:
blog.damato.design/posts/css-on...
blog.damato.design/posts/css-on...
Reposted by Dominik Wilkowski
After 20 years of writing code and 10 years trying to quit, I did the only logical thing:
I built a website to rant about it.
Introducing SegfaultAndCoffee.com — a collection of sarcastic rants, emotional tech debt, and the kind of Rust-powered existential dread you can’t cargo fix.
I built a website to rant about it.
Introducing SegfaultAndCoffee.com — a collection of sarcastic rants, emotional tech debt, and the kind of Rust-powered existential dread you can’t cargo fix.
May 16, 2025 at 11:55 PM
After 20 years of writing code and 10 years trying to quit, I did the only logical thing:
I built a website to rant about it.
Introducing SegfaultAndCoffee.com — a collection of sarcastic rants, emotional tech debt, and the kind of Rust-powered existential dread you can’t cargo fix.
I built a website to rant about it.
Introducing SegfaultAndCoffee.com — a collection of sarcastic rants, emotional tech debt, and the kind of Rust-powered existential dread you can’t cargo fix.
Reposted by Dominik Wilkowski
Fastest way to check if a year is a leap year?
hueffner.de/falk/blog/a-...
Best part:
"I couldn't immediately find a way to prove it, so I employed the tried-and-true method of getting someone else to do it for me by posting it to the Code Golf StackExchange."
hueffner.de/falk/blog/a-...
Best part:
"I couldn't immediately find a way to prove it, so I employed the tried-and-true method of getting someone else to do it for me by posting it to the Code Golf StackExchange."
May 16, 2025 at 9:52 AM
Fastest way to check if a year is a leap year?
hueffner.de/falk/blog/a-...
Best part:
"I couldn't immediately find a way to prove it, so I employed the tried-and-true method of getting someone else to do it for me by posting it to the Code Golf StackExchange."
hueffner.de/falk/blog/a-...
Best part:
"I couldn't immediately find a way to prove it, so I employed the tried-and-true method of getting someone else to do it for me by posting it to the Code Golf StackExchange."
Reposted by Dominik Wilkowski
Fun fact \\#2137: the Rust compiler recognizes git diff markers
May 13, 2025 at 5:13 PM
Fun fact \\#2137: the Rust compiler recognizes git diff markers
Great article.
> Further, I advocate for Rust developers to document and share their mistakes in the hope that we can all learn from them.
Couldn’t agree more.
> Further, I advocate for Rust developers to document and share their mistakes in the hope that we can all learn from them.
Couldn’t agree more.
To better understand what makes a good #rust type, I'm exploring what makes a "bad type" with the first in my series "The Duplicate Duck."
LMK what you think and if you have any other type anti-patterns I should watch out for.
www.schneems.com/2025/05/07/b...
LMK what you think and if you have any other type anti-patterns I should watch out for.
www.schneems.com/2025/05/07/b...
Bad Type Patterns - The Duplicate duck
Why aren’t people writing more types? Perhaps it’s because the intermediate and expert developers deleted the patterns that didn’t work and left no trace for...
www.schneems.com
May 8, 2025 at 10:44 PM
Great article.
> Further, I advocate for Rust developers to document and share their mistakes in the hope that we can all learn from them.
Couldn’t agree more.
> Further, I advocate for Rust developers to document and share their mistakes in the hope that we can all learn from them.
Couldn’t agree more.
This article speaks deeply to what I think the right way is you build a “high performing team/company”. This is how you do it.
Our compensation model at @oxide.computer was a very hot topic when we first posted about it over four years ago. But now years later (and a tripling in size!), how is it going? An overdue update: oxide.computer/blog/oxides-...
Oxide’s Compensation Model: How is it Going? / Oxide
Reflecting on how our compensation model is going
oxide.computer
May 1, 2025 at 10:33 PM
This article speaks deeply to what I think the right way is you build a “high performing team/company”. This is how you do it.
I feel seen
The Rust compiler and I make a great team with a common enemy: my code.
April 30, 2025 at 9:23 AM
I feel seen
Just published BEAST. A recreation of a game I grew up with from 1984. I tried to keep it as close to the original as practical. There is a global Highscore server now too which is cool. Was a lot of fun to write this in #rust and playing it.
github.com/dominikwilko...
github.com/dominikwilko...
GitHub - dominikwilkowski/beast: An ASCII game built in rust in loving memory of the 1984 hit BEAST
An ASCII game built in rust in loving memory of the 1984 hit BEAST - dominikwilkowski/beast
github.com
April 29, 2025 at 8:13 PM
Just published BEAST. A recreation of a game I grew up with from 1984. I tried to keep it as close to the original as practical. There is a global Highscore server now too which is cool. Was a lot of fun to write this in #rust and playing it.
github.com/dominikwilko...
github.com/dominikwilko...
Fantastic post and a novel approach to something seemingly unrelated. #rust
yo, i think i've accidentally discovered something new - pwy.io/posts/marchi...
Marching Events: What does iCalendar have to do with ray marching?
pwy.io
April 17, 2025 at 4:50 AM
Fantastic post and a novel approach to something seemingly unrelated. #rust
I’m writing the pathfinding for my 2D #CLI #rust game and in there you can move multiple blocks so I added a comment:
// there is a chain of blocks (a blockchain) that can be pushed to squish the player
I think I’m pretty funny. But I just asked Claude to review my code and it came up with this.
// there is a chain of blocks (a blockchain) that can be pushed to squish the player
I think I’m pretty funny. But I just asked Claude to review my code and it came up with this.
April 16, 2025 at 8:39 AM
Reposted by Dominik Wilkowski
April 10, 2025 at 9:11 PM
Folks I’m hiring a principle eng at my company. Web stuff is important and we do a lot of #Shopify stuff but I would LOVE someone with an interest in #rust (either you’re already building it or have an interest in learning it) in Australia or New Zealand.
The work is super exciting.
DMs are open
The work is super exciting.
DMs are open
February 23, 2025 at 11:33 PM
I really like the default compiler output of VI vine.dev/docs/startin...
Anyone know if there is something like this for #rust? A cargo plugin that shows you interactions (clone, copy, other trait calls) and the memory footprint (heap, stack size)
Anyone know if there is something like this for #rust? A cargo plugin that shows you interactions (clone, copy, other trait calls) and the memory footprint (heap, stack size)
Hello, world! - The Vine Programming Language
vine.dev
February 23, 2025 at 7:26 PM
I really like the default compiler output of VI vine.dev/docs/startin...
Anyone know if there is something like this for #rust? A cargo plugin that shows you interactions (clone, copy, other trait calls) and the memory footprint (heap, stack size)
Anyone know if there is something like this for #rust? A cargo plugin that shows you interactions (clone, copy, other trait calls) and the memory footprint (heap, stack size)
The 90s were a golden age for efficient binaries—hardware constraints forced developers to optimize. Now, we ship layers of abstractions on top of each other.
Lately, I find myself wanting a self-imposed performance limiter, just to build leaner, more efficient software. Even for desktop apps.
Lately, I find myself wanting a self-imposed performance limiter, just to build leaner, more efficient software. Even for desktop apps.
February 14, 2025 at 12:07 PM
The 90s were a golden age for efficient binaries—hardware constraints forced developers to optimize. Now, we ship layers of abstractions on top of each other.
Lately, I find myself wanting a self-imposed performance limiter, just to build leaner, more efficient software. Even for desktop apps.
Lately, I find myself wanting a self-imposed performance limiter, just to build leaner, more efficient software. Even for desktop apps.
Reposted by Dominik Wilkowski
This is an interesting read about the Fish shell team's experience porting fish from C++ to Rust. There's some good, some bad, but an improvement in the end.
It's also interesting to see them highlight using Rust will (hopefully) encourage more contributors
fishshell.com/blog/rustport/
It's also interesting to see them highlight using Rust will (hopefully) encourage more contributors
fishshell.com/blog/rustport/
Fish 4.0: The Fish Of Theseus
A smart and user-friendly command line shell
fishshell.com
February 14, 2025 at 8:27 AM
This is an interesting read about the Fish shell team's experience porting fish from C++ to Rust. There's some good, some bad, but an improvement in the end.
It's also interesting to see them highlight using Rust will (hopefully) encourage more contributors
fishshell.com/blog/rustport/
It's also interesting to see them highlight using Rust will (hopefully) encourage more contributors
fishshell.com/blog/rustport/
February 1, 2025 at 1:56 AM