> 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.
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.