The Case for a Second (or Third) Monitor — a Real Productivity Argument, Not Just "More Screen"
The argument isn't that more screen is inherently better — it's that switching windows costs more than switching monitors, and orientation matters as much as count.
I run three monitors at my home setup, and between five and seven at work depending on what I'm actually working on that day. At this point there's no realistic way I'd go back to working with fewer than three — not because more screens are inherently better, but because of what having them actually removes from my day.
The real cost being avoided is context switching. Every time a single-monitor setup forces you to alt-tab or cmd-tab between a reference doc, a ticket, a chat thread, and the code you're actually writing, you pay a small tax: finding the window again, re-locating your place in it, re-loading whatever you were mid-thought about. That tax is small per switch, but it adds up fast across a full day of real development work, where those switches happen constantly.
What a second or third monitor actually buys isn't "more room" — it's the ability to keep reference material, logs, or a ticket visible at the same time as the code, so the switch is a glance instead of a full window change. Debugging is the clearest case: a stack trace or log output on one screen while stepping through the actual code on another beats tabbing back and forth between them every few seconds.
Orientation matters as much as raw count. I run some of mine in portrait, specifically for long spreadsheets and other content that scrolls vertically rather than needing horizontal width — a landscape monitor forces constant scrolling through something that's naturally tall, where portrait shows most of it at once. The same logic applies to reading a long log file or a long document: matching a monitor's orientation to the actual shape of what you're looking at is as real a productivity lever as adding another screen in the first place.
The case does get weaker past a certain point. More screens add setup complexity — cabling, a dock or GPU with enough outputs, desk space — without a proportional return, and window management across many displays becomes its own minor discipline. The right count is the one that actually removes context-switching for your specific workflow, not a number to maximize for its own sake.