No, you're not the only one. I share your concern for all the reasons you cite. I'm also concerned about the development process itself. Design reviews? Code r

No, you're not the only one. I share your concern for all the reasons you cite. I'm also concerned about the development process itself. Design reviews? Code reviews? Automated testing? CI/CD? What is the impact of an easter egg on these things? Were the eggs noticed and tacitly approved? What does this tell us about the process? Do I want to rely on the product of that process? Or are we saying we don't care? I appreciate the idea behind the easter egg, the little human touch, the little flourish that says "look what I built", I really do. But, fundamentally, the software I use becomes part of the machine - and I want it to behave that way, like a reliable machine that does exactly what I expect and only what I expect. If I want a human touch, I'll reach out to a human. If I want a surprise, I'll read a book or play a game. Imagine an easter egg in your car's navigation system. Won't that be cool! Not. Easter eggs, especially in software that should be part of the machine, strike me as the height of unprofessional irresponsible behaviour. An f-u to management and to users that deserves its own resounding f-u, I'll use someone else's professional, reliable tools, thank you.