Programming, the good and the bad

[Kimi]

Assuming all the programmes you have in hand and are supposed to produce the same result are working (giving the right results), so what makes one better than the other is the processing or uploading or whatever speed and perhaps the design, is there anything else?
When it comes to make a programme to run quicker, do you programmers play with the logic or more with the compiler?
Just curious...
Might have to make a macro or a VB module one of these days

[Guest]

Issues like performance aside, the more efficient (ie. simpler), the better written (eg. modular coding, good documentation etc.) and basically the easier to understand (from the point of view of someone other than the original developer) program is the better one.

It all comes down to how difficult it will be to support/enhance the program over it's life time. Too many developers (i would say the majority actually) code with a short sighted view. Basically if it works, they are happy. But 2 years down the track will it still work and if it needs to be enhanced, will it be easy for someone unfamiliar with it to do so.

My experience with other developers is that most of them are hacks and have no idea about quality programming. This is why the majority of software today is full of bugs.

[Fohls]

Here, here, nothing worse than crap code. I just spent 2 days debugging a program error that was put in 2 years ago and no one noticed till the customers changed the way they work.... the comment attached to the offending line of code was: ;ksw (The offending programmer's initials)



Would like to meet him again one day!!

Always keep it as simple as possible and comment, comment, comment...