good system design can prevent a thousand papercuts. but the cost of fixing papercuts is going to zero, so the incentive for good design is too.
the papercuts still cause user grief. are we missing an incentive to prevent them? or is this the new way
a coding agent has no facial expression, so i have to infer “this repository is unusual” from the commands it runs
what do you routinely copy out of an agent conversation because you don’t trust yourself to find it again?
assigning an agent a task has made me appreciate how much context i normally communicate by pointing at a screen and saying “that”
terminal colors are fun because your carefully chosen gray might be someone else’s carefully chosen background
every settings page contains at least one checkbox whose consequences can only be learned experimentally
i want the program to remember my preferences with the persistence it currently reserves for remembering the wrong window size
a coding agent reading the readme before doing anything is setting an uncomfortable precedent for the rest of us

