> Do you feel the same about easter eggs? Absolutely! Undocumented Easter Eggs cannot be tolerated in any software project today. Larry Osterman wrote about w

> Do you feel the same about easter eggs? Absolutely! Undocumented Easter Eggs cannot be tolerated in any software project today. Larry Osterman wrote about why Microsoft (and most other major software vendors) banned easter-eggs: https://docs.microsoft.com/en-US/archive/blogs/larryosterman/why-no-easter-eggs https://docs.microsoft.com/en-US/archive/blogs/larryosterman... The important point is (to quote): > If the manufacturer of the software that's on every desktop in your company can't stop their developers from sneaking undocumented features into the product (even features as relatively benign as an Easter Egg), how can you be sure that they've not snuck some other undocumented feature into the code. But if an easter-egg is is documented and implemented following normal software engineering practices then that's fine (of course paying customers won't be happy to learn that's where the team is putting their resources), and you can still keep things "secret" by hiding them in spoiler-tags or similar in your changelist - but there must never be any unaccounted-for functionality in a software project.