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.
  • Clearly we should redouble our efforts to study the first steps of a software project!

    • As it happens, about a dozen of the books I culled where project management books. A few of the older ones extolled the virtues of Waterfall. There's been a lot of study on how to run software projects, much of it well-intentioned nonsense.

      I've seem many software projects doomed, or at best crippled, from the outset, either by silly management decisions or by inappropriate choice of methodology. Or by both ("We need this quickly, but we also want to be CMM Level 3 by the end of the year").

      Alas, software development will never be chess. So instead of always repeating the same classic mistakes, we get to add new ones.

      • I don't think any software project is doomed unless it's completely incapable of solving the customer's needs. That said, there are plenty of doomed projects.

        I'm more interested in the middle of the project, though. No matter how well you start, I think the more discipline and better communication you have when you're actually coding, the better your chances of success. I've been accused of being a cowboy, though, by starting to code so soon.