3 ms·
To some degree this was a system or process failure. The build should have never become a beta build that gets send to the public. Many years ago I worked on an
by ajmurmann 4y ago
To some degree this was a system or process failure. The build should have never become a beta build that gets send to the public. Many years ago I worked on an Android game where on April 1st one of the other devs swapped the game's theme for Never Gonna Give You Up as a similar prank directed at the QA team. If we had shipped this more widely, it would have been a larger organizational failure, similar to this case.
- heleninboodler 4y agoThere's an infamous case from Adobe where an engineer added an unauthorized easter egg that caused a runtime problem and was fired for it. The firing spurred widespread shock among the employees, and management quickly rescinded his termination. He quit shortly afterward. The takeaways here are that a rash firing for this sort of thing isn't always the best course of action, and that being fired-then-unfired leaves a bad taste in an employee's mouth. Oh, and test your easter eggs.