Category: strategy
-
The 5x Myth: What AI Actually Changes About Delivery Speed
A fintech CTO I work with had her board moment three months ago. The chair leaned forward mid-review and asked the question every technology executive dreads: “So you’re telling me you don’t know if this is working?” Her answer was better than most: “I’m telling you that the numbers we were using to answer that…
-
The four layers of AI-driven engineering organizations
After a year of writing about what breaks when AI enters engineering organizations, I can name the single thread that connects every failure and every success: whether the organization preserved judgment while changing how work gets done. Threat modeling, governance, spec-driven development, architecture reviews, measurement problems, the CTO’s evolving role. Each post addressed a specific…
-
The CTO’s real job when AI changes how software gets built
A few months ago, a CTO I know pushed a massive change directly to production. He had used an AI coding tool to generate the entire thing over a weekend, bypassed code review, skipped staging, and deployed it himself. By Monday morning, the system was broken. The QA engineer who spent two days untangling the…
-
The Community Is Building AI-DLC Without Knowing It
A few weeks ago, a developer on Reddit posted about a workflow they had built for Claude Code (r/ClaudeAI, March 2026). They had split their AI-assisted development into three distinct agents: an Architect that defined the system design and constraints, a Builder that generated the code, and a Reviewer that evaluated the output against the…
-
Why Your Cloud Migration Succeeded and Your Cloud Operations Didn’t
A few years ago, a financial services company asked us to help them roll back a cloud migration. Not pause it. Not optimize it. Roll it back. This wasn’t a company that was new to the cloud. They had been running cloud-native workloads on AWS for years: new applications, innovation projects, critical business services built…
-
The Four Things AI Cannot Replace in the People You Hire
A few months ago, I was interviewing a candidate for a senior engineering role. Strong resume. Solid certifications. Good technical depth. Halfway through the conversation, I asked a question I always ask: “Tell me about a time you had to throw away your own work because the team found a better approach.” The silence lasted…
-
The Conversation This Book Is Really About
Over the past year, I’ve had the same conversation with at least thirty CTOs and VPs of Engineering. The setting changes: a conference hallway, a video call, a dinner after a workshop. The words change. But the conversation is always the same. It starts with a number. “Our developers are 40% more productive.” Or 30%.…
-
I Wrote a Book: Reimagine, Don’t Retrofit
I’ve been building software since I was fourteen, when I sold my first software product. Nearly three decades later, having risen through consulting and architecture roles, co-founded companies, and eventually become a CTO responsible for the delivery strategy of hundreds of cloud projects across Latin America, one pattern has stayed constant. Every major platform shift…
-
The Hidden Cost of Unpreparedness: Cloud Migration Without a Foundation
Recently I was working with a financial services company on a cloud migration project. The scope was significant: over 180 servers, multiple business-critical applications, and tight regulatory requirements. On paper, it looks like a standard enterprise migration. But there was a problem, one I’ve seen too many times before. The customer hasn’t prepared for what…
-
From Vibe Coding to Spec-Driven Development: The Next Leap in AI Software Engineering
In my last post, “The Mismatch Between AI Code Assistants and Enterprise Software Development,” I talked about how coding assistants (despite their brilliance) often fail to align with enterprise reality. They generate code fast, but without context, structure, or shared understanding. The result? More rework, more debugging, and less trust. Today, I want to explore where…
