Laws of Software Engineering · Saying
Saying
The Map Is Not the Territory
Your model of the system is not the system.
How to use it. When the architecture diagram and production disagree, production is right. Update the diagram.
How it gets misused. Used to dismiss models entirely. Maps are useful because they are not the territory. They fit on a wall.
Related
-
Framework
Wardley Mapping
Plot the things your system depends on. Two axes: how visible they are to the user, and how mature they are. Watch how they move over time.
-
Principle
Observability
You cannot run, fix, or improve what you cannot see. Build systems that explain themselves.