Quality is a team knowing what its software does.
We write about how teams keep that knowledge while coding agents write more of their code. We also build suss, an open-source tool that reads code and writes down what it does, with no model in it.
suss Reads TypeScript, Python and Ruby and writes down what each handler, consumer and query does. It runs on your machine or in CI, with no account and no model. suss.sh → suss for Claude Code A plugin that tells the agent after each edit when it broke the other side of a route or table, and checks the work against the agent's plan when it stops. How it works →
Featured essay Congratulations, You Gave Your Most Confident Junior Engineer a Megaphone Ownership, review and the senior engineer’s job when an assistant writes much of the code. From the archive
"Their value is in their familiarity with the system. It's the hard-won, almost intuitive understanding of the codebase's dark corners and emergent behaviors."
Matt Kindy, on what senior engineers are for, in Congratulations, You Gave Your Most Confident Junior Engineer a Megaphone
Example
From one handler to the whole path.
suss reads the handler, follows the functions it calls, checks the app that calls it, and joins it all into one record of the path.
src/accounts.ts the API
1 app.get("/accounts/:id", async (c) => {
2 const account = await db.account.find(c.req.param("id"));
3 if (!account) return c.json({ error: "not found" }, 404); ← 404 when there’s no account // 404 when there’s no account
4 if (account.deletedAt) return c.json({ error: "gone" }, 410); ← 410 once it’s deleted // 410 once it’s deleted
5 await recordAccess(account.id); ← calls recordAccess in src/audit.ts // calls recordAccess in src/audit.ts
6 return c.json(account); ← 200 with every column of the row // 200 with every column of the row
7 });
app/routes/accounts.py the API
1 @router.get("/accounts/{account_id}")
2 def get_account(account_id: int, db: Session = Depends(get_db)):
3 account = db.get(Account, account_id)
4 if account is None:
5 raise HTTPException(status_code=404) ← 404 when there’s no account # 404 when there’s no account
6 if account.deleted_at:
7 raise HTTPException(status_code=410) ← 410 once it’s deleted # 410 once it’s deleted
8 record_access(db, account.id) ← calls record_access in app/audit.py # calls record_access in app/audit.py
9 return account ← 200 with every column of the row # 200 with every column of the row
app/controllers/accounts_controller.rb the API
1 def show
2 account = Account.find_by(id: params[:id])
3 return head :not_found if account.nil? ← 404 when there’s no account # 404 when there’s no account
4 return head :gone if account.deleted_at ← 410 once it’s deleted # 410 once it’s deleted
5 AuditTrail.record_access(account.id) ← calls record_access in app/models/audit_trail.rb # calls record_access in app/models/audit_trail.rb
6 render json: account ← 200 with every column of the row # 200 with every column of the row
7 end
What we keep writing about
People
When an agent writes the code, a person on the team still owns it. We write about review, ownership and what senior engineers do now.
Attention
Understanding a system takes time and focus. Good tools take on as much of that cost as they can, so people can spend theirs on decisions.
Process
Planning, review, release and on call each depend on knowing what the code does. We look at how each step can find out.
Essays
All essays → Boundaries Finding the Unknown Unknowns A field rename passes every check, and days later a dashboard nobody knew about stops working. Boundaries Avoiding Integration Bugs: Beyond SDKs & Contract Testing Typed clients, contract tests and integration tests each catch a different kind of break. Coding agents Congratulations, You Gave Your Most Confident Junior Engineer a Megaphone Ownership, review and the senior engineer’s job when an assistant writes much of the code. Distributed systems Serverless Isn’t Magic Cold starts, the distributed monolith, and services cut so small nobody can see where one ends. Distributed systems Embrace Complexity How a chain of synchronous calls grows into sagas, circuit breakers and gateways. Reading code Designing Dev Tools with Cognitive Load in Mind What a developer has to hold in their head to make one change, and how tools can help.