Engineers have a gift for detecting patterns, it's basically the whole job. So when a coworker said "that's just Murphy's Law" to me recently, it caught me off guard that I couldn't tell you where the phrase actually came from, who coined it, or when it came into existence. It's something we all know, and I thought to myself, what are the other laws? One search turned into ten, and by the end I had a list of eleven ideas I'd been recognizing my whole career without ever knowing their names.

Take a look at these laws and see how many, if any have you heard at any point of your career:

1. Parkinson's Law
Work expands to fill the time you give it. Schedule a two-week window for a migration, it takes two weeks. Get told you have a single weekend maintenance window because that's all change management will approve, it somehow gets done in a weekend. The task didn't change. The window did the work.

2. Hofstadter's Law
It always takes longer than expected, even when you plan for it taking longer than expected. "This should be a fifteen-minute patch" is a sentence that has never once been true, and I keep saying it anyway.

3. Hanlon's Razor
Don't assume malice when incompetence explains it just fine. A ticket sits untouched for two days, a config gets pushed without a change record, someone skips you on an email chain, the first read is never "they're doing this to sabotage me." It's usually just an overloaded queue or someone who forgot a step. Assuming malice is a fast way to burn a relationship with another team over nothing.

4. The Pareto Principle
80% of your incidents come from 20% of your environment. Same handful of aging switches, same one flaky link, same misconfigured service account showing up in the postmortem every single time. The rest of the environment barely makes noise by comparison.

5. The Peter Principle
People get promoted until they land in a job they're bad at, then they stay there, because the promotion was the reward and there's nowhere left to put them.

6. Hick's Law
More options, slower decisions. A dashboard with four key metrics gets read in ten seconds. A dashboard with forty widgets crammed onto one pane of glass gets stared at for five minutes while you try to figure out which one actually matters right now.

7. Goodhart's Law
Once a measurement becomes a target, it stops measuring anything real. Say average ticket close time gets used as a performance metric, makes sense at first, faster closes usually mean the tech knew what they were doing. Then it becomes something reviews are graded on. Now tickets get closed and reopened just to reset the clock, or bounced to another queue to get them off someone's own numbers. The average still looks great. It's not measuring efficiency anymore, it's measuring who's best at gaming the number.

8. The Dunning-Kruger Effect
The less you know about something, the more confident you tend to feel about it. An engineer three weeks into the job will tell you exactly what's wrong with total certainty. A thirty-year engineer will hedge every sentence, because they've actually been burned by every edge case that makes certainty a bad bet.

9. Occam's Razor
The simplest explanation is usually the right one. A server's unreachable and the pager's going off. It's probably not a sophisticated attack. It's probably a cable, a certificate that expired, or somebody's change and did exactly what it was told to do.

10. Chesterton's Fence
Don't remove something until you understand why it's there. Some ancient firewall rule, some VLAN nobody remembers provisioning, some scheduled task with a name like "DO NOT DELETE", it looks like dead weight until you disable it and something two systems away breaks in a way that takes half a day to trace back.

11. Brooks' Law
Adding people to a late project makes it later. A rollout is behind schedule and someone suggests pulling two more engineers onto it to catch up. New people need ramp-up time and answers to questions, and that ramp-up time gets pulled straight from the people who were already making progress. The math never works out the way it feels like it should on paper.

None of these are new ideas. They're old enough that somebody already named them an eternity ago because the pattern kept showing up enough to earn a label. I've personally seen most of them in action. Now that I know the name to them, I catch myself seeing them happening in real time. How many have you seen? How many did you know by name?