Loading...
Loading...
point of view · operating thesis
Not a blog post. A working thesis on how I think about technology, teams, and the work of leading engineering at scale.
last reviewed · May 2026
These are the beliefs I keep coming back to, the ones that survive the next tool, the next framework, the next reorganization. They shape how I lead, how I hire, how I evaluate platforms, and how I pick the problems worth solving.
It was not the stack when we moved to cloud. It was not the stack when we moved to containers. It is not the stack now that we have agents. The bottleneck is clarity of intent, encoded in durable artifacts, enforced by systems rather than willpower. Most enterprise technology debates argue about tools when the real conversation lives upstream of any tool decision.
Tools matter, but they rarely fix unclear ownership, weak incentives, or disconnected priorities. Before we argue about platforms, we should agree on who owns the outcome, how work flows between teams, and what the business is actually trying to do. The tooling conversation becomes easier, and cheaper, once those are clear.
The advantage will not go to the organization with the most AI pilots or the biggest model budget. It will go to the one that builds feedback loops, challenges its own assumptions, and adapts the operating model as the work changes. Shipping velocity without learning velocity is just expensive motion.
Prompt engineering taught us how to talk to a model. Spec engineering is what we are learning now: a clear, versioned, reviewable specification, a layer of project standards, and a coordinated set of specialists working inside the guardrails. In an agentic SDLC, code becomes the regeneratable output of that system. The artifact your organization is producing is no longer the codebase. It is the specification. The repo starts to feel less like inventory and more like a fossil record.
A platform is not successful because it exists. It is successful when teams can move faster with less friction and more confidence. Every platform decision should be evaluated by whether it makes the daily work of engineers easier, not by how elegant it looks on an architecture diagram. Discipline does not scale. Automation does. Standards belong in files, not in heads.
Developer experience is not an internal nicety or a recruiting perk. It shows up in delivery speed, quality, reliability, cost, and the ability to retain the engineers you want to keep. Treat it like a product with measurable outcomes, not a side project that gets attention when someone complains loudly enough.
Teams move faster when they trust the system, their leadership, and each other. Governance, observability, and human-in-the-loop are not friction. They are the engineering work that makes speed sustainable. When trust is present, small process problems get solved quietly. When trust is absent, even good processes produce friction. Leaders spend too much time on process and not enough on the conditions that make process unnecessary.
Leaders do not need to write every line of code, review every PR, or sit in every design session. But they do need to understand how the work is changing, especially when AI, platform shifts, or new delivery models are rewriting the ground rules. There is a unique kind of empathy that comes from debugging your own code at 11 PM. Leadership three layers removed from the craft makes slower, weaker decisions.
Strategy that cannot survive a leadership transition was a preference, not a strategy. Platforms only work when the defaults are inherited, not chosen. If you are building monuments to yourself, you are building tomorrow’s technical debt. The best thing any of us can build is something that keeps getting better after we leave the room. That is not a small ambition. It is the whole job.
Technical alignment without sociopolitical alignment is not safety. It is just better engineering for a worse outcome. Vague reassurance is not safety. Specificity is. When we describe an engineering vision in the same words we would use with someone whose career is being reshaped by it, we sound like the villain in a movie. Builders set the language. Builders own the trust deficit. Pick the version of the bargain you can live with.