One screen to rule them all

As a late Gen-Xer, my wet dream was always the bridge of the Enterprise: a wall of screens, controllers, and blinking metrics glowing in the dark. We operated under a premise we now know to be false: "One more screen will make me more productive." We believed that more glass surface area equaled higher mental processing speed.

The reality hit me hard. By filling my desk with devices, I didn't multiply my performance; I multiplied my windows for distraction by four. Every monitor was an open invitation for an email, a log, or a Slack message to assault my focus without permission. Today, my limit is two screens for operational tasks and one single screen for deep work.

Here is why you should start closing tabs and turning off monitors.

1. The Slack Black Hole

Keeping messaging apps open is working in a state of perpetual interruption. In small teams, it’s manageable; in large organizations, it’s professional suicide.

• Manage expectations: Turn off notifications. Establish blocks (e.g., 50 min focus / 10 min management). Use your Slack status to indicate when you’ll be back. Respecting your own time teaches others to respect it too.

• Asynchronous protocol: Don’t just send a "Hi" and wait. It’s inefficient and creates anxiety. Write the full context, the request, and the urgency in a single block. If it’s too complex, ask for a brief sync.

• Public by default: Avoid DMs for technical doubts. Use channels. Don’t burden a single person and ensure the solution is indexed for the rest of the team.

2. The Monitoring Mirage

Unless your job is strictly as a SOC operator, you don’t need to watch Grafana charts all day. If the service crashes, a screen won’t save it; a good alert will.

• Automate surveillance: Spend time configuring precise alert thresholds. If something needs your attention, your phone or critical notification system will let you know.

• Ritual reviews: Set a specific time—morning coffee is perfect—to check dashboards, triage errors, and plan fixes. For the rest of the day, close the tab.

• Zero dependencies: Evangelize your peers so they can interpret metrics. Being the only one "watching the screen" makes you a bottleneck, not a hero.

3. The Git Graph Aesthetic Trap

It’s undeniable: a Git tree full of colored branches on a vertical monitor looks amazing for an Instagram photo. In practice, it’s usually a symptom of a broken workflow.

• Trunk-based development: If you need an entire screen to understand your branches, your branches are living too long. Move to short integrations and minimal lifespan. Less visualization, more continuous integration.

• Trust your tests: If you’re tracing the graph to find where something broke, you’re missing unit and integration tests. TDD is the best tool to stop staring at the commit tree.

• Code is not a diary: Use Jira, Linear, or Notion for task tracking. Don’t try to reconstruct the product’s history through commit messages.

4. The Multimedia Screen: A Symptom

If you need Netflix or a dense podcast in the background just to get through the day, you have a problem that an extra screen won’t fix:

• Repetitive tasks: If the work is so boring it requires distraction, automate it. Don’t settle for being a robot that consumes content.

• Lack of purpose: Sometimes, the need for "noise" is a sign that your work no longer motivates you. Listen to yourself.

• Guilt management: If you simply can’t wait to watch the season finale for fear of spoilers, stop for 50 minutes, watch it, and return to work with a clear head. Multitasking with entertainment only guarantees you do both things poorly.

Definitive Do's and Don'ts

• Don’t multitask in meetings: If you can work while others talk, you shouldn't be in that meeting. Leave and reclaim your time.

• Code reviews on one screen: If a PR is so large you need three monitors to understand the context, the PR is too big. Break it down.

• The learning exception: Use as many screens as you need when studying or doing Front-End work. Seeing changes in real-time while consulting documentation is a legitimate use of hardware.

exit(0);