3 ms·

I 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 revi

by plasma 6y ago

I 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 ago
In 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.