The way I think of it, there are two sessions a day of doing difficult coding work, before and after lunch. Maybe 3 hours each. If you interrupt one of those b

The way I think of it, there are two sessions a day of doing difficult coding work, before and after lunch. Maybe 3 hours each. If you interrupt one of those blocks, you can't do "difficult coding work", but you can communicate with people, document your code, and organize. The easy work can take up a lot longer, it's just not part of the block, and interrupting the block means you don't have that block. Organizing means simple stuff like moving pieces around to where it makes sense to have them, simplifying well understood issues, and automating parts of the build. By difficult work, I mainly mean exploratory coding work, where you write new code, see if it compiles, and whether it does what you expected. Or you are debugging something that's broken and following various hypotheses about what might be wrong. Once you've either written the new piece or discovered the bug, you can spend time doing "organizing", where you know the answer, but you just need to spend the time moving stuff around. I'd be lucky to have a block each day.