And where better than MD!A few minutes ago, I wrote: . . .
This discussion belongs elsewhere
sid smith wrote:In an online forum, I saw one old post in which someone complained that that he/she had the misfortune of having to debug poorly written code. I was curious to know how (java) code can become difficult to debug, given that the developer does not intentionally use anti-debugging tricks and also comments his code well.
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
Winston Gutkowski wrote:
Since I assume this was a serious question, about the simplest answer I can give you is: Don't follow all the good advice you've (hopefully) been given about formatting, naming conventions, Object-orientation, modularization and code reuse.
No more Blub for me, thank you, Vicar.
sid smith wrote:In an online forum, I saw one old post in which someone complained that that he/she had the misfortune of having to debug poorly written code. I was curious to know how (java) code can become difficult to debug, given that the developer does not intentionally use anti-debugging tricks and also comments his code well.
"The good news about computers is that they do what you tell them to do. The bad news is that they do what you tell them to do." -- Ted Nelson
J. Kevin Robbins wrote:
Someone once said "Any idiot can write code that a computer can understand. Good programmers write code that a human can understand."
Oracle Certified Professional: Java SE 6 Programmer && Oracle Certified Expert: (JEE 6 Web Component Developer && JEE 6 EJB Developer)
Dieter Quickfend wrote:
J. Kevin Robbins wrote:
Someone once said "Any idiot can write code that a computer can understand. Good programmers write code that a human can understand."
Martin Fowler?
"The good news about computers is that they do what you tell them to do. The bad news is that they do what you tell them to do." -- Ted Nelson
To debug a program you first have to understand it, and some programs can be very difficult to understand. Aside from purely technical considerations, all the flaws that make English prose difficult to read and understand also make programs difficult to read and understand, as most of the principles of technical writing also apply to programming.sid smith wrote:In an online forum, I saw one old post in which someone complained that that he/she had the misfortune of having to debug poorly written code. I was curious to know how (java) code can become difficult to debug, given that the developer does not intentionally use anti-debugging tricks and also comments his code well.
Oracle Certified Professional: Java SE 6 Programmer && Oracle Certified Expert: (JEE 6 Web Component Developer && JEE 6 EJB Developer)
Dieter Quickfend wrote:On a higher level: do not accept requests to implement complex behavior that users think they want. Trust me, it's really not what they want.
.
sid smith wrote:how (java) code can become difficult to debug,