Building software the same way they did in 2023
Not resistant. Not incompetent. Just not yet crossed the threshold. They're in your organization today, and they're falling further behind with every month they don't cross it.
Slide 01
December 2025 came and went without fanfare. No breathless announcements. No revolution headlines. Just model releases from Anthropic, Google, and OpenAI within six weeks of each other. Any one of these models, arriving alone, would have been a generational leap in capability. All three arrived in a month.
Slide 02
Unclear competitive landscape. Multiple technical approaches with different tradeoffs. Opus 4.5 acted as product manager. It asked clarifying questions I hadn't thought to ask. It searched Google and Bing for competitive analysis, synthesized findings, identified gaps in competitor offerings I hadn't known existed. Then it built a working prototype.
Gemini 3: different reasoning style. Equally coherent output. GPT-5.2: same story.
While everyone watched model releases, Anthropic released Agent Skills as an open standard. OpenAI adopted it. The same skill format now works across Claude, Codex, and ChatGPT.
Skills encode institutional knowledge. Your compliance workflows. Your architecture patterns. Your way of doing things. Once encoded, that knowledge compounds. Every process you teach the model becomes available to every person in your organization, instantly.
Slide 03
Not resistant. Not incompetent. Just not yet crossed the threshold. They're in your organization today, and they're falling further behind with every month they don't cross it.
The gap between using these models for autocomplete and using them to reason through complex problems is the difference between having electricity and having the internet. Your adoption dashboard cannot see this gap.
A small but growing population has reorganized how they think about building software entirely. They're building alone what used to require teams. The gap between this group and the others isn't about productivity. It's about capability — and it's widening every month.
Slide 04
Slide 05
This thing is evolving too fast for consultancies to package into adoption frameworks. By the time they publish the methodology, the capabilities have moved. This is not Agile. This is not DevOps. There is no twelve-month transformation roadmap.
There is only rapid evolution — and the leaders who will thrive are the ones putting their hands on the keyboard now.
Not delegating to your teams. Not waiting for the approved vendor or the security review or someone to tell you it's safe.
Building means running the same product problem through three frontier models yourself. It means encoding your own compliance workflow as a skill and seeing what changes. It means reorganizing how you think about building software — not reading about how others have done it.
Slide 06
The leaders who saw December 2025 for what it was are six months into building the institutional knowledge moat, encoding their compliance workflows, and shipping at a velocity their competitors can't yet explain.
The leaders who treated it as "more model releases" are six months behind — and falling further behind with every month they spend evaluating instead of building.