7 ms·
Why no Easter Eggs? (2005)
- jsmith45 6y agoThat old post has a heavy emphasis on the problem being "undocumented features", which is absurd, since most Microsoft products have undocumented features. These often intended for use in automated testing, or used internally by the software, or for use only by the developers and support personnel. SQL Server's `DBCC WRITEPAGE` is a great example of the latter. There are plenty of APIs intended only for Microsoft to use. There are significant features locked away by registry settings with zero documentation. Windows itself even has entire APIs that were explicitly designed and intended for external that are effectively undocumented. The real issue is easter eggs (or any code) that a developer snuck in without approval. Sadly, the post goes on to claim that even approved easter eggs should not be shipped (with the implication that them being undocumented is the problem), but that is absurd. Better cease all development on Windows/Azure/Office for the next decade so that all the undocumented features can be properly documented.
- lwansbrough 6y agoNot a great example IMO. Any accessible API is a public API once it’s released into the ether. Inevitably people build on those undocumented features (or come to expect them to exist) and it’s not sufficient for Microsoft or whoever to day “oops too bad, you built on a private API” because ultimately they would be disrupting their customers. I’m not against easter eggs though, you just have to be okay with the prospect of breaking expectations users may have in the future.
- yellowapple 6y ago> and it’s not sufficient for Microsoft or whoever to day “oops too bad, you built on a private API” because ultimately they would be disrupting their customers. Uhhh, that seems perfectly sufficient to me. Play stupid games (like relying on undocumented APIs), win stupid prizes (like watching everything break when those APIs change). Private interfaces should be used as a last resort, and with the full understanding that - being private - they have no obligation to be "stable".
- userbinator 6y agoThere's a difference between "undocumented undocumented", which is what Easter eggs usually are, and plain undocumented (what you're referring to.)
- cmeacham98 6y agoSerious question: from my perspective as the user what is the difference?
- plasma 6y agoI understand the main concern is related to security, if code (a team member's secret easter egg) is shipped unbeknownst to the development lifecycle (code review, QA, etc) then a security exploit may have just (accidentally) been included with the product. I'd imagine if the easter egg was a documented feature (eg, scoped by product managers, went through security review, etc) perhaps it would be fine.
- PeterisP 6y agoIn many products 'easter eggs' were well planned by the developing company, they're just not documented for the end-user and left there for them to discover. However, it probably made more sense in the pre-mass-internet age.
- Talanes 6y ago>The real issue is easter eggs (or any code) that a developer snuck in without approval. Sadly, the post goes on to claim that even approved easter eggs should not be shipped (with the implication that them being undocumented is the problem), but that is absurd. I think the poster you replied to originally had this covered.
- unnouinceput 6y agoHeh, this is benign. Now imagine the "Easter Eggs" that Intel/AMD/ARM has in their processors, the ones of undocumented CPU instructions that allows an attacker to elevate to kernel privilege. With Specter/Meltdown the world has only scratched the tip of the iceberg, with more to come in following decade.
- skissane 6y ago> The real issue is easter eggs (or any code) that a developer snuck in without approval. Sadly, the post goes on to claim that even approved easter eggs should not be shipped (with the implication that them being undocumented is the problem), but that is absurd. Developers still slip “undocumented features” into code all the time. I think it is ultimately a public relations and legal liability issue. If you add an undocumented feature, and you have a plausible argument as to how doing it serves the needs of the business (e.g “it dumps diagnostics useful in debugging customer issues”), it is much easier to defend yourself (and for your management to defend you) if that code later causes problems (whether security or performance or whatever) than if you embed a flight simulator. It is about the CYA of having a believable business purpose to what you did, which is helpful both in courts of law and the court of the media. A lot of places nowadays you need at least one PR review from a peer to merge code. Still you can end up with a feature that only two or three people know exist (the author and the PR reviewers) In my experience “undocumented features” often happen because the original specs don’t go into details about issues like diagnosability, etc, often because PM/design teams write the specs but only the implementing developers have a good idea of what useful diagnostics actually are. Maybe the developers should go back and update the spec but they very often don’t
- vl 6y ago> That old post has a heavy emphasis on the problem being "undocumented features", which is absurd, since most Microsoft products have undocumented features. Context is important here. As part of anti-trust deal, MS had to document all APIs and file formats, and there was a massive internal effort to do so. Basically it’s not allowed to call non-public APIs from one MS product to another. On top of that there was massive security push when entire Windows division stopped working on new version and concentrated on security of XP for many months. After these traumas there was no way Easter eggs would survive.
- peterkelly 6y agoMicrosoft was the first company to join PRISM, in September 2007: https://en.wikipedia.org/wiki/PRISM_(surveillance_program) https://en.wikipedia.org/wiki/PRISM_(surveillance_program) I'll take a flight simulator hidden in Excel over widespread, systematic violations of privacy any day thanks. Want to maintain trust from your customers? Don't spy on them.
- cortesoft 6y agoThis seems... completely unrelated?
- admax88q 6y agoWhy? The thesis of the article is that they dont allow easter eggs because they can hurt users trust. Seems like there are a lot of other practices they do which are far more harmful to user trust.
- cortesoft 6y agoSo, since they participated in PRISM, they shouldn't do anything else to improve trust? It wasn't like this was an either/or situation... a manager wasn't deciding between prioritizing not participating in PRISM or not making an Easter egg.... in fact, I can almost guarantee this person wasn't involved in the PRISM decision.
- square_usual 6y agoOk, let's think about trustworthiness like it's an RPG stat. Preventing easter eggs is, at best, +1 modifier. Joining PRISM is, conservatively speaking, ~-100 on the same scale. It kind of makes whether or not there are easter eggs in the code meaningless in comparison.
- drdeca 6y agoI suppose one might argue that if they [prism] then they don’t value user trust, and therefore user trust wouldn’t be a reason for them to not [easter eggs]. However, that would seem to be based on an idea of valuing which is absolute, and which accepts no trade-offs. Conceivably they could value user trust (at least, instrumentally value it), but value what they would get out of doing [prism] more, per amount of lost user trust, then they value what they would get from [easter eggs] per amount of (somehow?) lost user trust. (Words in square brackets are abbreviations for the activity relevant to the words in the square brackets)
- bsnwosdh 6y agoMeanwhile, Google has their own blogpost explaining why they have so many easter eggs https://www.thinkwithgoogle.com/intl/en-gb/advertising-channels/search/hidden-meaning/ https://www.thinkwithgoogle.com/intl/en-gb/advertising-chann...
- pjfin123 6y agoI switched from Windows to Linux, Easter eggs were not the reason.
- drfuchs 6y agoHeard in the halls of Adobe in 1995: In an earlier version of Photoshop, a high-ranking member of the team had snuck in a Halloween easter-egg, but failed to take account of the fact that text encodings for the Japanese version's string resources required two-byte encoding. So, starting at midnight on Oct 31, in most of the world, Photoshop would start up with a "Happy Halloween" alert; but in Japan, it would crash at startup. Whoever did it got fired by the CEO, via phone call in the middle of the night. Any or all details might be wrong...
- fortran77 6y agoNot quite correct. The Easter Egg would change the name of Steve McS———( a QA engineer ) to ‘Steve Bassomatic McS———’ on April 1st. And the person responsible was fired the next day.
- salawat 6y agoThat's incredibly depressing actually. Someone getting fired over such a minor joke because they didn't run tests related to localization is what is depressing there.
- zingplex 6y agoThe fact a QA engineer didn't properly anticipate localization issues with the joke could be indicative of other performance issues.
- fortran77 6y agoThe QA engineer was the butt of the joke. Not the implementer.
- drfuchs 6y agoPerhaps you missed the point: An entire country's worth of customers had a product they paid maybe $1,000 for become completely useless all at once, for no good reason. And this was at a time that software came on floppy disks or CDs in shrink-wrap boxes, with updates maybe once a year; no downloading bug fixes over the internet in a few seconds. One can only imagine the cost in dollars and reputation to Adobe, and the pain caused to customers. Even if the fix involves flipping a single bit in the binary, there are days worth of manufacturing (making a new "golden master", duplicating floppies / pressing CDs, typically done by a third-party who may or may not have room in their schedule), boxing and shipping it all, etc. It was huge and avoidable, and due to someone(s) specifically evading the sanctioned flow of production. Think of it more like "Ha ha, after it was QAed, I hacked a picture of my cat into the masks for the new Intel CPU; who knew it would mess up some capacitance and change some critical timing in the barrel-shifter? Oh well, the fix is easy, and all we have to do is send a new chip to everyone."
- deleted 6y ago[deleted]
- Aransentin 6y agoWhat a joke. Yes, Windows might show advertisements in the start menu and unbiddenly download & install crapware like Candy Crush, but thank god there's no Easter eggs anywhere.
- pugworthy 6y agoJoke perhaps, but consider this was written 16 years ago. Back when none of the "yes but" stuff was around. They would probably say their position "evolved"...
- causality0 6y agoSometimes I wonder how different things would've been if Gates had kept an active role. Would we be using Windows 9 now? Would you not have to spend five minutes doing something you can do in Windows 7 in ten seconds, like adding a shortcut to a folder to your taskbar that actually opens the folder when you click it?
- SavantIdiot 6y agoGo back to 2005, would you have believed "automatically installed ads on your Start Menu" would be anything other than a joke from Futurama? Yet here we are.
- DaiPlusPlus 6y agoWindows 98 came with ads in Active Desktop
- SavantIdiot 6y agoI stand corrected. I had to google it, and I completely forgot that brief period of chaos where desktop was a web page. Ughhh... At least it was "opt in", which is my feeble attempt at hanging on to my argument that MS is more nefarious now than before. :)
- 6y ago
- nemo1618 6y agoProgramming is nothing without whimsy.
- II2II 6y agoWhile I agree with the no-Easter egg policy for many of the reasons cited in the article, some of the cited customer concerns just rubbed me the wrong way. Take a more serious sounding one: > Is this what MS developers do when they should be concentrating on security? The presence or absence of an Easter egg is not an indicator of the time spent concentrating on security. Claiming the Easter egg can introduce bugs that impact security or erode customer confidence due to the presence of hidden features are legitimate concerns. Why do I bring up the differentiation? Hyperbole attacks the credibility of the legitimate. As for solving the Easter egg problem, the incentive would be diminished if credit was given where credit was due (e.g. a documented credits screen).
- bartread 6y ago> As for solving the Easter egg problem, the incentive would be diminished if credit was given where credit was due (e.g. a documented credits screen). I don't know so much about that. When I worked at Redgate the About boxes in all of our tools would, after about 30 seconds, fade from the product logo to a photo of the team that developed the product. I always quite liked that - it added a personal touch to the software - but it certainly didn't stop the practice of Easter Eggs. Most were small but one of my colleagues did embed a complete version of the game Asteroids into one of our SQL tools. Doctoring the team photos also became increasingly popular for several years. I haven't put an Easter Egg into an application in more than a decade (at the end of the day you have to know whether it's acceptable or not to your employer) - though there has been the odd somewhat on point symbol name - but I do think people get unduly bent out of shape about this stuff. Lives depended on the sofware run by the Apollo Guidance Computer and yet it contains symbol names such as BURNBABY, POOH and (I think) POOHDOO. E.g., https://archive.softwareheritage.org/browse/content/sha1_git:665f8e95921e92776819b719f780ddbece2b78ac/?origin_url=https://github.com/virtualagc/virtualagc#L62-L81 https://archive.softwareheritage.org/browse/content/sha1_git.... I think it's important that people experience some joy in their work, and put something of their personalities into it, because the overall effects are both higher engagement and higher quality. Some will judge and say, "Well, if you had time to do $FRIVOLOUS_THING then you had time to do $MORE_SERIOUS_AND_WORTHWHILE_THING so why didn't you?" Maybe, but that's not really how many people work. These things aren't just vanity: they're often a sign that staff are putting some love into what they build.
- deleted 6y ago[deleted]
- Mountain_Skies 6y agoInteresting that David Plummer, a retired systems engineer at Microsoft, posted a podcast on this very subject two days ago. https://www.youtube.com/watch?v=vlo5PLOlT6I https://www.youtube.com/watch?v=vlo5PLOlT6I
- caslon 6y agoThe fact that they bit the onion with Adequacy is really, really funny.
- deleted 6y ago[deleted]
- pugworthy 6y agoSpeaking from practical terms, I've put a few Easter eggs in various projects since the late 90's, but it's always terrified me that my dumb little fun thing would cause the crash of a mission critical task. No oceanographic scientist from a long planned expensive research mission needs to find out that the data is bad due to some "funny stuff". But speaking in fun terms, probably the best fun I ever had with it was putting little "Waldo" images in levels I developed as part of a popular online shooter. It was my online nickname at the time, and it was a lot of safe entertainment, both for me and for the players.
- ARandomerDude 6y agoPro tip: don't use Windows.
- nicklecompte 6y agoI think a missing bit of context here is that you shouldn’t be writing Easter eggs (or jokes in general) in your software if a) your software is used in critical operations involve real human lives or large amounts of money; AND b) your company is developing a reputation for buggy and insecure products Both applied to Microsoft in 2005! While the author is perhaps guilty of abstracting the concerns too much and avoiding MSFT-specific issues, I think it’s a fair point that Easter eggs are unprofessional and can blow up in management’s face for high-profile software.