The Discipline That Atrophies the Escape Hatch
Keeping a tmux session under ten windows is a discipline. Learning the window picker that lists and jumps to any of them is a skill. The discipline is cheaper, right up until it isn't.
Discipline that keeps you under a threshold is a real optimization in the moment. It costs nothing to maintain, no new keybinding to learn, no menu to navigate, no awkward pause mid-task while you remember the command. You just don't let the window count hit eleven. You close a tab before the second row forms. The discipline is invisible, which is the appeal: it looks like a good habit instead of what it actually is, which is capability you never built, sitting unused, waiting to matter.
The discipline and the skill aren't two paths to the same outcome. They pay out on different schedules. The discipline pays every single day, in small real savings: one fewer thing to think about, one less tool to carry in your head. The skill, once learned, pays rarely but completely, on the one day the limit breaks anyway. You can't swap between the two at will, because by the time you need the skill, the discipline has spent months or years making sure you never touched it.
That's the actual cost, and it's compounding. Staying under the threshold doesn't just avoid needing the escape hatch, it prevents you from ever practicing the escape hatch. Every day the discipline successfully intercepts the situation, your fluency with the real tool gets a little more theoretical. You read the keybinding once, maybe bookmark it, and it never loads into muscle memory, because the whole point of the discipline was to make sure the triggering moment never arrived. Unused procedural knowledge doesn't sit there neutral. It rots at a steady rate, and nothing resets the clock, because resetting it would mean doing the thing the discipline exists to prevent.
Then the threshold breaks anyway, because the world doesn't respect your budget. A frantic debugging session spins up more panes than you planned for, or a project running behind schedule needs more juggled at once than your ceiling was built to allow. And here's the part that only shows up once, at the worst possible time: you cross the threshold at the exact moment you're least equipped to have crossed it. You need the picker for the first time in a year, under pressure, with no fluency, fumbling through a command you half remember exists.
That's worse than never having learned the skill at all. A beginner who's never touched the picker at least knows they don't know it, and goes looking with appropriate humility. Someone who learned it once, used it twice, then spent two years under a self-imposed ceiling has false confidence instead. They remember that there's an answer, just not what it is anymore. The discipline doesn't only starve the skill. It erases the memory of how hard the skill was to pick back up, so you walk into the moment it finally matters assuming it'll come back to you. Often it doesn't, not fast enough.
This isn't a case against discipline in general. Staying under a threshold is frequently the right call, calmer and cheaper and less to carry around. The real claim is narrower: discipline that works purely by avoidance is quietly betting the threshold never breaks on a day you can't afford to fumble. If the threshold is fully in your control, close the tabs, keep the pile small, the bet is fine. If the world gets a vote, a failure under load, a dependency finally hitting its ceiling, a system finally outgrowing your habits, the discipline stops being risk management and starts being risk storage, with interest due on a day you don't get to pick.
The honest fix, if you expect the threshold to break eventually, is to cross it on purpose now and then, just to keep the escape hatch from seizing up. It costs a sliver of the savings the discipline exists to protect. That's the fee for not being the one fumbling through a half-remembered menu on the day it actually counts.