Program Compiled successfully, 0 errors
-
Missed your meds again huh?
If it's not broken, fix it until it is
Coder For Hire wrote:
Missed your meds again huh?
Actually, it's the meds that put me in these moods. (just kidding!) Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
0 syntax errors. Correcting logic errors is still up to you, however.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
-
I had that yesterday. Code still broke at runtime :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
:) <= $
«To kill an error's as good a service, sometimes better than, establishing new truth or fact.» Charles Darwin in "Prospero's Precepts"
-
Nope. "Payment received" is the happiest moment. :rolleyes:
I'd rather be phishing!
Agreed. Payment comes after post-installation testing by the client.
The difficult may take time, the impossible a little longer.
-
"0 Errors" is nothing - that's easy. "0 Errors, 0 Warnings" is better - but also pretty easy. Passing all tests and actually doing what you wanted it to? Now that's a good moment! (As is getting paid, as has been mentioned)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Let's not forget zero code analysis errors, and zero style cop errors, and zero QA errors.
Get real - we'll never get zero QA errors here! :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Get real - we'll never get zero QA errors here! :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Wishful thinking, I know. ;P
-
Nope. "Payment received" is the happiest moment. :rolleyes:
I'd rather be phishing!
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"
