Software Development
11 posts on this topic — practical guidance from Shawn Livermore on fractional CTO, AI, and technology leadership.
Enterprise Vibe Coding Fails Without Architecture
Vibe coding works for individual builders and MVPs. In enterprise contexts, the same approach without architecture review introduces compounding risk that scales fast.
Read post →What 945 Vibe-Coded Games Teach Us About Code Footprints
945 games were submitted to Vibe Jam 2026. Most shared the same code footprint. Understanding what that means for production software matters more than most builders realize.
Read post →The Code Footprint Your Vibe-Coded Product Leaves Behind
Vibe coding produces working features fast. It does not automatically produce tests, documentation, or clear ownership. Here is what the code footprint problem actually costs and how to manage it.
Read post →Why Enterprise Engineering Teams Are Not Vibe Coding
A Pragmatic Engineer survey shows Claude Code is the top AI tool in smaller teams while enterprise defaults to GitHub Copilot. The blocker is not budget or buy-in — it is architecture.
Read post →Enterprise Vibe Coding Governance: What the Review Standard Needs to Become
At enterprises, AI-generated code has passed 40% of total output and is climbing. Governing it isn't about restricting which tools developers use — it's about ensuring the AI has the architectural context it needs to generate code that is actually deployable.
Read post →What AI Tools Actually Change About Who Builds Software
Benedict Evans argues AI won't make everyone a software builder and apps aren't dead. He's right. Here's what 27 years of watching abstraction waves taught me about where the judgment goes.
Read post →What Vibe Coding Leaves in Your Codebase
AI coding tools generate working code fast. They also make decisions about structure, dependencies, and patterns that persist long after the sprint ends.
Read post →Enterprise Vibe Coding Is Not What the Demo Looked Like
Vibe coding tools work well in constrained solo sprints. In enterprise environments with legacy systems, compliance requirements, and distributed teams, the rules change significantly.
Read post →AI Removed the Developer Bottleneck. Now Every Other Constraint Is Visible.
For decades, enterprise software creation was throttled by developer capacity. AI has shifted that ceiling. The constraints that remain — process clarity, architecture coherence, data quality — were always there. Now they are the binding constraint.
Read post →Enterprise Vibe Coding Governance: What Actually Needs to Happen
Developers inside large organizations are already vibe coding. The question for technology leaders is not whether to allow it but how to govern it before the risk accumulates.
Read post →Vibe Coding Starter Templates and the Hidden Code Footprint
The starter template you pick defines more than the first screen. It defines the security surface, the integration complexity, and the maintenance cost for everything that follows.
Read post →