XP is the only methodology I've used that gave direction on what programmers should be doing. Most methodologies have plenty to say on what happens around the p

XP is the only methodology I've used that gave direction on what programmers should be doing. Most methodologies have plenty to say on what happens around the programming, such as planning and design, but when it comes to producing code---the entire point of the exercise---they treat it as a black box. I don't think XP is the final word on programming, or necessarily even good in all its suggestions, but I think it's worth knowing just because it tries to tackle the most important part of software development.