In response to a tweet by Esther Derby, I’m left contemplating the relationship between developer competence, methodology and success.
Michael Hill has produced a lovely essay about how TDD and Pair Programming ensure that the internal quality of your code doesn’t cost you in future productivity.
Another very compelling example of the benefits of pair programming.
You’ve never done agile before and you work on a legacy system which is extremely fragile and bug-ridden. I’m guessing quite a few developers will be able to identify with this scenario. Does this mean agile is a no-go? On the contrary, applying agile techniques will probably make it easier to fix those bugs, faster and in the process improve the code just a little bit.