Why these principles matter
Suggest an editEach of the three design mistakes below has its own lesson in this course. In each of them no algorithm is broken and no library is misused, but the design ignores a principle that has a name and a well-known reason.
- A design that trusts a value the user controls becomes the security hole someone walks through. See The common-sense check and Thinking as a rational adversary.
- A component that remembers state it never needed becomes the thing an attacker corrupts. See What makes a system stateless.
- A convenience bolted onto the part that holds the assets becomes the reason a small change leaks them. See The core and periphery pattern.