Lecture 5

[yoavram]

Debug and Exceptions. See http://www.cs.tau.ac.il/courses/pyProg/1415a/recitations/9_debugging_and_errors.pdf

[yoavram]

• http://hplgit.github.io/teamods/debugging/debug.html
• https://teachcomputing.wordpress.com/2013/11/23/sabotage-teach-debugging-by-stealth/
• http://www.cs.tau.ac.il/courses/gip/2014/Tirgul/2/tirgul2.ppt

Maybe use students errors from HW?

[yoavram]

@soungalo ok if I take over this?

[yoavram]

https://medium.com/@karan/the-7-rules-for-writing-software-that-wont-die-when-you-do-38ef0a925650?source=tw-18b7de952d74-1425654315015

[soungalo]

Sure, go ahead. The link looks very interesting BTW.

[yoavram]

I've pushed a half backed notebook in commit 4784b86 - would appreciate comments (ping @soungalo )

[soungalo]

Nice examples! Few ideas for stuff to add\change:

• [x] Use functions instead of plain code, so they get used to them.
• [x] Explain in the beginning the difference between runtime, syntax errors and more 'complex' bugs (logical bugs).
• [ ] Try/except
• [x] Assert statements (especially in the beginning of functions to assure the input is correct)

[yoavram]

Tips for debugging by Amir Rubinstein:

• [x] adding "diagnostic" printouts
• [x] narrowing down search space by fixing variables / return values (not trivial at all for non CS students!)
• [ ] and of course using debuggers. I don't like debuggers in python.

From Ohad Lewin-Epstein:

• [ ] mutable bugs - changing a list etc.
• [x] incorrect code vs. bugs

[yoavram]

Updated commit 0b26336.