Named after 14th-century philosopher William of Ockham, this principle has stood the test of time for one simple reason: it works.
The core idea? “The simplest explanation is usually the correct one.”
- In Latin: “Pluralitas non est ponenda sine necessitate”
- In plain English: “Don’t multiply entities beyond necessity”
- Or, as we’d say today: Stop overcomplicating things.
Why Does This Matter?
Our brains love creating elaborate stories. Someone doesn’t reply to your message? Your mind might craft an entire narrative about what you’ve done wrong, when in reality, they’ve simply left their phone in another room. Occam’s Razor cuts through this mental clutter. It’s not about being lazy or simplistic—it’s about starting with the most probable explanation before jumping to complex conclusions.
Important Caveats
Occam’s Razor Isn’t Always Right
Sometimes, the complex explanation is correct. The point isn’t that complexity is always wrong—it’s that you should test simple explanations first. If you’ve genuinely ruled out the simple causes, then by all means, investigate the complex ones. But don’t start there.
Simple ≠Simplistic
Occam’s Razor doesn’t mean “pick the easiest answer and stop thinking.” It means:
- Start with the most probable explanation
- Test it properly
- Only add complexity when evidence demands it
A simple solution that doesn’t work isn’t a solution at all.
Key Takeaways
For Coding:
Write the simplest code that solves the problem Don’t add abstraction layers “just in case” Optimise for readability first, cleverness second
For Debugging:
Check your own code before blaming external systems Look for typos before architectural flaws Test the obvious before investigating the obscure
For Life:
Don’t create elaborate narratives when simple explanations exist Most people aren’t thinking about you as much as you think The straightforward answer is usually right
For Communication:
Say what you mean, clearly and directly Cut unnecessary jargon Simple words are powerful words
Your Challenge
For the next week, whenever you face a problem:
- Pause. Don’t immediately jump to complex explanations.
- Ask. “What’s the simplest possible cause?”
- Test. Check that first, thoroughly.
- Reflect. How often was the simple answer correct?
You’ll be surprised how often the answer is right in front of you.
Remember: The best code is the code you don’t need to write. The best solution is the one you can explain in a sentence.
Keep it simple. Find the truth.
William of Ockham would’ve made a brilliant developer. His razor? It’s the original KISS principle, 700 years before we called it that.