Series
Software Engineering Laws
For senior ICs, tech leads, and engineering managers who want sharper judgment when systems and teams get complicated.
A practical sequence on the recurring laws and constraints that shape engineering work, from coding and architecture to testing and performance.
11 posts in this bundle
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
- 156 Laws of Software Engineering6 min read
An overview of the recurring laws and constraints that shape software engineering, from teams and estimation to architecture, testing, and performance.
- 2Software Engineering Laws - Team & Project Management9 min read
The engineering laws that explain why teams, coordination, and project plans behave the way they do.
- 3Software Engineering Laws - Time & Estimation7 min read
The laws behind software estimation, uncertainty, and why deadlines slip even when teams are trying to plan honestly.
- 4Software Engineering Laws - Coding & Development8 min read
The software engineering laws that govern code quality, complexity, and the tradeoffs of day-to-day development.
- 5Software Engineering Laws - System Architecture7 min read
The laws that explain how systems evolve, why architecture drifts, and what makes technical structures hold up over time.
- 6Software Engineering Laws - Human Factors6 min read
The human-side laws of software work: motivation, cognition, communication, and the habits that shape team behavior.
- 7Software Engineering Laws - Quality & Testing6 min read
The testing laws that explain why quality is never finished, coverage is never complete, and tradeoffs matter.
- 8Software Engineering Laws - Risk & Security5 min read
The engineering laws that make risk and security inevitable design concerns, not compliance afterthoughts.
- 9Software Engineering Laws - Performance & Scalability5 min read
The performance laws that explain bottlenecks, scaling limits, and why more hardware is not a strategy.
- 10Software Engineering Laws - Metrics & Monitoring5 min read
The laws that explain why metrics get gamed, what monitoring is actually for, and how to measure without self-deception.
- 11Software Engineering Laws - Design & UX5 min read
The UX and design laws that explain how people actually use software and why intuitive products follow recognizable patterns.