I'm the one asking "why" in the meeting
Before the ticket, before the stack, I want to understand who's on the other side of the screen and what's getting in their way. Most bugs start as misunderstandings.
I care about the part most people skip: understanding who's going to use what I build, and why. Then I move fast, with a first version that works in real hands, early, and I build it clean enough to change and solid enough to grow. AI makes me faster; the decisions are still mine. And I'm still learning, out loud, one project at a time.
Before the ticket, before the stack, I want to understand who's on the other side of the screen and what's getting in their way. Most bugs start as misunderstandings.
Interfaces people enjoy, APIs that don't surprise anyone, databases that keep their promises, and the pipeline that gets it all to production.
I build with AI every day: clear specs first, then I let the tools run, then I check everything. Speed is only useful when you can trust what comes out.
Some ship, some teach me something, a few do both. That's where most of what I know comes from.
Design, books, well-made products and whatever I'm curious about this month. Curiosity is the one habit I never had to build.
Usually within reach: