4 ms·
Wow thanks for the surprise in traffic this morning. Author here: I really wanted to illustrate the "why" it's frustrating. A more complete visual of what is a
by amozoss 5y ago
Wow thanks for the surprise in traffic this morning.
Author here: I really wanted to illustrate the "why" it's frustrating. A more complete visual of what is actually in my head.
Also I didn't get a chance to pull it out as much as I'd like, but I'm my own worst enemy when it comes to interruptions. So I broke my tips into 3 categories:
1. Protect against myself (2 tips)
2. Protect against day to day working cycle (1 tip)
3. Help teams work together to help each other (1 tip)
hence why I catered 2 of the 4 tips to myself.
- commandlinefan 5y agoAs I suspected, your post has brought a barrage of "deal with it" dissenters. This is as predictable as it is frustrating: the contrarians themselves seem to accept that an uninterrupted programmer is a better programmer and that an uninterrupted programmer will produce a better result - but they _still_ insist that we just deal with the (mostly unnecessary, non-value-add, easy to remove) interruptions anyway.
- amozoss 5y agoMy hope was that it would cause self reflection on what types of interruptions are causing us the most grief. For example, in tip 3, I realized I obsessively check my business metrics to the point where I could never lay the foundation of a focus tower. So I decided to put it in a red tab group in chrome to remind myself not to go there.
- MarkLowenstein 5y agoI liked your suggested mitigations. Well-designed to accommodate human motivation, and simple enough to be practical.