3 ms·
I've never done it but it sounds horrific to me, and also incredibly wasteful to have 5 people all just working on one bit of code. It's like you've single-thre
by anentropic 5y ago
I've never done it but it sounds horrific to me, and also incredibly wasteful to have 5 people all just working on one bit of code. It's like you've single-threaded your team. Surely they don't do this all the time?
- sdoering 5y agoI would not do it all the time, but I imagine one benefit could be that the whole team is on one page, when it comes to a central complex part of the application's logic. Everybody is invested as everybody had (probably) their say and was part of the decision. Institutional knowledge is high across the whole team. This for the cost of single threading the team. It is a business call and might be a valuable and valid approach in some cases. I think it is a tool. A tool with a specific problem it solves. And if you use it all the time you are the worker that only has a hammer so that every problem looks like a nail (not you personally, but generally speaking). Being a data analyst I remember great sessions of pair and team analysis of a specific data problem. Some sucked and were unproductive but most were great if facilitated well.
- anentropic 5y agoI can certainly see that, as a tool to use occasionally for critical, complex bits of the system. Or even as a team-building exercise. I had the impression some are advocating it as a default way of working though, and that seems so alien to me