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.
  • Maybe you really are superior at maintaining a system like that, but FWIW in the systems I've worked on it seems to just be how things eventually end up. I probably just suck too, though. I would like to work in one of these mythical places where development is done sanely.

    For one thing, if he's like me, he probably doesn't have enough resources to able to carefully document and test things. I've heard the arguments before about how these things actually save time over the long run and blahblahblah, so I do

    • You do make a point, but this is a system that consists of only 53 files, counting all scripts, modules, sql files, etc.

      I've dealt with legacy systems that had thousands of modules, that had grown over the years, also with no documentation whatsoever, and it was nothing like this.

      While I agree that the lack of documentation and that kind of thing may not be his fault (but instead a product of circunstances), there are clearly a lot of things that are the product of a non-programmer creating code.

      Again, it m

      • This is me complaining about a specific system and a specific programmer and the discrepancy between his skills and the skills he claims to have.

        Ok, I guess you just hit a nerve with me. ;)

  • I know you didn't inherit my codebase, because I used source control. But the rest of it....
  • I think I've done every one of those at some time in my career, just not all in the same codebase. I probably did a quarter of them just yesterday. :)

    Well, okay, I don't think I've had a 500 character long, but I did have a period where I thought everyone should go back to the 132 character line printer width. That lasted like a month.

    • Yes, but I'm sure you weren't going around bragging how good you were.

  • You can either refactor, or drop it.

    Either way, this is what I would do first:

      1. create a repository for your project;
      2. import the project from the production server into a subdirectory: call it "old", "mess", or "omfg", I don't care;
      3. foreach part of the code that you refactor or drop, remove it from the old directory and commit to a decent organized place.

    At the end of the refactor, your old directory should be empty, but you can always go back in time and see what happened to ea

    --
    life is short