2 ms·
There is no substitute for hard-won experiences, but debugging is a skill that can be taught. The academic world (well, some part of it) knows about debugging a
by sanxiyn 15y ago
There is no substitute for hard-won experiences, but debugging is a skill that can be taught. The academic world (well, some part of it) knows about debugging and is surely qualified to put together a curriculum. Really, go read "Why Programs Fail".
http://www.whyprogramsfail.com/ http://www.whyprogramsfail.com/
A lot of what I know about debugging I learned in the trenches, but I also learned a lot from that book. My question is that why I had to discover this book myself, instead of being taught.
- dasil003 15y agoIn my CS program they taught debugging, but the majority of what I learned about debugging happened in the lab. Working on the problem sets was a microcosm of debugging that transferred quite well to the professional world, but I suspect not all CS curriculums have as rigorous a programming practice as mine (University of Minnesota, based on the MIT curriculum: scheme, c, java, c++, perl).
- phamilton 15y agoIn a CS class I took, we built a project over the course of a month. The TA's then introduced 5 bugs into the project, locked us in a room for 3 hours and we were required (individually) to find and identify the 5 bugs in that time. If you failed, they do it again a week later for a lower grade. Cool assignment.
- bobbydavid 15y agoI'll assume you simply ran your comprehensive test suite, inspected the five failing tests, and left in five minutes :-)
- phamilton 15y agopretty much. Though some were nasty: char * getFirstName(char * name){ char * fname = strtok(name, " "); return fname; } became: char * getFirstName(char * name){ char * fname = strtok(name, " "); return "fname"; } And stuff like that. It was fun though.