Example · part of The finite reader
Two charting tools for the Python programming language can produce the same picture: a scatter of points with a trend line through it. In matplotlib, the general and powerful one, the book’s example takes a screenful of code, and every color, label and line is yours to set. In seaborn, built on top of it, the chart takes one line. Seaborn even adds a shaded band around the trend line that its authors thought you would want.
The short version is short because someone else already decided. For every option seaborn hides, its authors filled in a default on your behalf. Common charts become cheap and unusual ones move out of reach: a built-in tilt in what is easy, much as a notation decides which operations are easy. Few people master matplotlib. Many more can use seaborn.
The book calls this software stratification, its plainest picture of a trade it finds in many places: more options buy precision and narrow the audience. matplotlib plays the full version, seaborn the short one. The same curve shows up in church ritual, popular science and law, and the book traces it to how little time and background any user has.
Read the full argument
- Chapter 4: Optionality vs. Access, section “Software stratification”
- Chapter 4: Optionality vs. Access, section “What the curve is, and what it isn’t”
How it connects
- What it shows: Complex form, Compressed form, Cost of generality is accessibility, and vice versa
- See also: A Brief History of Time, Cost asymmetry, Defaults, Latin Mass vs. vernacular liturgy, Leibniz’s dy/dx and the British lag, Notation as a tool of thought, Statutes vs. plain-language legal summaries
- Where the book discusses it: Chapter 4: Optionality vs. Access
← Compressed form · The finite reader (6 of 14) · Latin Mass vs. vernacular liturgy →
Explore all the ideas · Read the book in order · Open the interactive map