Software Architecture
5 posts on this topic — practical guidance from Shawn Livermore on fractional CTO, AI, and technology leadership.
The Vibe Coding Code Footprint: Why Your Starter Template Is a Governance Decision
How you start a vibe coding session shapes every line that follows. The starter template is not a convenience — it is the governance boundary that determines whether the code is reviewable, extensible, and safe.
Read post →The Enterprise Software Specification Is Broken. AI Is Making That Visible.
AI coding tools fill specification gaps with defaults from their training data. In enterprise software, those defaults are rarely correct. The specification problem that always existed is now impossible to ignore.
Read post →The Context File Your AI Coding Tool Needs Before the First Prompt
Starter templates set the structure of your codebase. Context files tell AI tools how to behave within it. The second matters as much as the first — and most teams skip it.
Read post →Enterprise Vibe Coding: Why Speed Without Governance Breaks at Scale
Individual AI coding assistance is a productivity story. The same capability running across 20 engineers in a shared codebase with security requirements and integration dependencies is a governance problem.
Read post →Vibe Coding Templates: What Your Codebase Leaves Behind
AI-generated code moves fast. The patterns and assumptions it deposits in your codebase stick around much longer. Here is why starter templates exist and what responsible vibe coding looks like in practice.
Read post →