9
7 Comments

Why interruptions are frustrating to developers - a deep dive

submitted this link to Icon for group Productivity
Productivity
on May 27, 2021
  1. 2

    Interesting post! I Will definitely share it with my team.

  2. 2

    Very good piece, thanks for sharing it :)

    1. 1

      Thank you! I appreciate that 😊

  3. 2

    Good piece.

    It wasn't until I had to code full-time for a few months that I finally got the difference between the depth of concentration I needed to run a marketing operation versus the level needed to build a complex Rails app.

    Still haven't managed to explain the difference to my co-workers in a way that they get, though...

    1. 2

      Thanks so much!

      Maybe bring in a deck of cards and have them build a focus tower 😊.

      I was hoping with the extra visuals the article might appeal to non developers, but I got a bit carried away explaining the layers.

      Could maybe send your coworkers my Twitter thread, it's a pretty good summary.

  4. 2

    Nice! I was expecting a fairly standard article about "Do no interrupt programmers", but was pleasantly surprised to find this a really thoughtful article with some great tips to maintain 'flow' state!

    1. 2

      Thanks so much Devan! Ironically, someone said that exact phrase with my article from a month ago 😅.

      Guess I need to work on my titles a bit :)

Trending on Indie Hackers
I built an AI that turns an idea into a live business in under 10 minutes. Here’s what 1,000 launches taught me User Avatar 90 comments Stop losing deals in the gap between "sounds good" and getting paid User Avatar 50 comments Building a startup costs $0. Your tooling budget costs $500K. Here's why. User Avatar 45 comments Building Noodle, a keyboard-first REST client for the terminal User Avatar 34 comments "Looks Good to Me" Is Quietly Killing Your Feedback Loop User Avatar 33 comments 787 tools for developers. 5 for nurses. Two weeks of tracking 14,000 indie launches. User Avatar 30 comments