4 ms·
Team-playerism is an attempt to do for developers what RAID does for storage or the cloud does for compute. It is an attempt to simulate a great programmer with
by bitwize 4y ago
Team-playerism is an attempt to do for developers what RAID does for storage or the cloud does for compute. It is an attempt to simulate a great programmer with a redundant array of good programmers, and get more reliability out of the deal. (Great programmers are highly sensitive to their work environment, and the more scrupulous ones will quit when they aren't getting the work conditions, respect, or compensation they feel they're entitled to for their work. The less scrupulous ones will sabotage your company from the inside, or sprinkle backdoors in to sabotage it from without once they've left.)
It never works, of course. Insights come from individuals, not collectives, and while having similarly skilled colleagues to bounce ideas off of and refine them with works well for great programmers, they have to come up with the ideas themselves in the first place. The communication overhead in a team of good programmers prevents them from having great-programmer insights at great-programmer speeds. The way to fight communication overhead is to ensure that each team member has a large corpus of shared information. In other words, a shared, standardized coding style which further hampers insight because insightful solutions have little regard for "the rules".
But most companies just want CRUD+business rules, so RAID (Redundant Array of Intransigent Developers) works well.
- CRConrad 4y ago> Insights come from individuals, not collectives, and while having similarly skilled colleagues to bounce ideas off of and refine them with works well for great programmers, they have to come up with the ideas themselves in the first place. Bouncing insights off each other in a team might lead to someone else taking up and working on something that to the originator was just a fleeting side idea in a train of thought, but can turn out to be valid on its on / viewed from a slightly different angle / in a slightly different context. Whereas if the individual works entirely on their own, valid ideas / insights may be forgotten and fall by the wayside forever. (Personally I probably tend more towards the solo side, but have to admit there are advantages to teamwork too.)
- galaxyLogic 4y agoProgramming is essentially mathematics. Imagine if mathematicians were required to do pair-proving. Pair- programming is a case in point. It emerged from "Xtreme Programming" which emphasized "values" and "people", not problem solving skills. So why didn't they go further and require "triple programming", then "quatro programming" and so on? The way to tackle complex problems is by divide-and-conquer: Divide the problem into smaller parts which can be solved independently. Pair-programming is not that, it doesn't divide the problem into two and then let each programmer work on one part of it individually. Instead there's a pair of chefs in the same kitchen team-cooking the same spaghetti. To put it bluntly I think people who demand "team-players" are typically those who don't have the skills to solve any part of the problem by themselves. By building a team around them they can hide that fact. If the project fails it is nobody's fault, the whole team did their best and still it couldn't succeed. We followed the best agile practices you know. Or maybe it succeeds, because of a few good men and women. (Successful) team-playing is when each team-member plays their part, not when they all play the same part. Think volley-ball, that's a great team-sport.
- kaczordon 4y agoUmm pair programming is literally how Jeff Dean and Sanjay Ghemawat code. MapReduce and Spanner are just two of their creations… Article on them here: https://www.wired.com/2012/08/google-as-xerox-parc/ https://www.wired.com/2012/08/google-as-xerox-parc/
- galaxyLogic 4y agoThe question remains: If pair-programming is so great, wouldn't triplet programming be even greater? Why not? Or why not "take it to the eleven"? Eleven programming. Why is 2 the answer? Why not 42? I can see that pair-programming can help in some situations like getting new team-members up to speed. But I question those who say it should be applied universally, always, as a general rule.
- erik_seaberg 4y ago“Mob programming” is a thing some people do; I don’t get it. https://news.ycombinator.com/item?id=30383382 https://news.ycombinator.com/item?id=30383382