Leadership Garden

Software Engineering Laws

A practical sequence on the recurring laws and constraints that shape engineering work, from coding and architecture to testing and performance.

For senior ICs, tech leads, and engineering managers who want sharper judgment when systems and teams get complicated. 11 posts. Read them in order; each post links to the next.

Read in order

  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.

  2. Software Engineering Laws - Team & Project Management

    The engineering laws that explain why teams, coordination, and project plans behave the way they do.

  3. Software Engineering Laws - Time & Estimation

    The laws behind software estimation, uncertainty, and why deadlines slip even when teams are trying to plan honestly.

  4. Software Engineering Laws - Coding & Development

    The software engineering laws that govern code quality, complexity, and the tradeoffs of day-to-day development.

  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.

  6. Software Engineering Laws - Human Factors

    The human-side laws of software work: motivation, cognition, communication, and the habits that shape team behavior.

  7. Software Engineering Laws - Quality & Testing

    The testing laws that explain why quality is never finished, coverage is never complete, and tradeoffs matter.

  8. Software Engineering Laws - Risk & Security

    The engineering laws that make risk and security inevitable design concerns, not compliance afterthoughts.

  9. Software Engineering Laws - Performance & Scalability

    The performance laws that explain bottlenecks, scaling limits, and why more hardware is not a strategy.

  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.

  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.

Topics