Writing · Dispatches

Code Quality

Standards, measurement, technical debt, maintainability, and codebase discipline.

← All dispatches
№ 054 Jul 2026

Tech Debt Has Gravity

Technical debt does not just slow teams down. At enough mass, it becomes gravity. Escaping it requires deliberate energy, protected capacity, and leadership willing to spend effort climbing instead of pretending every sprint is forward motion.

Tech DebtEngineering LeadershipTeam Systems
Read →
№ 053 Jul 2026

Spartan Simplicity: Carry Less

Every platform, pattern, library, and tool becomes something the team has to carry. Spartan simplicity is the discipline of keeping only what helps the team do the work right.

Code QualityArchitectureEngineering Judgment
Read →
№ 051 Jul 2026

Boundaries Preserve Optionality

Good architecture is not about adding layers for their own sake. It is about preserving future options by putting decisions where they belong.

Code QualityArchitectureEngineering Judgment
Read →
№ 050 Jun 2026

Taste Is Fast (and Earned) Orientation

Taste in software is not magic. It is fast orientation, and it only becomes useful when it can be examined, explained, and turned into judgment other people can use.

Code QualityEngineering JudgmentStandards
Read →
№ 041 Jun 2026

The Disciplined Codebase

Healthy codebases are not built by chasing what feels exciting. They are built through restraint, standards, boring consistency, and doing the necessary work in the right order.

StandardsDisciplineTechnical Debt
Read →
№ 039 Jun 2026

Disciplina: Standards Beat Preference

A healthy codebase cannot depend on every engineer carrying a private version of good. Disciplina turns taste into shared standards the team can actually follow.

Roman VirtuesStandardsDiscipline
Read →
№ 032 May 2026

Stop Reading AI Code. Score It.

The question was never read or measure. It was human or agent. The reviewer does not have to be you.

Code ScoringAI ReviewMetrics
Read →
№ 031 May 2026

I Scored Four Codebases. The Humans Lost.

I scored four codebases against the same rubric. The two that failed were 100% human-written. The two that nailed it were 99% AI-written. Quality is not a human trait.

Code ScoringAI CodeMetrics
Read →
№ 020 Apr 2026

Good Code Isn't Taste. It's Measurable.

Calling code quality 'taste' sounds sophisticated. It's actually the reason teams can't teach it, can't enforce it, and can't get AI to meet it.

Code QualityTasteMetrics
Read →
№ 008 Mar 2026

Tech Debt Is a Choice, Not a Failure

Technical debt can be a rational business choice. It becomes neglect when the cost disappears from view and the team keeps paying interest without reducing the principal.

Tech DebtRiskMaintenance
Read →