1)      If your Jr. Developer is interested in a new .Net technology,  remind him at lunch that Microsoft is ‘teh suk’ and produces only crap.

2)      If your Jr. Developer says the word "Pattern", ask him what book he read and remind him that book writers are like those who teach.

3)      If your Jr. Developer is concerned about a section of code he has inherited being hard to understand,  lecture him on the need to write better comments. 

4)      If your Jr. Developer says the phrase "Cyclomatic Complexity", remind him he is not in college anymore.

5)      If your Jr. Developer attempts to write a unit test, remind him to "Do it right the first time".

6)      If your Jr. Developer wishes to use a vacation day to attend a conference, refer to it in house as "Brain Washing".

7)      If your Jr. Developer says the word "Refactor",  ask him "You think you could write it better?”

8)      Require everything your Jr. Developer writes to be static.  If a threading problem emerges, blame it on him.

9)      When reviewing your Jr. Developers code, if you see an interface or any inheritance, make him rewrite it,  this time without "Over complicating" the issue.

10)   Never, under any circumstances, offer help.  Just repeat:  "You can do it right or get it done.  Get it done".  If he can’t figure out your entire codebase the first week,  he's an idiot.