Programmer Interrupted
Research shows the devastating effect of interrupting developers: 1. 15 min is required to resume work; 2. A programmer get just one uninterrupted 2-hour session in a day; 3. Worst time to interrupt: during edits, searches & comprehension.
- from
- Engineering Team Management
- added
- 2026-10-10
- likes
- 0
similar
-
Psychology Today: How Programmers Can Avoid Burnout psychologytoday.com
“Veteran software developers often recommend to: 1. Work at a place where you can grow; 2. Build transferable skills; 3. Have creative outlets and create a space to focus on yourself, switch off, and relax; 4. Of course, there's always the nuclear option: make your money and…
-
The art of destroying software youtube.com
Greg Young described a good way to deal with requirements volatility: optimize from the beginning to be able to delete your code, and structure your code so that any part of it is no bigger than 1 week's worth of coding. So that any part can be re-written in 1 week.
-
The Intangible Skills You Can't Interview For staysaasy.com
“1) Cut-Through on Crappy Tasks; 2) Knowing How to Finish; 3) Knowing How to Start; 4) Giving (And Receiving) Diagonal Feedback; 5) Harnessing the Value of Intangibles.”
-
How To Prevent Or Recover From Developer Burnout actitime.com
By Anastasia.
-
-
Strategies for long Projects benbrostoff.github.io
Relentless, irrational optimism; Daily progress documentation; Compounding investments; Time budgeting.
Engineering Team Management › Cognitive Tools > Behavioral: “Research shows the devastating effect of interrupting developers: 1. 15 min is required to resume work; 2. A programmer get just one uninterrupted 2-hour session in a day; 3. Worst time to interrupt: during edits, searches & comprehension.”