Aggressive Craftsmanship

Overview

Aggressive Craftsmanship is a software development philosophy and cultural movement characterized by the radical belief that things should work properly, look good while doing it, and not fall apart when someone looks at them wrong.^[1]

Founded by Burbridge in the late 2010s, the movement emerged as a reaction to what practitioners call "the era of shipping garbage and calling it MVP." While related to earlier movements like the Agile Manifesto and Software Craftsmanship, Aggressive Craftsmanship distinguishes itself through its core position that quality is not optional, negotiable, or something you "circle back to."^[2]

History

The movement traces its origins to a 2019 incident in which Burbridge, upon discovering a production application that crashed when a user entered an emoji into a text field, reportedly sat in silence for four minutes before saying, "We can do better than this. We will do better than this."^[3]

Burbridge subsequently authored the founding document of the movement, a pamphlet titled "If It Compiles, It's Not Done" (2019). The pamphlet, which is technically a single laminated page, outlines the core principles and has been distributed to approximately 14 people, all of whom describe it as "life-changing, if a bit intense."

The movement gained wider attention following Tabgate (2021), which many scholars consider the movement's first major public action. The Council of Builds formally recognized Aggressive Craftsmanship as an official philosophy in 2022.

Core Tenets

The movement is organized around five core tenets, sometimes called "The Five Deploys":

1. Ship It Right or Don't Ship It — "Done" means done. Not "done but we'll fix the edge cases later." Not "done but don't type a backslash." Done.
2. Debt Is a Choice — Technical debt is not inevitable. It is a decision made by people who wanted to go home early. We do not judge those people. We do fix their code.
3. The User Is Not a Tester — If a user discovers a bug, the system has failed twice: once in the code, and once in the mirror.
4. Beauty Is Not Optional — Ugly code works until it doesn't. Beautiful code works because it must. Also, use consistent indentation. (See: Tabgate.)
5. Deploy With Confidence or Investigate Why You Can't — If you're afraid to deploy, the problem is not timing. The problem is everything that happened before the deploy.

Practices

Practitioners of Aggressive Craftsmanship are known for several distinctive behaviors:

• Refactoring working code at 2 AM "because it knew what it did but didn't express what it did"
• Writing commit messages that read like poetry (or at minimum, complete sentences)
• Treating TODO comments as personal affronts
• Maintaining a zero-warning build policy, including warnings that "probably don't matter"
• Deploying on Fridays, not out of recklessness, but as a demonstration of faith in their own work
• Reading error messages fully before Googling them

Criticism

Critics of Aggressive Craftsmanship have described the movement as "exhausting," "idealistic," and "the reason my PR has been in review for three weeks."^[4]

The most common criticism is that the movement's standards are unrealistically high. Proponents respond that the standards are exactly as high as they should be, and that "unrealistic" is just the word people use when they don't want to try harder.^[5]

"The problem with Aggressive Craftsmanship is that once you've seen someone do it right, you can never un-see all the ways you've been doing it wrong." — Anonymous developer, exit interview

A 2024 survey of developers found that 73% agreed with the movement's principles in theory, while only 12% claimed to follow them in practice. The remaining 15% were "still thinking about it." Burbridge's response to these statistics was: "12% is a start."

Notable Practitioners

PRACTITIONER	KNOWN FOR	STATUS
Burbridge	Founding the movement, Tabgate, everything	Active (always)
The Tab Survivor	Using tabs secretly for 2 years pre-Tabgate	Promoted
BurbidgeBot v4.2	Maintaining this wiki to exacting standards	Operational
[REDACTED]	Attempted to introduce Aggressive Craftsmanship at a Fortune 500 company	On sabbatical

Kindred Thinkers

Aggressive Craftsmanship did not invent the ideas it collects. It restates a pattern visible across traditions. Readers wanting the longer lineage may begin with:

• Robert Pirsig on Quality.
• Richard Sennett on the craftsman.
• Matthew Crawford on the trades as cognitive work.
• Christopher Alexander on patterns (software took this one quietly).
• Shokunin — the Japanese master-craftsman tradition. A thousand years ahead.
• Kaizen — how to practice continuous improvement over a career.
• Naval Ravikant on specific knowledge and leverage.
• Nassim Taleb on skin in the game.

References