Slashdot Mirror
Easter Eggs in Web Sites?
cwikla asks: "Back in the .COM days, I worked at eGroups, now owned by a larger Company. During my time I added a couple of easter eggs to the site, which I was reminded of while watching Being John Malkovich this weekend. I checked, and ones sort of still there. If you append malkovich=1 to a message URL it would turn the message into 'malkovich' mode. It sort of still works, but over time I guess the code has been a changin' so it's kind of spotty. Oh, there are others that still are in there, but where's the fun of telling all the secrets? Any other folks done anything equivalent, especially on mainstream sites?"
How do you "stumble" across the flight simator in Excel? I've never had the need to do those things on a spreadsheet. The programmers had to tell someone in order to find it.
For reference...2002-03-19 20:37:21 Easter Eggs at the Expense of Resources? (askslashdot,programming) (rejected)
That just got rejected in the last three days.
My comments went something like this - I have a friend who works for a company that does Palm software, and he inserted a tic-tac-toe game in their application. The software he develops is fairly large and robust, and the thought came to mind: Where do you draw the line with Easter Eggs?
The Palm platform, and any other portable/embedded system, deals with small storage and memory footprints. Adding in a hidden extra like this isn't taking up an "infinitesmal" amount of space or resources. Proportionally, it's of significant size. On a PC, this might be different, but for a Palm with 2 MB of memory, I'd personally be a bit disappointed to find out that the software I'm installing is artificially fluffed/bloated because some yahoo decided to have a little fun.
So, where do you draw the line with Easter Eggs? Fun in programming is cool. And I'm not saying that he was wrong for doing it...but what if he decided to put in JezzBall or something larger instead? Or something that wound up being a security/system hazard?
"Mod, mod, mod...and another troll bites the dust."
I've helped create a number of easter eggs in the past, but these days, I've had a serious change in thinking about them.
This may sound extreme, but if a coder added an easter egg to a project that I was running, they would get in serious trouble, maybe even fired. Now, before you think that is just being too serious or flame-bait, here's my reasoning:
Simply put, easter eggs are for the developers, not for the customers, and they don't belong in commericial software developement. The risk almost always outweighs the benefits, especially in a project like a public site! That is incredibly dangerous.
One of the biggest problems with easter eggs is they almost always bypass the QA process. Think about that for a minute. The developers are writing code that hasn't been tested, and the QA department doesn't even know it exists! Granted, this isn't always true, but most of the time, it is. Bad, bad. Like potentially company-ruining-bad if the dev uses some bad judgement (gee, that never happens, late at night, at the end of a project, does it?).
The best course of action is that the devs know ahead of time that easter eggs are not tolerated unless they are totally above-board in the development cycle. Save your humorous inside jokes for internal little apps you give to your mates, and you and your company will be a lot better off. They're usually inside jokes, anyways, so putting them in a public software project is just a totally unecessary risk, IMO. A few yuk-yuks is not worth your company or your project being compromised by bad code or a PR hit from an embarassing easter egg.