Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • The Aegis software management tool has been around for a long time [], but I strongly suspect that part of the reason it never became very popular is because it enforced a particular belief on users. For example, your code is always in one of multiple stages and for the "being developed" state, you cannot check in unless you have new tests and your code must pass those tests. There are numerous other states and numerous other preconditions which developers much satisfy before they can move the code to the next state and integrate it.

    Or I can check out my code, change it, check it in.

    Ultimately, we all know which we'd rather develop on, even though many of us might find it tempting for force developers to have tests.

    By insisting upon a numeric plan:

    • We ignore that there might be other equally valuable ways of accomplishing the same task.
    • We possibly put others off with our dogmatism

    Me? I'm laid back about this issue now. I know most developers aren't going to sweat things too much and many detest and mistrust evangelism. That's OK. Find other ways to bring them into the fold.

    (And for all of my arguing about an iteration count being off and that's why I need a plan, I've discovered that this happens so seldom to me that I was arguing a use case I rarely had. If later it turns out to be a bug, I'll add a test for it. Your mileage may vary.)

    • Are we talking about organised religion or programming? I find the language in your last couple of comments… creepy.

      • The religious allusions were deliberate. The dogmatism of those who insist that we "must have a plan" put people off in the same way that dogmatists for anything will put off certain parts of the population. I don't care for dogmatism because it's often a fancy word for "we think we understand this, so we don't need critical thought". Since dogmatism is often accompanied by a near religious fervor, I thought it was OK to continue with the metaphor.

        Sorry if I was a little too zealous in that. Obviously i

        • You lost me when you started talking about bringing people into the fold and such. I want to teach trade-offs and how to weigh them, not convert people to a doctrine – any doctrine.

          • My apologies. I meant that strictly as tongue-in-cheek. I should hope that that those who know me would appreciate the irony of me using religious allusions. I'm not serious, dude :)

    • We've never insisted on a plan, you just had to explicitly say that you didn't have one.

      What I'm seeing now is the opposite, you (and others) seem to be actively encouraging people to NOT use plans. Or at least, that is the impression I get.

      People have never HAD to use DBI placeholders either, but the default documentation comprehensively refers to it.

      • Not using DBI placeholders is far more serious than not using a plan. It's can leave you wide open to serious security holes. Lack of a plan, however, while risky, is far less risky.

        When I'm moving, my friends and I are carrying stuff into my house and I leave the door unlocked. I lock the door when I'm done. Similarly, when I write tests, I set them as no_plan and add the plan when I'm done. What I want to do is minimize the accounting when writing tests and when the developer is done, they lock the d