A prototype should answer one question
The fastest prototypes are narrow, disposable, and built around the risky part of an idea.
Thoughts on design, development, and building products.
The fastest prototypes are narrow, disposable, and built around the risky part of an idea.
A practical look at how AI tools changed my daily workflow as a design engineer, and why the results surprised me.
Why thinking in both design and code produces better products than either discipline alone.
Lessons from founding multiple products, the mistakes I keep making, and the few things I've actually figured out.
The fastest prototypes are narrow, disposable, and built around the risky part of an idea.
A product feels calmer when the first state already reflects a reasonable decision.
A practical look at how AI tools changed my daily workflow as a design engineer, and why the results surprised me.
Why thinking in both design and code produces better products than either discipline alone.
Lessons from founding multiple products, the mistakes I keep making, and the few things I've actually figured out.
The patterns I've noticed in projects that actually make it to production versus the ones that collect dust.
How I approach component design and consistency without over-engineering a system nobody asked for.
Sharing what I'm working on before it's ready turned out to be the best career decision I've made.
Technical skills can be learned from documentation. Knowing what feels right takes years of paying attention.
The strategies that work at zero don't work at scale, and the ones that work at scale don't work at zero.
After years of remote work, I've found that most meetings could be a message, and the work is better for it.