Left of the Loop
A series about shifting engineering left in the age of agents.
Left of the Loop is a mental model I’m building in public.
AI erodes the incidental friction that used to produce shared understanding as a byproduct of the work. That makes shared understanding the scarce resource, and constructive friction the mechanism that protects and tests it. Implementation getting radically cheaper is why this is happening now, and at scale. The organizations that preserve the constructive kind will outperform the ones that optimize it away.
Practically, that means engineering work moves earlier. Left, toward defining what the system should do before anything gets built.
This is a working theory, not a proven framework. I don’t have the structure yet to validate it at scale: no team running it end to end, no metrics, no final proof. These are field notes, not conclusions.
But I think it’s worth following. Maybe as a team, maybe as a company. Not to turn engineers into reviewers of whatever the agent produced, but to put thinking back at the center of the work.
I’ll keep writing as the ideas take shape. If a post shifts how you see your own process, or you think I’ve got it wrong, that’s the point. Tell me.
Short on time?
Four posts carry the spine: The Wrong End of the Problem sets up where AI actually belongs in the process. The Agora is the room where a team builds that understanding together. The Alexandria Problem is what’s at stake when nobody writes the code anymore. The Phoenix closes it. Read the rest when you want the whole argument.
The Full Series
The complete series: 20 parts.
- The Wrong End of the Problem 2026-06-18 Where does AI actually belong in your development process?
- A Fool with a Tool is Still a Fool 2026-06-20 If one person and an agent can ship, why keep the team?
- The PO is Dead, Long Live the PO 2026-06-22 What happens to the product owner when agents do the implementing?
- The End of the Craftsman? 2026-06-24 Does craftsmanship still matter when agents write the code?
- The Ever-Agreeing Genie 2026-06-26 What breaks when your only reviewer is built to agree with you?
- The Alexandria Problem 2026-06-28 When people stop writing the code, where does the shared knowledge go?
- The Agora 2026-06-30 What actually happens inside a Spec Session?
- The Trireme 2026-07-02 What's the smallest team structure a Spec Session still needs?
- The Astrolabe 2026-07-04 Which layer does each AI tool actually belong in?
- The Oikonomos 2026-07-06 Who's stewarding the budget an agent loop spends?
- Nobody's Walking Over to a Desk 2026-07-08 What broke when walking over to ask became asking the agent?
- Who's on the Hook? 2026-07-10 When agents write the code, who's accountable for what ships?
- The Kybernetes 2026-07-12 How do you see into and steer an autonomous agent loop?
- The Mimesis 2026-07-14 How do juniors learn when the agent writes the code?
- The Metron 2026-07-16 What should you measure once output is cheap?
- The Gymnasion 2026-07-18 How does a team learn what an agent can really do before betting a spec on it?
- The Boule 2026-07-20 How do you run a Spec Session across more than one team?
- The Pheme 2026-07-22 How does a decision reach everyone who wasn't in the room?
- The Hestia 2026-07-24 What keeps shared understanding alive after you've built it?
- The Phoenix 2026-07-26 When a team ends anyway, what do you choose to carry forward?