01 // About
How I think, why I care, and the turning point that shaped how I build software.
Executive Summary
I’m a software engineer who spends as much time in a product roadmap as I do in a code editor. My role is to translate business goals into software that makes sense to the people using it. Over time, I’ve learned that the most expensive code is the code nobody needs. That realization fundamentally changed how I work.
How I Think
I start every project by asking: "How can we solve this without writing code?" Code is a liability. It requires maintenance, security updates, and cognitive load. The best feature is the one you didn't have to build because you solved the user's problem a different way.
- Start with the problem: Technology is just a tool. If a spreadsheet solves the problem, use a spreadsheet.
- Constraints are inputs: Limitations in budget or time aren't blockers; they are the parameters that define the elegant solution.
- Simpler systems win: Complex systems fail in complex ways. Simple systems fail in predictable ways.
The Turning Point
Early in my career, I spent six months architecting a "perfect" microservices backend for a product that hadn't found product-market fit. When the business pivoted, all that code became instant technical debt.
That was the moment I realized that shipping fast without clarity isn't agility; it's just generating waste. Now, I optimize for decisions, not just delivery.
Values, In Practice
- Work–life harmony: Burnout is an engineering failure. Sustainable pace delivers better software than heroics.
- Collaboration over ego: Strong opinions, loosely held. I care more about getting to the right answer than being the one who provided it.
- Ethical integrity: I won't build dark patterns. User trust is a finite resource that is hard to gain and easy to lose.
What This Site Represents
This is a garden of finished thoughts, not a stream of consciousness. I publish here when I have something substantive to say about the intersection of technology, business, and human behavior.
You won't find hot takes on the latest framework here. You will find essays on the enduring principles of building useful things.
What I Do, Explicitly
I help companies stop bleeding money on software they don't need. I build products that serve business goals, using the simplest technology possible to get the job done.