I'll never forget the launch. I was sick, and sitting on the floor of a war room live-coding a script to give every attendee $1. Python, had tests, and it persisted its state to SQLite so that we could Control-C it if our service got too slow. It didn't get too slow; we did a lot of load testing and capacity problems and the launch was very smooth. Most fun I've ever had while sick. (10-year-older jrockway wouldn't go to work while sick, though.)
Thanks for the insight on why Google makes so many braindead decisions. It's so frustrating I'm ready to abandon them entirely.
And that's why things slowly rot away. Cleanup should be a priority, otherwise it eventually slows down new feature work.
In fact, a project should not be declared finished until its inevitable follow-up cleanup tasks have been completed as well. Just like a party weekend is not finished until you have cleaned up the mess after. Somebody is going to have to do it, and if it's not you right after you're done with your deliverables, then somebody else will have to do it. Possibly yourself further down the road when you actually want to do something else more exciting. Just like doing the dishes. Nobody wants to start preparing a big meal by having to do the dishes from the week prior.
In business, we don't have to be adults.
Strategically, this is called being a Fast Follower. One of GOOG's problems is that it acts in the market as a fast follower, but tells itself internally that its an groundbreaking innovator. Your reaction (which was also my reaction),
> Nothing I ever do here is exciting. Thought maybe working on app with over a billion users would be exciting...
is a form of corporate-wide cognitive dissonance between GOOG's propaganda and reality.