Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The whole point about XP isn't about tools, it's about process.

    You should test constantly and integrate continuously, whether you are using JUnit and Ant, prove and Make, Aegis, or scratch paper and a fleet of hamsters.

    You should be in constant contact with your customer, whether he is on site with the developers, teleconferences twice daily, video chats on demand, or retains a psychic to transfer thoughts through subspace telepathy.

    If you read between the lines in the XP literature, it's not about us

    • Microsoft Project style tools are precisely what I am trying to avoid. However, there are still benefits to a good XP project management tool.

      • It's easy for me to misplace a 3x5 card. Not so easy for the computer.
      • It's tough for me to restore an entire paper-managed project from backup.
      • If someone else wants to see what I'm working on, they can glance at my online cards rather than bug me.
      • If I want to know what I'm working on and I don't have cards handy, I can glance online.

      The primary benefit of XP is how it lowers the cost of information. A good tool can lower those costs even further. A bad tool, however, can raise those costs significantly and hurt XP style practices, hence my desire for find a good tool.

      • Understood.

        But moving away from 3x5 cards for these use cases seems rather, um, heavyweight. Reading what problems you want to solve, the one word that comes to mind is photocopier.

        If you've got a good 3x5 card process at the moment, making photocopies of what you're doing this week takes about a minute, and has very little impact on your workflow. Added cost to the team, maybe $5/year. Added cost to adopt some software automation? Well, depends on how long it takes you to retool your workflow.

        If,