A long, interesting and entertaining post. Remember... processes, methodologies, or technologies don't kill projects....People Do!
http://steve-yegge.blogspot.com/2006/09/good-agile-bad-agile_27.html
I do have a problem with Steve's statements about pair programming. When I first heard about Pairing, I was skeptical and didn't any first hand experience. After experiencing it, I noticed these benefits:
1. Coding standards are spread through out a team without the needs for exhaustive standards docs and painful code review meetings.
2. It leads to better design. Think about each time you've written code that didn't feel "right". Did you ask someone about it, or was it discovered in a code review? Probably not! With pair programming that doesn't fly. The two of you will have a quick discussion and come up with a simpler design and cleaner code.
3. It's faster! Unfortunately, this is very difficult to prove, but my experiences with pair programming have produced more features; quicker and with better design and fewer defects.
posted @ Thursday, September 28, 2006 6:51 PM