3 ms·
> 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
by 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