Debugging Process Quotes

It's probably fair to say that the ratio of time our Connector developers spend in the debugger versus the Emacs buffer is higher than with most software.

Indeed the early history of rocket design could be read as the simple desire to get the rocket to function long enough to give an opportunity to discover where the failure occurred. Most early debacles were so benighted that rocket engineers could have been forgiven for daubing the blood of a virgin goat on the orifice of the firing chamber.

Most of the time spent wrestling with technologies that don't quite work yet is just not worth the effort for end users, however much fun it is for nerds like us.

Nobody actually creates perfect code the first time around, except me. But there's only one of me.

If there is a bug in your code than you have to drop everything you're doing and go fix it.

Coding, it's an endless process of trial and error, of trying to get the right command in the right place, with sometimes just a semicolon making the difference between success and failure. Code breaks and then it falls apart, and it often takes many, many tries until that magical moment when what you're trying to build comes to life.

Reusable rockets promise much easier testing because you should usually get them back, and you can debug as you go rather than having to get everything perfect the first time.

Science requires a society because even people who are trying to be good thinkers love their own thoughts and theories - much of the debugging has to be done by others.

Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.

Experience shows that the success of a programming course critically depends on the choice of these examples.