Thoughts on engineering, leadership, and building software that matters.
Traditional code reviews are broken. After years of watching pull requests languish in review queues and rubber-stamp approvals erode quality, I replaced them with something better — pair programming sessions, automated quality gates, and architecture reviews.
How we built a deployment pipeline where any engineer — from day-one new hires to senior architects — can go from code to production in 30 minutes with full confidence and zero heroics.
Why we started with a monolith, when microservices actually make sense, and the cautionary tale of a competitor whose premature decomposition into microservices nearly destroyed their engineering velocity.
Building software in telehealth and health tech means navigating HIPAA, SOC 2, and a maze of regulatory constraints. Here is how we learned to move fast without breaking compliance — and why regulation can actually be a competitive advantage.
Technical debt is not a moral failing or a sign of bad engineering. It is a business decision that should be quantified, communicated to stakeholders, and strategically managed like any other form of leverage.
Building an on-call culture that respects engineers' time through automation, runbooks, escalation policies, and blameless postmortems — because sustainable operations require sustainable people.