There is plenty of "good naming vs. bad naming" content out there in developer circles. But the real jump is from no naming to naming. Ever had a conversation where a dev says "the thing that responds to the event ... " or "the code that checks that the credits are still valid

What good factoring/naming does is it rescales problems. It creates a bridge between a low level that is hard to talk about and a high level that is too big. People often treat naming/factorization as being about reuse (eg “patterns”). The ability to reuse is further downstream

If design is about solving problems, then a way to define taste is: the ability to *see* the problems.

The #1 thing that distinguishes an interaction with a very senior-level person (designer, developer) is the ability to have a conversation about the problems. Not just what to do, but what needs to be solved.

Love what I’m seeing in Remix 3. High-leverage simplicity.

AI transcripts tell you more about how the human works than how the agent works.