Since the dawn of time (well, the 1980s) copy protections have had booby-trap/fail pits. Some of those fail routines have been remarkably creative (and occasionally ridiculously destructive).<p>Delayed flags with adverse consequences, subtly changing CAD points or musical note timings or slowly corrupting user data if a dongle has bad wiring. Deliberate hardware damage, from the C64 disk drive happily being made to chew on its own heads to (arguably) setting counterfeit USB serial interface chips to a PID of 0. I've even seen one which quietly dropped to desktop with a virus when tripped (in fact this was the origin of that particular bootsector virus, which achieved an unexpectedly wide spread on its platform, and its own payload had a generation counter attached so you wouldn't notice for quite a while).<p>This one is curiously poetic. Very meta. But still a logic bomb.<p><i>Don't</i> booby-trap your code. It's incredibly unethical and stupid. Logic bombs misfire. Frequently.