Hello, world

The biggest perspective shift I've had over the last few years: velocity is everything. It's so tempting as an engineer to build for scale with clean abstractions, layers that anticipate every future need, an architecture you'd be proud to whiteboard. I spent a lot of my career chasing that. And the more I've shipped, the more I've moved away from it.

At this point I'm convinced: building to scale is the wrong north star for any engineer, at any company, at any size. The actual goal is building something users love. And figuring out what users love is a discovery process — nobody nails it on the first try.

But if you're listening and iterating quickly, the patterns show up fast. This holds at every stage. 0-to-1 startups, public companies with thousands of engineers, doesn't matter.

Does this mean nobody should care about clean code, DX, or scalable architecture? That we should ship everything and let the tech debt pile up? That every codebase should be unreadable garbage? Obviously not.

But these things only deserve focus once they start slowing you down or hurting the user experience. Working on them before that point is pointless.

Speed of learning beats perfection. Build fast, learn fast, iterate fast. The rest is ego.

If you want to be nudged when I publish, grab me on LinkedIn — the "Ask me anything" button in the corner also works.