Why the Terminal Wins
This is a member-only chapter. Log in with your Signal Over Noise membership email to continue.
Log in to readModule 1 · Section 2 of 6
Why the Terminal Wins
It’s not about being a developer. It’s about where your attention lives when you’re doing actual work.
If you’re already in a terminal building something, switching to a browser tab breaks the context. You lose the thread of what you were doing, spend a few minutes trying to summarise it for LinkedIn, produce something mediocre, and close the tab feeling vaguely dissatisfied.
If posting is a command — something you run in the same environment where the work happened — you don’t break context. The work and the post about the work are in the same place. The friction drops enough that you actually do it.