When Smart Developers Generate Crappy Code 195
itwbennett writes "If you've ever worked on a team you can probably recall a time when, as a group, you produced work that was not as good as any one of you could have done on your own. Sarah Mei had this sort of sub-par teamwork experience, which she shared in her session at the O'Reilly Fluent Conference this week. Mei 'spoke about a time she worked on a team with really expert developers. Every one of them was someone whom you'd admire, who had previous written code that you and I would boast to have created. Yet, these smart people created modules that didn't talk to each other. And its quality was, to be kind, on the rotten side.' It's not an uncommon story, but why and how does it happen? The answer, says Mei, is that code quality 'is defined by its patterns of dependencies,' not all of which have equal weight. And, as it turns out, team communication is the heaviest dependency of all."
oh jeez; let's all discover agile again (Score:5, Funny)
Re:oh jeez; let's all discover agile again (Score:4, Funny)
Fix everything by having a 5 minute standup meeting for two hours every morning and then every two weeks drop everything and build a deliverable that isn't finished yet.
Re:oh jeez; let's all discover agile again (Score:5, Funny)
Re:the basement dwellers hate people (Score:5, Funny)
they want to sit in a corner far from other people coding in silence they hate meetings and talking to people
And with good reason. Other people are annoying and I am immensely interesting to me.
Comment removed (Score:5, Funny)