The Shape of the System
Structure over vigilance: twenty-five tenets for engineering around the limits of human and machine cognition, building correctness into the shape of the system.
New here? Start at the front door. Five ways in, depending on why you came. Software gets read far more than it gets written. It gets changed more than it gets read, and then it runs in a world that fails partially, at the worst possible moment, usually while you're asleep. So build correctness into the shape of the system, not into the vigilance of the people keeping it going. Any rule you can only enforce by remembering it is a rule that will eventually get forgotten, and any defence you have to run by hand gets skipped the first time there's a deadline. The objective has two terms and…
saved by
related reading
- Engineering for Bounded Cognitionshapeofthesystem.com
- Everything I know about good system designseangoedecke.com
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- Cognitive load is what mattersminds.md
- Computers can be understood - Made of Bugsblog.nelhage.com
- How Complex Systems Failhow.complexsystems.fail
- Notes on Distributed Systems for Young Bloods – Something Similarsomethingsimilar.com
- Do the simplest thing that could possibly workseangoedecke.com
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- Things I believe · GitHubgist.github.com
- How To Do Lessalexturek.com