Why interruptions cost programmers dearly
Summary
Chris Parnin visualises the complex mental state that is built up while programming and partly destroyed by interruptions. A well-known illustration depicts the programmer's state as a network. The article distinguishes between working and getting back into it.
Ideas
- Programming keeps goals, assumptions and dependencies in working memory at the same time.
- An interruption pushes out parts of this short-term state.
- Getting back requires reconstruction from code, notes and tools.
- Visible focus times reduce avoidable context switches.
Insights
- The cost of an interruption depends more on the depth of the state than on the length of the conversation.
- Team communication needs shared rules for urgency.
- Notes turn a fleeting state of mind into recoverable traces.
Recommendations
- Bundle non-urgent questions into fixed time slots.
- Leave a concrete next step before breaks.
References
Links to the original source and the Web Archive open in a new tab.