These Easter eggs really give an “early desktop PC era” vibe to it all. It’s very human and connects you to the fact that you’re using something that people with faces and names made. Back when these were passion projects by a bunch of hardcore nerds.
But they’d rather you not really see through the product abstraction layer anymore. The Product People want to control the full image of the product and it’s just safest to de-humanize it in case that list is too big or people on that list become undesirables or whatnot.
I’m thinking about what this might look like today. Maybe a neat Easter egg in my iPhone that every time I activate it, it shows me a few people at random who played a role in development. I’d love it, but I imagine this would offend the high tastes of the Product People.
Having been at this long enough to have put Easter eggs of my own into works I've done, I can say that the biggest issue is the lack of stomach for introducing a possible failure point to the software for little more than shits and giggles, especially when software has gotten so complex and big. That and who has the time to build silly stuff at work anymore. I feel like we're constantly at 120%.
> Maybe a neat Easter egg in my iPhone that every time I activate it, it shows me a few people at random who played a role in development. I’d love it, but I imagine this would offend the high tastes of the Product People.
Be careful what you wish for, lest a special hotkey on a new Mac brings up a fullscreen portrait of Craig Federighi in his full mighty hairy-chested glory with “infinite” zoom into the chest (available as a 5GB download).
I don't know what your odd issue with product people is but this has absolutely nothing to do with Product (management). Software used to be done by a handful of people. Now there are thousands involved across an organisation. For better or worth that's how it is. An Easter Egg highlighting just a few people just doesn't make sense for a large software project nowadays
I wonder too if there was more of this before Agile. With deadline driven development you can run into situations where part of the team is stuck waiting for their teammates to finish something so they can surpass a milestone. You can only poke at the backlog so much. Boredom and being able to rationalize that you aren't really affecting the roadmap by sneaking a little extra something in makes for a lot more 'motive and opportunity' situations.