Why government apps fail before engineering does
Most civic products lose at the behavior layer, not the codebase. Here's what I've seen across public-sector mobile work.
Writing
Essays and notes on behavioral design, product strategy, government technology, engineering, AI, and learning to build. Organized by theme, a digital garden, not a chronological blog archive.
New here? Start with these three
Every feature must earn its place
A filter I use before anything ships, and why most roadmaps ignore it.
Simplicity creates trust
What funeral homes and state lotteries taught me about digital products when the stakes are real.
Technology is the medium. Behavior is the outcome.
The central question behind everything I build and write.
What lotteries taught me about App Store psychology
Extended rejections aren't technical problems first. They're trust and communication problems wearing a technical costume.
From the court to the code
Seven years of professional basketball, then self-taught software. What the transition taught me about learning and building.
Practitioner vs. pundit
Why I operate a family business, write code, and refuse to be a slides-only advisor.
Stability before growth
What the SEE Framework taught me about why most apps chase expansion before they've earned the right to grow.