Making software visible enough to argue with.
Presented at
- JSConf, Berlin, October 2022
Evergreens are ideas I've invested significant time into. They are refined, edited, and won't significantly change – aside from the occasional trimming.
Legible Systems
Making software visible enough to argue with
8 Backlinks
Design Tokens Are Social Contracts
The technical layer is easy. The agreement between people is the hard partQuiet Interfaces: Designing Software That Knows When to Shut Up
On notification fatigue, ambient signals, and the case for tools that respect your attentionCSS Is a Programming Language, and That Is the Point
Declarative systems reward a different kind of thinkingKeyboard-First Is a Culture, Not a Feature
Notes on who command palettes are really forLegible Systems
On making the invisible machinery of software visible enough to argue withCommand Palettes
Command bars you can summon from anywhere with a keyboard shortcutUndo Everything
Making every action reversible so people can explore without fearOptimistic Interfaces
Pretending an action succeeded before the server agrees, and recovering gracefully when it does notMentions around the web
3 Likes and Reposts
Adding this to the list of pieces that convinced me to stop posting to timelines first.
I disagree with the second half, but it is the useful kind of disagreement. Writing a reply post.
Did not mean to write a whole essay, but got on a roll. Corrections welcome.
This perspective really resonated with me today. Thank you for posting this.