Kernighans Law
-
I have never found debugging to by hard. More of a simple algorithmic process of deducing errors using common tools and techniques. It is, however, time-consuming.
Need custom software developed? I do C# development and consulting all over the United States.
If you don't ask questions the answers won't stand in your way.
Doing a job is like selecting a mule, you can't choose just the front half xor the back half so when you ask me to do a job don't expect me to do it half-assed.You're right. The debugging is fine, it's finding bugs that's the problem. TDD seems to be catching on. It works if the tests reflect the requirements well enough. Debugging gets bad when you are integrating with something that isn't well documented (Blackberry).
SS => Qualified in Submarines "We sleep soundly in our beds because rough men stand ready in the night to visit violence on those who would do us harm". Winston Churchill
-
That explains why the standard C libraries are only half as clever as they should be.
PIEBALDconsult wrote:
are only half as clever
Half is being pretty generous! :)
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog Just Say No to Web 2 Point Oh
-
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." No wonder no-one can adequately debug their own code.
SS => Qualified in Submarines "We sleep soundly in our beds because rough men stand ready in the night to visit violence on those who would do us harm". Winston Churchill
Yes! In fact one of my plans was to write articles on some tough debugging situations I have been through in my career. In majority of cases fixing the code in question turned out to be very simple. Finding the problem was always hard.
-
PIEBALDconsult wrote:
are only half as clever
Half is being pretty generous! :)
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog Just Say No to Web 2 Point Oh
Well he didn't have access to the plethora of books on C we have and he couldn't post, "Urgent! Need codez for C library!", messages on CP.
-
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." No wonder no-one can adequately debug their own code.
SS => Qualified in Submarines "We sleep soundly in our beds because rough men stand ready in the night to visit violence on those who would do us harm". Winston Churchill
If you write multithreaded code with reader writer locks and deadlock avoidance I can fully agree with that statement. In my line of work I have been doing this since the late 1990s since most of my projects have needed 2 or more cores back then and even though CPUs are much faster today a typical dataset is also 4 to 8 times as large so this has not gone away..
John
-
Yes! In fact one of my plans was to write articles on some tough debugging situations I have been through in my career. In majority of cases fixing the code in question turned out to be very simple. Finding the problem was always hard.
-
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." No wonder no-one can adequately debug their own code.
SS => Qualified in Submarines "We sleep soundly in our beds because rough men stand ready in the night to visit violence on those who would do us harm". Winston Churchill
-
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." No wonder no-one can adequately debug their own code.
SS => Qualified in Submarines "We sleep soundly in our beds because rough men stand ready in the night to visit violence on those who would do us harm". Winston Churchill
-
If you write multithreaded code with reader writer locks and deadlock avoidance I can fully agree with that statement. In my line of work I have been doing this since the late 1990s since most of my projects have needed 2 or more cores back then and even though CPUs are much faster today a typical dataset is also 4 to 8 times as large so this has not gone away..
John
-
Much harder to debug timing issues / race conditions than single threaded code.
John