Programming And Debugging
Author: Samuel Williams When: Wednesday, 14 October 2009April 2009
May 2009
August 2009
September 2009
October 2009
- Building a Concrete Bath
- LED Lighting Comparison
- Thinking about Programming Languages
- How To Be A Consultant
- Lucid Programming Dojo
- Exim4 + ClamAV + SpamAssassin
- Secure login using AJAX
- Ramaze And Rack
- ActiveMerchant
- Concurrency And Immutability
- Floating Point Numbers
- Programming And Debugging
- Useful jQuery Plugins
- Loading Anonymous Ruby Classes
- 尺八 (Shakuhachi)
- Card Trick
- Object Oriented C
- Gemcutter
- Writing Clearly
- Richard Stallman In Christchurch
- Magnatune
- Client Side Graphing
- Zena CMS
November 2009
February 2010
March 2010
April 2010
May 2010
June 2010
July 2010
August 2010
September 2010
December 2010
January 2011
March 2011
May 2011
August 2011
September 2011
My friend Pistos recently pointed me to this quote:
"Debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?" - Brian Kernighan
I'm not sure I agree with it but I can understand what he is saying. I don't know if debugging and writing a program are two separate issues... When we write a program, we can write a small complex portion with a clear interface. We can then write tests assertions which ensure that the computer is actually doing what we think we told it to do :) Even if that part is complex, there are techniques and processes that can assist with this.
Sometimes, debugging is complicated, but I don't believe that is a real problem - it simply means the tools we have are not adequate. And with that, GDB 7.0 has recently been released. It has a number of cool new features including scriptability with python and reverse debugging (you can step backwards). I'm looking forward to trying it out.
Comments
Please note, you can leave a comment that uses (limited) XHTML and Textile syntax.