2 ms·
> every developer in the team should be able to do all tasks I hate this. People have strengths, even if they’re all technically backend / frontend / whatever.
by sgarland 3y ago
> every developer in the team should be able to do all tasks
I hate this. People have strengths, even if they’re all technically backend / frontend / whatever. Should you have more than one person who can perform a given task? Ideally yes, but let’s not pretend that Alice isn’t objectively better at SQL than James, but worse at async functions. Let people do what they’re best at, and enjoy the most.
- bee_rider 3y agoI could see why management wouldn’t want to do that. By not getting Alice some practice on async functions, aren’t they making the team more fragile? Everything in moderation of course, but the team wouldn’t want to start leaning on each other’s specialization to the point that it all falls apart if somebody quits.
- pooper 3y agoI would love it if we were all "cross function" but that comes at a cost of reduced velocity. First of all, a manager shouldn't be side channel dm his reports questioning the estimates/story points the team collectively decided at all but in this situation you have to live with reduced capacity forever if you want everyone to be a jack of all trades. Management wants to have its cake and eat it too. I feel like if you object to an estimate, you must have to do the task yourself with the reduced estimate. This falls flat because I suspect my manager has ZERO programming/qa/development or even business analyst experience. Just my personal opinion that if you think the estimate is wrong, you should take the task yourself and do it in less time or shut up. You know how we talk about developers not able to do fizzbuzz with ten years' experience? I suspect he is whatever the equivalent of that is for managers.