in reply to Perlmonk's "best pratices" in the real world

But their code still works. and it works well.

Yes. But they probably took twice the time a disciplined guy takes.

Yes. But later when an unlucky guy takes over those code, you will hear him swear all the time.

Yes. But one day, someone will say that he would rather rewrite it than fix all those bugs.

  • Comment on Re: Perlmonk's "best pratices" in the real world

Replies are listed 'Best First'.
Re: Re: Perlmonk's "best pratices" in the real world
by schweini (Friar) on Nov 13, 2003 at 10:55 UTC
    someone will say that he would rather rewrite it than fix all those bugs.
    which is exactly what i have been doing :)

    and as i tried to aknowledge: it IS suboptimal not to use every trick in the book, and i sure as hell am not advocating really sloppy programming practices, but how much sloppyness is acceptable, on the long run?
[reply]
      but how much sloppyness is acceptable, on the long run?

      In long run no sloppyness is acceptable at all. Quick dirty solutions work only in short time. If the solution is to stay then for your own sanity rewrite/refactor it so it has no sloppyness you know about left. I learned this lesson hard way - not doing so hit myself so many times. If you allow yourself not to cleanup and refactor your code continuously you always end up with Big Ball of Mud which costs (in terms of time/money) way more to maintain.

      --
      Ilya Martynov, ilya@iponweb.net
      CTO IPonWEB (UK) Ltd
      Quality Perl Programming and Unix Support UK managed @ offshore prices - http://www.iponweb.net
      Personal website - http://martynov.org

[reply]

In Section Meditations