I believe that the most important ingredient of code quality is the mind-set of the developer. So I started with some slides about the Zero-Defect Mindset and Software Craftsmanship. Then I did a live demo performing the Prime Factors Code Kata to show the basics of unit testing, Test-Driven Development and regression testing. This was the main part of the presentation.
After that I explained the principles of code coverage, continuous integration, static code analysis and code reviews to the students. I mixed the theory (slides) with hands-on examples on the newly created Java code using EclEmma, Hudson, PMD and ReviewClipse.
Doing the demo was fun and the whole presentation was a success. For the demo I tried to stick to Scott Hanselman's Tips for a Successful Technical Presentation, esp. font size (Lucida Console, 16pt). Here is my "BigFonty" checklist:
- Create a new, clean user profile for presentation only.
- Set icons to large and number of colours to maximum.
- Remove all icons from the desktop and choose a plain desktop background. I like to minimise all windows if I get lost between them.
- Disable any screen saver and turn off energy saving. Otherwise they will definitely activate at the most annoying moment.
- Set the command shell font to Lucida Console 16 point, bold, green on black. Have the default shell point to your main demo directory.
- Clean up the browser, remove unnecessary tool bars and symbols. Unfortunately, at least in Windows, new users always have tons of crap on the desktop and in the browser.
- Set the default browser page to empty or your main demo web-site.
- Set the font size in your browser to very large and enable override of font sizes in styles. This is done in some accessibility sub-menu.
- Use the browser in full screen mode (
F11). You need all the space available for the large text.
- Set the main font in your IDE to Lucida Console 16. In Eclipse it's enough to change the
Text Font(in the Basic category in the sub-menu Colours and Fonts in Appearance).
- Turn on line numbering in the IDE for quick reference of single lines.
- Maximise the IDE and use a full screen source window whenever possible. In Eclipse just press
Ctrl-Mto maximise a view.
- Start all applications like IDE or any server before the presentation. They may take some time.