Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

(d4vis)RE: Good, Fast, Cheap: pick the last two or get out!

by d4vis (Chaplain)
on Sep 17, 2000 at 22:46 UTC ( [id://32882]=note: print w/replies, xml ) Need Help??


in reply to Good, Fast, Cheap: pick the last two or get out!

It all depends on your definition of good. If good means that it works, then I'm with you 100%. If 'good' means that it has to be elegant, that it has to be 'art', then I have to differ. It may be different if you code for a living, but I use Perl only as a sys/network admin, and I worship the good one-time kludge.
If it's fast, if it works, that usually make it 'good' in my book.
Mostly, I'm so pressed for time on a normal day that I can't be concerned with creating works of art, though if it's really ugly code, I can always revisit it after deadline. ;)

~acolyte d4vis
#!/usr/bin/fnord
Update: Just one clarification. I do clean up anything that might have to be used by others in the future. That's just common courtesy.

Replies are listed 'Best First'.
RE: RE: (d4vis)Good, Fast, Cheap: pick the last two or get out!
by cianoz (Friar) on Sep 18, 2000 at 02:03 UTC
    my definition of GOOD(tm) does include "sufficently well written so i can put my hands on it a month later"
    deadlines are important but too short deadlines are simply stupid.
      deadlines are important but too short deadlines are simply stupid.

      And believing deadlines are selected according to how long it will take to do the job perfectly is naive. Dealines are selected according to when the product is needed. If I need a script to take care of a frequent problem, I need it before the next occurance of the problem - not two weeks from Tuesday. If that means the code will not be as elegant as it could be - oh well. If it does the job, good enough.

      - email Ozymandias
        While I agree with your point, I don't like the example.

        If I am writing the script you are not getting it until the time after occurance after the next one. Why not? Because before scripting a problem I *really* like to do it by hand once. I find doing that that I see a lot of critical requirements that way which I won't get just trusting someone's description of the problem.

        i'm not talking about elegance!
        even the most stupid script need to be maintained!

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://32882]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others avoiding work at the Monastery: (4)
As of 2024-03-29 09:27 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found