Practical writing on technology leadership, architecture decisions, and the operational reality of building software organizations. No hype.
This is where I write about the decisions, patterns, and trade-offs that technology leaders deal with every week. Each post is grounded in real situations I have encountered across 20+ years of building and advising engineering organizations.
Topics span AI adoption, system modernization, security programs, engineering culture, and the mechanics of technical leadership. If you lead a technology team, these posts are written for you.
Most AI projects fail not because of technology, but because of unclear problem definition. Before writing a single prompt or training a model, answer these three questions to dramatically improve your odds of shipping something useful.
The instinct to start fresh is strong, but big-bang rewrites almost always take longer and cost more than planned. Here is a practical framework for incremental modernization that delivers value at each step.
Compliance does not have to mean months of checkbox exercises. This post walks through a streamlined approach to SOC 2 readiness that focuses on real security outcomes, not just audit artifacts.
Lines of code, story points, and velocity charts feel productive but often obscure the real question: is your team shipping outcomes that matter? A better approach to measuring engineering effectiveness.
The most common mistake is hiring for technical depth when you actually need operational leadership. Here is how to define the role, structure the interview, and set your first engineering leader up for success.