3 ms·
Conversely, get better at handling interruptions. In almost every non-junior role (not just "manager") you will be required to deal with many things throughout
by lxe 7y ago
Conversely, get better at handling interruptions. In almost every non-junior role (not just "manager") you will be required to deal with many things throughout the day, coding being just one of them.
- rch 7y ago> almost every non-junior role To me, this sounds far from being universally true. Some Sr. roles allow for hard-split meeting days vs. productive days, and moving to six week self managed "sprints" with regular updates to a draft publication instead of shuffling vaguely defined tickets around a board.
- kraigie 7y ago>Some Sr. roles allow for hard-split meeting days vs. productive days Such as?
- jbeninger 7y agoI'm not sure "get better at handling interruptions" is possible. If I'm juggling a dozen ideas in my head and am interrupted, that tower is going to crumble regardless. If you're suggesting I rebuild my methods of developing from the ground up to avoid that mindset, that's a huge ask. I'm not convinced it's even possible. I'm able to muddle through a task with regular interruptions, but I'll be more likely to make mistakes and it will take longer. There's a world of difference between what I accomplish in an "office" day vs a "coding" day. I think the article has it right. Dedicate some "office hours" to being interrupted, but recognize that some people are far more productive during long uninterrupted periods.
- afarrell 7y agoAny tips on how to do this?