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.
  • I don't know the exact details of the situation you describe, but in situations I have experienced that exhibit similar indicators, there has been a fear to rewrite/refactor. One of the syptoms of this has been the error of enforced duplication by "doing it right from here on in" (which for some reason, some people seem to think can be done effectivly without altering existing code ). Could it be that the codebase is growing brittle and the need to increase the team could be a symptom of a problem rather th
    • There is a fear to re-do anything, but it's a little bit different than that. When things reach a point where no one cares any more and my non-disclosure won't be a noose, I'll write about it...

      Yes, growing the team is a symptom.

      Thank you for your comments...


  • The number one thing to realize is that an average team of 5-7 people has a throughput that matches a team of 20 people. So there is a big productivity drop chasm that you don't want to stumble into by accident.

    If you need a cite, read Software Estimation by Steve McConnell. (I forget where in the book the tidbit is, but the whole book is good so you should read it anyways.)