In well-architectured code, easter eggs are free. Removing them is trivial, but you don't need to because they don't cause problems. They add value, not only be

In well-architectured code, easter eggs are free. Removing them is trivial, but you don't need to because they don't cause problems. They add value, not only because they're great, but because they force you to make your system more extensible than it otherwise would be – but if they break, no harm done. (You might even get bug reports from users, if they stop working! But the users won't mind, because the easter egg isn't why they were using the program.)