Collaborate, but only intermittently, says new study
sciencedaily.com
sciencedaily.com
I've got a more detailed comment on that page, but, in a nutshell, I don't think one can reasonably extrapolate these results to a business setting.
I'll go a step further here and say that I see this Science Daily article as a great example of questionable science journalism. Critical details left unmentioned, wild extrapolations, all that fun stuff.
This kind of nonsense is what I like to call anti-knowledge. It tangles our decision making and it'd be better if it didn't exist at all.
Of course, this is just a 1st. person anecdotal claim, so it certainly does not extrapolate anywhere.
It makes the cynic in me want to say that the real take-away here is that greedy search is more likely to get caught in a local optimum in a problem where the search space is not convex.
It's also worth pointing out that, to achieve P<0.05 on their main result, they had to run a LASSO regression with cross-validation. IMO, that counts as P-hacking.
On befriending everyone and getting drunk one day, i asked them why don't you talk more at work?
They said, it's due to bad previous experience where they opened up and got attacked. Now, they only plan to speak when absolutely necessary otherwise, just solve the tickets assigned to me and i go home.
We talk about doing pair programming or something in the next release, then we all go back to our respective stacks of work and don’t feel like we have the time to collaborate on anything, unless it’s a question for someone who knows a part of the codebase better.
I know you didn't ask for advice, but perhaps code-review and design-review is actually all your team needs? i.e. instead of the constant collaboration of pair programming, you work on slightly lighter weight interaction by having pairs of people work on closely related projects code-reviewing each other and having times where they bounce ideas off each other, but who ultimately work alone till they produce something the other can see. A half-day boundary of interaction (non-formalized of course) may be sufficient to allow for the degree of collaboration to be fruitful.
This happens and fosters groupthink and prevents critical thinking and creativity.
When a whole team (or company) comes up with a poorly designed product this is often the reason.
You can fight this by talking about the problem, encouraging constructive criticism, engaging with communities and other social groups, gathering anonymous feedback from other teams.
http://freakonomics.com/2011/09/29/the-myth-of-common-sense-...