Every line of code is a liability. I build systems where the complexity lives in the business domain, not the technology. Simple code, clear interfaces, boring technology that your team can master — that's what ships reliably.

I design for change, not perfection. Customers invest in outcomes, not technology. I make architectural decisions that keep options open, delay irreversible choices to the last responsible moment, and keep the cost of iteration low. When your assumptions change — and they will — your system should adapt gracefully.

Strategy without execution is a slide deck. I build execution cultures — where sprints actually work, PRs get real reviews, master is always deployable, and deployments are zero-touch. I've codified this into what I call The KHIVI Test: ten questions that tell you if your engineering org is actually shipping or just busy.

I believe in small experiments over grand plans, fast feedback over perfect specs, and teams that own their quality end-to-end. Product, engineering, and business aren't separate functions — they're one team solving one problem.

The best engineers I've worked with weren't born great — they were mentored well. I challenge engineers to come up with their own solutions, guide them through the tradeoffs, and create environments where they can take ownership. I wrote Culture Seeds to capture the patterns that build great teams: how to hire, how to set standards, how to create a culture where quality is the path of least resistance.

Currently writing my next book on engineering in the AI era — how the craft changes when your tools can generate code but can't yet think about systems.