Program Compiled successfully, 0 errors

[BillWoodruff]

:) <= $

«To kill an error's as good a service, sometimes better than, establishing new truth or fact.» Charles Darwin in "Prospero's Precepts"

[Member 10707677]

Agreed. Payment comes after post-installation testing by the client.

The difficult may take time, the impossible a little longer.

[decaffeinatedMonkey]

Let's not forget zero code analysis errors, and zero style cop errors, and zero QA errors.

[mBuchwald]

This is only true if it isn't you first time building the code. If you get zero errors on the first try, paranoia begins.

[OriginalGriff]

Get real - we'll never get zero QA errors here! :laugh:

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

[decaffeinatedMonkey]

Wishful thinking, I know. ;P

[dpminusa]

Debugging is the creative part. Successful Compiling is great, but I enjoy debugging a lot more. Debugging leads to better code as well as working code when you iterate through each debugging session. Creating the initial code is often a free flow of ideas when the algorithms and specifications are created. I treat programming like writing an article. I get the ideas down and assume I will be improving them iteratively. I don't like to over-think and block the code flow. This works well in a small group that can be creative. This would not work well for larger projects and larger groups, of course. I work in a small group with limited constraints on creativity. I try to stay object-oriented, concise, and well-documented. Coding should be fun and enjoyable. Maybe that is why I like small independent projects. Less structure, more fun!? I suspect I am like many Code project members. That is why I keep coming back to Code project and sites like stack overflow. Or maybe I just had too much coffee this morning.

"Courtesy is the product of a mature, disciplined mind ... ridicule is lack of the same - DPM"