Game programmers break down how interruptions impact their work, and how to get back on-track
Having your work interrupted is bad. Everyone knows that. But Chris Parnin of Gamasutra took the time to analyze 10,000 programming sessions and survey more than 400 programmers to bring us this cohesive, scientific study of how interruptions impact our work, why it does, and what we can do about it. Try some of his memory exercises yourself and see how they impact your workflow.
We often talk about the big issues that impact game development - high financial costs, the toll on a life outside work, complicated relationships with publishers - but we rarely get a glimpse this thorough at the minute details that can have a big impact on how the work gets done.