

 makefile.lab (with description of HW1)
	people found this one very useful

 solid.code
	work on comments
	add stuff on STDIN and on string handling - most common bugs for students
	example of getopt too
	file guards

 source control (maybe this should be earlier)
	needs to be revamped
	use cervisia as graphical front end to
		cvs

 debugging (maybe 2-3 labs)
	split into 2 labs - exp if add Purify

	I would suggest learning how to debug in a windows
environment, and then perhaps following up with one of the Unix command
line editors after learning all of the important debugging terminology.
Great packages with both development and debugging capabilities are
available for both X Windows and Microsoft Windows. Some things are just
easier on Windows. 
	
	make workskeet

	Also gdb is a helpful debugging tool when you only have access to a command line.  However, in a
visual environment which I assume most of us program in there are far better tools that dramatically
 
increase debugging speed.  For unix/linux I use kdevelop, although it does have some limitations
and needs some revision it is still the best visual debugger I have seen for that environment.
For windows development no questions asked Visual C++ has the best debugger I have ever used.



 design tools (UML modeler)
	UML Modeler etc. Rational products
	ArgoUML (in Java?)
	maybe use dia to make UML then
	dia2code to generate C/C++/Java headers

 doxygen 
	lab on this would be neat to reverse
	engineer some open source project
	also has ability to generate UML 
	diagrams   	 
	
 gcov.gprof 

 gnutools, open source, reading good code
	download a piece of code and look at it
	in class


 STL usage



