All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

7 unwritten software engineering laws learned the hard way

By

Anton Zaides

3h ago· 7 min readenInsight

Summary

The article discusses unwritten rules in software engineering that experienced engineers learn through trial and error. It presents 7 practical laws that go beyond the famous named laws (like Hyrum's, Conway's, Zawinski's), focusing on hard-earned lessons from breaking things in production. The author aims to help newer engineers avoid common painful mistakes by sharing these unwritten principles that every seasoned engineer knows but rarely documents.

Key quotes

· 4 pulled
Beyond the named laws, there are many unwritten rules every engineer who's been around for a while just knows.
You learn them by breaking things and swearing you'll never do it again.
As everybody and their mother thinks they can build great software right now, I decided to help them avoid a bit of pain.
Here are 7 laws every engineer has broken at least once, learned the hard way
Snippet from the RSS feed
Last April, I wrote a well-received article about the 13 software engineering laws - Hyrum’s, Conway’s, Zawinski’s, and 10 famous others.

You might also wanna read