4 ms·
The question there is why you're operating using teams of 5 devs. The most productive environments I've worked at were ones where single devs had ownership over
by ajb 3y ago
The question there is why you're operating using teams of 5 devs. The most productive environments I've worked at were ones where single devs had ownership over a chunk large enough not to require that much interaction (IE an amount of interaction that you would contemplate between teams, not between devs on a team)
The issue with that is that you have to eat a big handover cost when people leave. But these environments had great retention and long contractual notice periods, so it wasn't a huge issue.
IMO the "two pizza team" isn't as productive as people think.
- throw_nbvc1234 3y agoHow did oncall/operations work?
- ajb 3y agoThe companies where I worked like this didn't run services, they shipped releases. Which is how open source stuff generally works, although the income part can be a service (but not always)
- palata 3y agoI am in a company where most of us are "experts" of one part of the system. This is very stressful (because when there is an emergency related to my part, I am the expert on whom management is waiting), annoying at times (because nobody cares about my part, they have their own stuff to do, so it's hard to share), painful at times (when I'm struggling, I don't really have colleagues who can help), and annoying again when someone is on holiday and we need a change in their part. Agreed on the handover cost, though (obviously). Not saying that 5 devs are required, but 1 is not always the nicest IMO.
- ajb 3y agoFair comment - I'm not saying it's a panacea. Just that it's productive.
- pixl97 3y agoHaving one person that knows everything about some system is great, until they get hit by a bus.