It wouldn't even be that difficult to have a series of examples of developing tests, cleaning up, trimming down, and debugging other people's code. Almost all o

It wouldn't even be that difficult to have a series of examples of developing tests, cleaning up, trimming down, and debugging other people's code. Almost all of the classes I took didn't allow collaboration, even though that's probably the most important working use case. Lines of (useless) code removed is at least as powerful a metric as lines of (usefull) code added when developing. It wouldn't directly teach them to think before writing, but they might learn the downside of failing to design the program structure well, and the pain of refactoring. It would be hilarious to give them back one of their early projects and slightly change the (marketing) requirements... (then require functionality can't be broken for testing more than X min-hours), just like real life. They'd learn they ARE the jerk writing unmaintainable code.