3 ms·
At first I thought this was another silly guide until I looked at it. There's some meat on those bones. Worth a bookmark.
by edw519 17y ago
At first I thought this was another silly guide until I looked at it. There's some meat on those bones. Worth a bookmark.
- jacquesm 17y agoDefinitely. I like it that the author jumps straight in with the most important skill any programmer should master: Debugging. Debugging is where the boys get separated from the men, for want of a better expression. To be able to replicate, locate and fix bugs is one of the most time consuming things in software development, and by employing the wrong techniques (for all the right reasons) you are going to waste a lot of precious time. If you think you can develop software that works well and 'as designed', think again! It's happened to me once or twice that I wrote more than 20 lines of code and it worked the first time out... This was such a rarity that I had to go over it back to front to make sure that I wasn't seeing things :) Usually when I'm done debugging a piece of code I can say for the first time that I really understand it. To read this article - if only the chapter on debugging, but the rest of it is pretty good stuff as well - is a good investment of your time.