The Engineering of Intent, Chapter 35: A Short Bestiary of Vibe Coders

This is Part 35 of a series walking through my book The Engineering of Intent. In the previous chapter, we catalogued the languages. Chapter 35 catalogs the people — a light-hearted bestiary of the eight archetypes you’ll meet on AI-native teams.


None Is Purely Good or Bad. Each Has Strengths and Failure Modes.

Over the years I’ve watched Vibe Coders fall into eight distinct personas. Recognizing your own is the first step toward improving it. Recognizing a teammate’s prevents most interpersonal friction. Don’t take the categories too seriously. Take them just seriously enough.


The Eight

  1. The Sprinter. Ships many small things per day. Creates momentum. Underinvests in Specs; leaves Context Rot. Growth path: plan a day’s work in advance, one morning a week.
  2. The Architect. Plans extensively, invests in Specs. Produces durable artifacts. Plans that never ship; abstractions two steps ahead. Growth path: no plan lives more than two days before a first increment lands.
  3. The Skeptic. Treats the agent as a suspicious collaborator. Pulls quality up. Slow; underuses available leverage. Growth path: grant tactical trust in one well-calibrated class of task.
  4. The Believer. Treats the agent as near-peer. High autonomy, fast iteration. Susceptible to agent failures; over-delegates human-judgment tasks. Growth path: one line-by-line review session a week.
  5. The Pedagog. Teaches every session. Excellent for culture. Slow; over-comments self-evident code. Growth path: time-box teaching; also measure shipping.
  6. The Tool-Smith. Builds compulsively. Productive at steady state. Yak-shaves; reinvents commercial tools. Growth path: set and hold a tool-building budget.
  7. The Commentator. Writes and speaks about the practice. Advances the discourse. Theory without practice; becomes a talking head. Growth path: publish only what you’ve shipped; keep ratio 2:1 shipping:speaking.
  8. The Steady. Consistent, unflashy, long-horizon. The backbone of good organizations. Under-recognized; becomes the unofficial bottleneck. Growth path: document more — make your quiet knowledge legible.
💡 Key idea: No one is purely one archetype. Most engineers are a blend of two or three, with one dominant. The failure is not having a type — it’s being stuck in your type’s failure mode without noticing. Each growth path is small, concrete, and repeatable. Pick the one that matches the type you’re closest to and run it for a month.

The Most Underrated Archetype

“The Steady is the backbone of good engineering organizations. Their aggregate contribution over years is enormous. They’re under-recognized in cultures that reward visibility. If you’re managing a team, find your Steadies and make sure they’re paid what they’re worth. If they leave, you will feel the absence for a year.”

âš  The most dangerous combination: The Believer + The Commentator. Someone who delegates broadly to agents and writes confidently about it. The talks are strong; the shipped code is fragile. If you’re hiring and someone’s Twitter looks perfect, check their PRs. Theory fluency is not the same as practice fluency.

Next up — Chapter 36: The Long View. The final chapter of Part IX steps back to ask what happens to the craft, the profession, and the life over the next ten years. Cycles and waves, what endures, what changes, and a final word on identity.


📖 Want the full picture?

The chapter walks all eight archetypes with strengths, failure modes, and concrete growth paths. Read to find your type. Then read the growth paths for the types you aren’t — those are the people you need on the team.

Get The Engineering of Intent on Amazon →

2026-05-21

Sho Shimoda

I share and organize what I’ve learned and experienced.