The latest expert opinions, articles, and guides for the Java professional.
Developer Productivity Report 2013 – How Engineering Tools & Practices Impact Software Quality & Delivery
Do you pair up? (programming, debugging, support, etc; ad hoc or policy)
For a page on wikiHow, this explains the benefits of pair programming remarkably fully:
“Some benefits you can expect: better code (simpler design, fewer bugs, more maintainable), higher morale (more fun!), shared knowledge throughout your team (both specific knowledge of your codebase and general programming knowledge), better time management, higher productivity.” http://www.wikihow.com/Pair-Program
While two-thirds (66%) of respondents pair up at least sometimes, one in three teams don’t.
Well, we see a significant increase in quality and a slight increase in predictability with pairing up. This is one place where we do wish we could measure productivity as well, as the main argument against pairing up is that two people separately can do more work. We can’t disprove that, but we can put numbers behind the increase in quality.
“Do you do code reviews?”
A solid majority (76%) of respondents review code for at least “Some commits”. Reviewing code has become more or less a standard practice for development teams. Only a tiny sliver of about 2% of teams do multiple code reviews for all commits.
The impact on predictability of releases is very high! However, the low effect on software quality is surprising. Looks like programmers are bad at spotting bugs in code, but good at spotting software design issues and code smells.
Leave a comment