$ cat about.txt

Hard problems are hard to start.

Paralysis by analysis kills productivity. A change management team should focus on change, not PowerPoints. A CrossFit coach should focus on coaching, not writing programs.

I build tools that remove the busywork so people can do the actual work.

Product and engineering: zoom out to shape the workflow, zoom in to make the implementation clean and shippable.

# how_i_work

[01]

Evidence-first decisions

I anchor work in real user behavior, real constraints, and measurable outcomes—not vibes.

[02]

Systems over hacks

I design for maintainability: clear interfaces, predictable state, and boring reliability.

[03]

Fast feedback loops

I prototype early, validate quickly, and iterate with intent.

[04]

Craft matters

Thoughtful UX, strong naming, crisp docs, and small details that make software feel inevitable.

[05]

Pragmatic optimism

I'm enthusiastic about new tech, but I'm careful about what goes into production.

# tools

AzureClaudeChatGPTCursorv0FlutterFlowNext.jsTypeScriptTailwindVercel

Want to see this approach in action?

$ cd ./projects -->browse case studies