Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

Re: Universal laws of bugs?

by Abigail-II (Bishop)
on Mar 10, 2003 at 00:41 UTC ( #241638=note: print w/ replies, xml ) Need Help??


in reply to Universal laws of bugs?

This entire thread can be summed up with one of the mottos of the monastry: "All software sucks".

To paraphrase the late E. W. Dijkstra, we have only been programming for a few decades. We can't even answer the fundamental question whether programming is hard or not.

Abigail


Comment on Re: Universal laws of bugs?
Re: Re: Universal laws of bugs?
by Wysardry (Pilgrim) on Mar 10, 2003 at 05:31 UTC

    This entire thread can be summed up with one of the mottos of the monastry: "All software sucks".

    Not all software sucks... Some of it blows.

    One huge software company, against all logic, even manages to create software that both sucks and blows at the same time. ;o)

    __________
    "Every program has at least one bug and can be shortened by at least one instruction -- from which, by induction, one can deduce that every program can be reduced to one instruction which doesn't work." -- (Author Unknown)

Re: Re: Universal laws of bugs?
by blackstarr (Pilgrim) on Mar 10, 2003 at 06:15 UTC
    We can't even answer the fundamental question whether programming is hard or not.

    Take it from one who's still struggling to tie his laces (programmatically). Programming is hard! It's coding that's easy.

    It's easy to write a bit of code that does a specific "thing" ... I do it all the time.

    What I still am struggling to get right is to write that same bit of code so that it is:
    1.) Usable in more than just the one situation it was coded for.
    2.) Stable in an unstable world.
    3.) Looks good (i.e. Others can understand it.)
    4.) Doesn't get me a metaphorical clout accross the skull when another programmer sees it.

    Maybe I've swopped the "correct" definitions of coding and programming around? :-)

    So Long
    blackstarr

      1 - see CPAN, modularization is easy 'nuff said. 2 - Logic. Just understand basic logic. No one can break logical code unless they invent a square circle. 3 - Don't drop the the lowest common programmer. Just keep it relatively simple and you'll be find (common sense stuff, break complex operations into multiple lines, etc) 4 - Program for yourself and you won't need to worry about this.

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (8)
As of 2014-12-29 07:27 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (185 votes), past polls