For nearly two decades, I’ve honed a proven philosophy which drives my engineering practice and helps me to better serve you.
If at all possible, I devote my time and attention to one client at a time. This ensures you always get my best work, and you know I’m not spreading myself thin.
I always start with asking why, before what or how. Software is built to serve people, and understanding their needs ahead of building anything is critical. Often, an expensive, complicated solution can be replaced with a simpler one if tradeoffs are considered.
When building a new feature, I work from the user’s point of interaction inward. This ensures that the user—not the engineering—is the focal point. Engineers often attempt to solve an internal problem first, which can lead to solving the wrong problem. Keeping focus on the user leads to better outcomes for everyone.
I remain humble. I don’t pretend to know everything about technology, the product, or its users. I’m not afraid to ask for clarification, but only after exhausting my own inner resources in the pursuit of a solution. I surround myself with people of different strengths, because that’s how you build great things.
I document as I go. Working remotely encourages consistent documentation in order to keep everyone informed. I write self-documenting code, narrate my thoughts as I go, and leave a paper trail which conveys both what changed and why.
Creativity requires regular breaks and time to recharge. Because of this, I rarely bill more than 25 hours per week. Beyond that, the work suffers. I want to give you my best, so I make sure to nourish myself so I come back to your project with a clear mind.
Does my philosophy of engineering resonate with you? Contact me for a free fifteen minute consultation.