Such Dev Blog
Who am I ?
Portfolio
Resources
Lessons
Opinions
Tutorials
Who am I ?
Portfolio
Resources
Lessons
Opinions
Tutorials
  • Who am I ?
  • Portfolio
  • Resources

    • πŸ‘Ά Resources for the Beginner WebDev
    • πŸ‘© Resources for the Intermediate WebDev
    • πŸ‘΄ Resources for the Senior WebDev
    • πŸ§‘β€πŸŽ¨ Design resources for WebDevs
    • πŸ€– LLM / AI Resources
  • Lessons

    • 🍻 Does your Pull Request pass the Hangover test?
    • πŸ“ˆ Productivity and Well-being, A summary of what works.
    • ⭐ Dramatically increase your productivity with Atomic Git Commits
    • πŸ§‘β€πŸ’Ό How to Learn Git Slowly
    • 😠 How to Start Learning CSS without hating yourself
    • 🧠 How to be a great software engineer without using your brain
    • ⁉️ Explaining Ruby's Singleton Class (Eigenclass) to confused beginners
  • Opinions

    • πŸ”ͺ The Technical Debt explained with a kitchen analogy
    • πŸͺ  Why our work culture sucks
    • 🧹 The Marie Kondo guide for the Clean Developer
    • πŸ’‘What contributing to Open-source is, and what it isn't
    • πŸ’΅ Why diversity is important, no, really, actually for real
    • πŸ•Έ Networking is easy, fun, and probably not what you think it is.
  • Tutorials

    • πŸ“ Build your own system with ArchLinux
    • πŸ’½ Testing Ansible scripts with Vagrant
    • πŸ’Ž Upload Files from Vue.js to Rails with ActiveStorage
    • πŸ’Ž Filter Anything in a Rails request in 10 lines of code
    • πŸ’Ž Test all your GET routes in rails with 20 lines of code
    • πŸ’Ž How to use Solr / Sunspot with Rails
    • πŸ’Ž Debugging Solr Sunspot like a pro

🍻 Does your Pull Request pass the Hangover test?

This is a short reminder about what Programming is.

Programming has and will always be about reducing complexity first and foremost.

If you ask a coworker to review your pull request, always ask yourself: does it pass the Hangover test?

Can your coworker turn on his computer after having drank too much the previous evening and still be able to understand your code with minimal effort?

It's always easy to write complex code on a good day. Complexity is easy to write; simplicity is not. Just because you had an easy time writing it on that day doesn't mean it's simple enough for someone else to understand it on a bad day.

Because you don't write code for writing it, you write it for it to be read - it will be written once but read 50 times or more.

If you're not writing for Hangover Coworker, you're making your life -and the life of every colleague, present and future- harder.

Remember that complex code is not a sign of intelligence, it's a sign of sloppiness.

So can someone kill their brain cells with too much alcohol and the next morning still make sense of your code with relative ease?

If not, back to the drawing board πŸ” Make it better until it passes the Hangover test.

Last Updated: 7/31/25, 11:17 AM
Contributors: Samuelfaure
Next
πŸ“ˆ Productivity and Well-being, A summary of what works.