What Running the Business Side Taught Me About Better Engineering

For most of my career, I've done both sides of the table: writing the software and running the business it lives inside — client delivery, hiring, operations, compliance. Early on, I thought of the business side as overhead that pulled me away from the real work. I don't think that anymore.

Sitting in client conversations changes how you scope a feature. You hear the actual cost of an ambiguous requirement, not the sanitized version that reaches engineering through a ticket. Hiring for a small team forces you to think concretely about what "good" looks like at every level, instead of relying on a vague sense of talent. Compliance work makes you specify edge cases you would otherwise have waved away as unlikely.

None of this makes me a better engineer than someone who has only ever engineered. But it's made me a more accountable one — because when a technical decision goes wrong, I'm also the person explaining it to the client, or the one who has to live with the operational fallout. That accountability loop is worth more than most technical training I've had.