3 ms·
What this typically means is the team lead thinks they're entitled to do the interesting work, like designing new features, exploring new ideas, and everyone el
by linuxftw 5y ago
What this typically means is the team lead thinks they're entitled to do the interesting work, like designing new features, exploring new ideas, and everyone else gets to fix the bugs and implement their half baked ideas. Then the developers push back, because no, we're just as capable as the 'team lead' and don't care what you think.
- dccoolgai 5y agoIn my experience, that's more likely to happen if the team lead _doesn't_ take an active role in defending the team's ability to do "interesting" work. I think the "do it all yourself" fallacy was covered in the article (which I found to be very well-written on the whole).