01
Defaults Are Decisions: The Invisible Politics of Software Design
A default is not an empty state: it is a design decision that shapes security, privacy, behavior, and who must spend effort to choose something different.
↗
A default is not an empty state: it is a design decision that shapes security, privacy, behavior, and who must spend effort to choose something different.
Abstraction makes software easier to use by hiding detail, but the hidden detail does not vanish; its cost moves into libraries, runtimes, compilers, interfaces, debugging, or maintenance.
David Parnas's 1972 information-hiding argument changed modular design from a matter of grouping related steps into a discipline of concealing decisions most likely to change.