1. WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010. They may not show up well on other PowerPoint versions. You can download PowerPoint 2010 viewer from here.here These slides contain a lot of animations. For optimal results, watch in slideshow mode.

2. CE1: when should you save the file? a)After each user operation b)After a fixed interval (e.g. every 60 sec) c)Only when the user is done editing d)Give a command for the user to save e)No need to save Consider costs and benefits of each approach. Give priority to costs/benefits that matter to the user.

5. SLAP? Can we tell the same story with less details? SLAP?

6. Higher level Same level

9. intention mechanism

11. [extra] Junit code sample 11 Java: Javadoc (built-in) C++: Doxygen (3 rd party)

14. [extra] Junit code sample 14

17. Good code looks neat.

18. Good Code

20. When to stop? Can I do better?

21. Good Code Code monkey Code gorilla

22. Good Code Code monkey Code gorilla Master craftsman

23. Good Code

24. Where we are… Lecture 3 Theme: From program to product idea. Can refactor code to improve quality. Can use revision control locally, individually.

25. Where we are… Can refactor code to improve quality. Can use revision control locally, individually. Any feedback on the lecture? feed2103 blah blah… 77577 OR tinyurl.com/answerpost