Software Engineering Laws
A practical sequence on the recurring laws and constraints that shape engineering work, from coding and architecture to testing and performance.
Series
For senior ICs, tech leads, and engineering managers who want sharper judgment when systems and teams get complicated.
How to use it
Start at the beginning and read in order. Posts in this series also link to each other directly.
11 posts in this bundle.
Editorial pick
56 Laws of Software Engineering
An overview of the recurring laws and constraints that shape software engineering, from teams and estimation to architecture, testing, and performance.
Read guide
Read In Order
Follow the sequence
-
Part 1
56 Laws of Software Engineering
An overview of the recurring laws and constraints that shape software engineering, from teams and estimation to architecture, testing, and performance.
-
Part 2
Software Engineering Laws - Team & Project Management
The engineering laws that explain why teams, coordination, and project plans behave the way they do.
-
Part 3
Software Engineering Laws - Time & Estimation
The laws behind software estimation, uncertainty, and why deadlines slip even when teams are trying to plan honestly.
-
Part 4
Software Engineering Laws - Coding & Development
The software engineering laws that govern code quality, complexity, and the tradeoffs of day-to-day development.
-
Part 5
Software Engineering Laws - System Architecture
The laws that explain how systems evolve, why architecture drifts, and what makes technical structures hold up over time.
-
Part 6
Software Engineering Laws - Human Factors
The human-side laws of software work: motivation, cognition, communication, and the habits that shape team behavior.
-
Part 7
Software Engineering Laws - Quality & Testing
The testing laws that explain why quality is never finished, coverage is never complete, and tradeoffs matter.
-
Part 8
Software Engineering Laws - Risk & Security
The engineering laws that make risk and security inevitable design concerns, not compliance afterthoughts.
-
Part 9
Software Engineering Laws - Performance & Scalability
The performance laws that explain bottlenecks, scaling limits, and why more hardware is not a strategy.
-
Part 10
Software Engineering Laws - Metrics & Monitoring
The laws that explain why metrics get gamed, what monitoring is actually for, and how to measure without self-deception.
-
Part 11
Software Engineering Laws - Design & UX
The UX and design laws that explain how people actually use software and why intuitive products follow recognizable patterns.
Discovery Signal
Popular in this collection
Based on site visits from the last 12 months. This stays a secondary input behind the editorial sequence.
Software Engineering Laws - Team & Project Management
The engineering laws that explain why teams, coordination, and project plans behave the way they do.
Software Engineering Laws - Time & Estimation
The laws behind software estimation, uncertainty, and why deadlines slip even when teams are trying to plan honestly.
Software Engineering Laws - Coding & Development
The software engineering laws that govern code quality, complexity, and the tradeoffs of day-to-day development.