No Repo, No Glory

“Here's the prod server password. Good luck!”

Previously: The AI agent discovered that “figure it out” means “ACCESS DENIED” everywhere. This week: what happens when you ask a developer agent to help—without giving it what developers actually need.

Comic: No Repo No Glory - Developer agent asked to fix bug but given only a sticky note with password

“Can you help me understand how the payment service works?” — “Ask Mike.” — “Mike left in 2022.”

The Point

TLDR: If your code isn't in version control with good commit messages, and your architecture lives in someone's head, you're already dead.

A developer AI agent needs: Git repositories, architecture documentation, API specifications, test suites, CI/CD configs, code review history, and deployment runbooks. What it usually gets: a sticky note with “password123” and a prayer.

Tech Gaps That Kill Developer Agents

Code not in Git

Still on SVN? TFS? A shared drive called “Code_Final_v2_REAL”?

No documentation

README last updated 2021, references deprecated services

Hardcoded secrets

Can't give AI repo access because prod passwords are in config files

Tribal deployment

“Ask Dave, he's the only one who knows how to deploy to prod”

Haunted files

“Don't touch that file, it's haunted” — actual institutional knowledge

The Human Version

Every developer has inherited a codebase where the original author left, the documentation is wrong, and the only person who understood the payment service was “Mike.” Mike left in 2022.

← Access Denied

Next Episode

I Don't Know These People →

Progress

3/8

Want the full context? Read the companion blog post.

Read Freedom '26