Throughout my career, I've met many developers who couldn't code their way out of a paper bag, network engineers who couldn't network their way out of a paper b

Throughout my career, I've met many developers who couldn't code their way out of a paper bag, network engineers who couldn't network their way out of a paper bag, sysadmins who couldn't sysadmin their way out of a paper bag, etc. I propose a new interview question: How would you code your way out of a paper bag? You will be given several constants, such as the strength of the paper bag, difficulty of tearing, etc, and will be expected to write your own Tear() function and call it properly. The best part is that when the recruiters/headhunters ask why you rejected a candidate, you can honestly say "he couldn't code his way out of a wet paper bag."