NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Pair Problems
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
XP: an amalgamation (Score:1)
I don't regard XP as a single, monolithic set of practices. All of its parts individually make sense, and they enhance each other, but I don't see a reason that they're all required during every phase of every part on every project. The single most important practice, in my observation (but not experience), is test-driven programming. All else is somewhat optional, or at least flexible, depending on the scope and size of the project and the rest of your methodology.
XP to me seems much like many assertions
Re:XP: an amalgamation (Score:2)
I definitely agree with the much of what you say, but I am concerned about XP in general. Pair programming is code review -> don't do too much refactoring without code review -> don't do the refactoring without tests ->don't write the tests without a clear understanding of the what the task is, etc. Pair programming is also knowledge sharing -> with knowledge sharing and more tests, we can write less documentation. XP seems to create certain chains of events that, if not properly understood,
Re:XP: an amalgamation (Score:1)
Again, the biggest issue is quite clearly test-driven development. Your coworkers do not seem to have understood why they should write tests. Consequently, they're seeing them as a burden, writing woefully inadequate ones to claim they're done. Inevitably, they have no courage to refactor cruft. It is all pretty obvious, if you ask me.
I really believe that once a programmer understands in his heart why test-driven development is A Good Thing, then all the other practices of XP will be understood effortles
Re:XP: an amalgamation (Score:2)
In fact, you can always practice test-driven development if you want to...
I turned down one Perl job because the man who interviewed me told me that he forbade programmers from wasting time writing tests :)
Re:XP: an amalgamation (Score:1)
Re:XP: an amalgamation (Score:2)
His reasoning was that writing tests meant that you were writing twice and thus were taking twice as long to get anything done. Since the process of debugging requires running the application anyway, that's where testing "should" be done. (No, I don't buy his argument either :)
Reply to This
Parent