Infrastructure religion
Kubernetes
A container orchestration system and reliable generator of organizational opinions.
- 🏠 Habitat
- Companies with 12–10,000 engineers
- 🦈 Predator
- docker compose
- 🤒 Symptom
- YAML
TOPICS · A FIELD GUIDE
Every technology is somebody's religion and somebody else's incident. Here are 42 specimens, their habitat, their natural predators, and who on the team will defend them to the death.
🔥 MOST CONTESTED SPECIMEN
Infrastructure religion
A container orchestration system and reliable generator of organizational opinions.
Repository doctrine
The belief that proximity of code can create proximity of teams, builds and arguments.
Architectural belief
Independent services that allow organizational boundaries to become network boundaries.
Development methodology
Software development in which intent is crisp, implementation is generated, and archaeology begins unusually early.
Agent integration protocol
A standardized way to let models discover tools, and engineers discover they now have too many tools.
Sovereignty practice
Replacing a vendor dependency with a personal operational responsibility.
Confidence metric
A number strongly correlated with the percentage of code executed by tests.
Procurement conflict
A recurring attempt to compare a vendor invoice with engineering time valued at zero.
Labor abstraction
Software given tools, memory and enough autonomy to generate both leverage and new categories of incident.
Operational practice
The process of collecting enough information to confidently misunderstand why production is down.
Engineering ritual
A fresh implementation unburdened by legacy decisions and, briefly, production requirements.
Security doctrine
Never trust, always verify, eventually create a ticket.
Release practice
A conditional that separates deploying code from releasing it, and eventually from understanding it.
Infrastructure belief
Servers you do not manage, billed by the millisecond, debugged by the afternoon.
API doctrine
A query language that lets clients ask for exactly what they need, and lets the backend find out what that costs.
Geographic aspiration
Running code close to the user, so it can wait for a database close to nobody.
Organizational doctrine
A team that paves the road for every other team, then studies why they still drive through the field.
Visual governance
A shared component library that makes every screen consistent, including the ones that needed to be different.
Forecasting ritual
A unit of effort carefully defined as not being time, converted into time by everyone who sees it.
Synchronization ritual
A fifteen-minute meeting where the team learns, out loud and in turn, what was already in the tracker.
Deliberation format
A document written to make a decision, reviewed until the decision has already shipped.
Financial metaphor
A loan taken out by past engineers, repaid by current ones, at an interest rate nobody wrote down.
Data sovereignty movement
Software that works offline, syncs later and resolves conflicts eventually, sometimes philosophically.
Database heresy
A file that is also a database that is also, it turns out, a production architecture.
Interface preference
A second color scheme, requested by everyone, designed by one person, and tested at night by users.
Productivity legend
An engineer whose output is ten times a peer’s, depending heavily on who is counting and when.
Triage ritual
A four-level scale on which every customer ticket is, according to the customer, P0.
Empathy program
A week in which engineers answer customer tickets, discover the product, and file eleven bugs against their own code.
Deflection technology
A friendly assistant that resolves 60% of tickets, measured as the share of customers who gave up.
Commercial doctrine
A principle stating that the customer is right about the problem and, occasionally and expensively, about the solution.
Alignment ceremony
A monthly gathering where the whole company hears the strategy at once, then asks about the parking in the Q&A.
Career artifact
A document proving the author's impact, written in the time that could have been spent having some.
Growth ritual
Running many small bets to learn what works, and occasionally learning that nobody agreed what was being tested.
Empirical practice
Watching real people use the product, then discovering they do not use it the way the roadmap said.
Financial hobby
Reducing the infrastructure bill, frequently using engineers whose salary is not on the bill.
Architectural reflex
Making something generic before the second use case exists, so that the third one can arrive and not fit.
Measurement faith
Numbers chosen to describe whether things are going well, until they become the thing everyone works on instead.
Reproductive ritual
Adding people to the team, usually to solve the problem the previous hire was meant to solve.
Load-bearing gift
Code written by strangers, for free, that the company's revenue quietly rests on.
Social infrastructure
Offsites, team buildings and escape games designed to build trust, attended by people who would rather be shipping.
Quality ritual
A pipeline that proves every change is safe, in roughly the time it takes to forget what the change was.
Nondeterministic species
A test that fails one run in twenty, and teaches a whole organization that red means “click retry”.
No species matches. Maybe it's still in beta.