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.
  • 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 don't need a lecture. But if you don't have enough people to deal with all the business demands and bug fixing, at some point you start to be the one who is getting in the way, and then it's you who are the idiot who needs to be removed. And no matter how well you try to document what you do, if there are other people working on things and they don't document what they do, and people come and go in your company, and have diverse skills and motivations, then that tacit knowledge [] erodes over time.

    And users don't ever know what they want. So you make any system, regardless of how elegant and clean it is, you end up making little compromises to accomodate this or that thing that popped into somebody's head and is suddenly a very important thing to have. Or otherwise, if you try to keep your precious system immaculate, you're just getting in the way and need to be removed in order to get things done. Or if your system is sufficiently decayed, you look stupid because something that should be ridiculously easy to change is not unless you add yet another dirty hack. [bah, I'll stop here arbitrarily]

    • 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. ;)