Skip to content

Navid's Blog

Ideas, Experiments, and Lessons Learned

Menu
Menu

The Simple Fix for Context Switching That Actually Works

Posted on March 18, 2026 by Navid

I’ll be honest — I used to think context switching wasn’t a big deal. “Just switch tasks,” I’d tell myself. How hard can it be?

Then I looked at my calendar and realized I’d jumped between 7 different projects in a single day. And accomplished basically nothing.

What Context Switching Actually Costs

Here’s the thing most developers don’t realize: it’s not the switching itself that’s expensive. It’s the reset time.

When you move from debugging a payment bug to answering a Slack message about the dashboard, your brain doesn’t just “switch.” It has to:

  • Unload the current mental model
  • Find where you left off last time
  • Load the new context
  • Actually start working

Research shows it takes about 23 minutes to get back into deep work after an interruption. Twenty-three minutes. Multiply that by however many times you check your phone or respond to “quick” messages.

What Actually Worked For Me

I tried everything. Time blocking. Pomodoro. Do Not Disturb mode. The thing that finally clicked was way simpler:

Theme your days, not your hours.

Instead of splitting my day into 1-hour chunks, I now assign entire days (or half-days) to specific work types:

  • Deep Work Days — No meetings, no Slack, just coding
  • Communication Days — Code reviews, standups, planning
  • Learning Days — Reading docs, experimenting with new tools

This sounds obvious when I say it out loud. But changing from “I’ll do 2 hours of this, then switch” to “Today is for this only” made a massive difference.

The One Rule That Made It Stick

Here’s the secret: I don’t let myself check email or Slack before 10am. Never. Not even “quickly.”

Those first 2-3 hours are when I’m sharpest. Using them for shallow work was my biggest waste. Now I protect that time ruthlessly.

Does This Mean Never Multitask?

No. Sometimes you have to context switch — emergency bugs, team dependencies, whatever. But the goal is to make that the exception, not the rule.

Track it for a week. Every time you switch contexts, write it down. You’ll probably be surprised by how often it happens and how little you get done.

The Bottom Line

Theme your days. Protect your mornings. Stop pretending you can deep-work in 30-minute chunks between meetings.

It took me years to figure this out. Hopefully, it’ll take you less time to try it.

Categories

  • AI Experiments
  • Coding
  • Debugging Stories
  • Hot Takes
  • Ideas
  • Lessons Learned
  • Project Management
  • Uncategorized
  • Vibe Coding

Recent Posts

  • How I Handled My First Production Outage (And What I Learned)
  • I Finally Fixed Our Slow Database Queries — Here’s What Actually Worked
  • I Finally Fixed Our Slow Database Queries — Here’s What Actually Worked
  • Why I Stopped Using Microservices for Small Projects
  • I Gave AI Full Access to Our Production Database. Here’s What Happened