cargo cult programming
/KAR-go kult PROH-gram-ing/ · noun · Hacker Culture · Origin: 1974
Definitions
Programming by imitating the visible form of working code without understanding why it works, named by Richard Feynman after Pacific islanders who built replica airstrips and control towers expecting cargo planes to return. In practice it looks like configuration copied wholesale from a blog post, ritual incantations retained because removing them once broke something, defensive try/catch blocks nobody can justify, and design patterns applied where they solve no problem the codebase has. The distinguishing symptom is that the practitioner cannot say what would change if the code were removed. Cargo cult programming is often a rational response to genuine time pressure and poor documentation rather than simple ignorance, which is why it accumulates fastest in unfamiliar or badly explained systems.
In plain English: Copying code or practices from successful projects without understanding why they work, hoping the results will magically follow — like building a fake airport runway hoping planes will land.
Example: Adding Kubernetes to a single-server app because Netflix uses it is classic cargo cult programming — the infrastructure won't summon their scale.
Origin Story
The practice of imitating success without understanding why it works
Richard Feynman coined **cargo cult science** in his 1974 Caltech commencement address, drawing on anthropological observations of Pacific Islanders who built wooden 'airplanes' and 'runways' hoping to attract the cargo that arrived during World War II.
In programming, **cargo cult programming** means copying code patterns or adopting practices without understanding why they work. Using design patterns because a book said so. Adding `try-catch` blocks everywhere. Implementing microservices because Netflix does.
The cargo cult concept applies broadly in tech: cargo cult Agile (daily standups without actual agility), cargo cult security (buying firewalls without threat modeling), and cargo cult startups (mimicking Silicon Valley culture without the substance). The antidote is always the same: understand *why* before copying *what*.
Coined by: Richard Feynman (cargo cult science), software community (cargo cult programming)
Context: Caltech commencement, 1974
Fun fact: Feynman's original speech described cargo cult runways in remarkable detail: 'They're doing everything right. The form is perfect. But it doesn't work. So I call these things cargo cult science, because they follow all the apparent precepts and forms of scientific investigation, but they're missing something essential.'