in reply to Rewriting a large code base

HAHA,

Lucky git. You can rewrite the application :) I just have to write new specs on a application like you are telling.

So I have to life with such a application and don't get permission to rewrite the *pain in the but*....

--
My opinions may have changed,
but not the fact that I am right

Replies are listed 'Best First'.
Re: Re: Rewriting a large code base
by clscott (Friar) on Jun 28, 2001 at 18:10 UTC
    Count me in on that Toadi. I'm a sub-sub-sub contractor on my current project and the code is nasty with globals and functions defined in required files that are used by each application, but there seems to be no rhyme or reason for this approach.

    There is also a ton of duplicated code because it's a website with an adminsite and a public site and no code is shared between them. Eww.

    Plus no strict, warnings, or taint. And I can't rewrite or fix it because I'm here to add new features ASAP because I'm "expensive".

    It will never get rewritten or refactored because it "works fine" for the end-client.

    Thankfully I'm not supposed to be here that long but I'm writing the worst Perl code of my life (and Perl is my first language!) in this job.

    Enough venting for today, back to the grind!
    Clayton aka "Tex"

[reply]
[d/l]
      Actually my code is ok that I write. Cos I can't stand for it to deliver bad code.

      What you do is the broken window stuff from Pragmatic Programmer. And I try to avoid the temptation :)



      --
      My opinions may have changed,
      but not the fact that I am right

[reply]

In Section Seekers of Perl Wisdom