3 ms·
That's the point. The "5 minute" disruption ends up with the team losing half a day of 'real' work. Tech leads seem to have it worst as they're expected to com
by muzani 2y ago
That's the point. The "5 minute" disruption ends up with the team losing half a day of 'real' work.
Tech leads seem to have it worst as they're expected to communicate but also write code. A common pattern is to be available 8 hours/day for disruptions like this, and then work 2-8 hours at night.
- codr7 2y agoIt's madness, most tech lead positions suck donkey balls.
- zmgsabst 2y ago> The "5 minute" disruption ends up with the team losing half a day of 'real' work. This has never been my experience across a decade of being an SDE — and this sort of hyperbole undermines your case. > Tech leads seem to have it worst as they're expected to communicate but also write code. Your numbers don’t align with (eg) Amazon’s definition of SDE, where SDE1s are expected to spend 4 hours a day coding (50% of time) and SDE3 (tech lead) only 2 hours a day (25% of time). They literally adjust their expectations to account for the increase in meetings.
- muzani 2y agoYou call it hyperbole then literally in the next paragraph say that SDEs are expected to spend 2-4 hours coding.