Good CLI Design Is Mostly Silence

https://paulgraham.com/talk.html

In particular, the PG essay contains exactly one designed-to-be-quoted pat-yourself-on-the-back really-send-it-home-ism:

> Informal language is the athletic clothing of ideas.

This entire link is nothing but those. I don't feel like I'm being spoken to, let alone taught to. I feel like I'm being repeatedly poked with a finger that really wants me to know it has punchy ideas. Which backfires, ofc.

Every paragraph two lines long max.

It feels like it's treating the reader as unintelligent. It's like a hammer every sentence.

That's probably just Claude. I do enjoy finding new ways to call out the patterns it uses though.

A command is something I shout to an underling or my shell prompt. My shell interpreter takes my command, parses it and calls the necessary tool, be it a builtin or an executable.

I tell Tom to fetch the morning paper from the yard. Is Tom a command? No, Tom is my son.

Flagged as slop. What is the point of posting something like this if you can’t even be bothered to write it yourself?

holy slopperoni