3 ms·

I think the best solution is to add an "easter eggs" section to the manual. Few people read the manual, so they're still hidden enough.

• ryandrake 7y ago
  If they are documented, as a user I would still think, "What else could they have been improving/fixing if they weren't working on easter eggs?" I wonder if in an alternate world, Excel minus the flight simulator easter egg could have been $1 cheaper or had 5 more bugs fixed.
  • trhway 7y ago
    > I wonder if in an alternate world, Excel minus the flight simulator easter egg could have been $1 cheaper or had 5 more bugs fixed. if anything, i think that Excel would have much more bugs, and would have much tougher time taking off :)
  • makapuf 7y ago
    As a dev, I can relate to working overtime for a small eater egg, or even if I were a manager I could understand those (security implications notwithstanding) if it would boost morale or team cohesion better than an akward social event.
  • LocalH 7y ago
    That's an amazingly entitled viewpoint, in my opinion. There's also a rabbit hole there of saying that about any feature that one doesn't make use of. I understand the concept that maybe certain classes of software (say, medical or military software) shouldn't have eggs, or perhaps that certified eggless versions of software should be available in situations involving contracted software. But would you say the same thing about game software? Hobbyist software? Easter eggs aren't always bad.