4 ms·
Unpopular opinion, but I'm very much against Easter Eggs, at least in SeriousProjects™. Hear me out. When I was younger, I used to find them funny and lighthear
by ryandrake 5y ago
Unpopular opinion, but I'm very much against Easter Eggs, at least in SeriousProjects™. Hear me out. When I was younger, I used to find them funny and lighthearted, but after years of having to debug other people's unnecessarily clever code, undocumented code paths, and corners of applications that had absolutely no reason to exist, I've changed my mind. Even though none of what I had to debug were technically Easter Eggs, they were unnecessary, and thus time spent working on/around them was wasted.
The best reason to not add Easter Eggs is simply: they add unnecessary (albeit tiny) risk to a project. Technical risk and schedule risk. They are not part of the software's requirements, and they are likely going to be undocumented. Every line of code we add increases risk. Part of our jobs as developers is ensuring every line we add contributes more value than risk. Easter Eggs don't do this. Sorry to be Mr. Serious Raincloud, but please leave Easter Eggs for personal, non business-critical software.
- cpeterso 5y ago> The best reason to not add Easter Eggs is simply: they add unnecessary (albeit tiny) risk to a project. A perfect example from the article: the performance and memory impact on Windows startup due to loading the ASCII cats’ monospace font.
- wizzwizz4 5y agoIn well-architectured code, easter eggs are free. Removing them is trivial, but you don't need to because they don't cause problems. They add value, not only because they're great, but because they force you to make your system more extensible than it otherwise would be – but if they break, no harm done. (You might even get bug reports from users, if they stop working! But the users won't mind, because the easter egg isn't why they were using the program.)
- deleted 5y ago[deleted]
- ghostbrainalpha 5y agoWe all hate debugging unnecessary and pointless code. But over the very LONG TERM projects I see with Easter Eggs tend to have had developers who cared more about the project and were having fun, which leads to an overall higher code quality. (Your own experience may be different).
- rendall 5y ago> Unpopular opinion, but I'm very much against Easter Eggs, at least in SeriousProjects™. OP, here. I don't completely disagree with you. As I said, there are always reasons to take them out, and almost always, those reasons are excellent. A well-executed Easter egg says something good about the team and the project, though. A team that has the time, resources and capability to build something neat or cool or (pleasantly) surprising, is a team that is unstressed and competent. To be clear, I'm not discussing something like adding a clown giggle to flight control systems. I'm talking about when there are two equivalent paths, neither objectively worse than the other, I prefer when the team follows the path that adds whimsy and fun to the project over when they decide boring is better. A team that will at least consider adding it will inevitably be more efficient than a team that absolutely will not consider it because they fear extra work.