News for hackers. Stuff that matters.
Re:Chief Architect of Google+ requests clarification on Goog... by ChuckMcM on Friday March 15, 2013 @03:04PM (#5382327)
Once Reader lost favor inside the 'plex people didn't want to work on it because it wouldn't show well on their resume. (you don't get promoted for applying CPR to a dead product and manage to keep it alive in intensive care for another budget cycle). So there were no doubt people who were working on other projects who had previously worked on Reader sometimes fixing bugs, and there was probably a product manager somewhere that had at one time been responsible for it, and kind of still remembered where the files were in the source tree. But as a "product" it could continue to exist in Google with nobody "in charge" of it. Its hard to believe, and even harder to explain to someone who hasn't be on the inside, but there are things that exist as Google "products" or "features" only because nobody turned them off, but there is no one at the wheel any more.
Re:Chief Architect of Google+ requests clarification on Goog... by CamperBob2 on Friday March 15, 2013 @04:32PM (#5382832)
Once Reader lost favor inside the 'plex people didn't want to work on it because it wouldn't show well on their resume. (you don't get promoted for applying CPR to a dead product and manage to keep it alive in intensive care for another budget cycle)

Yeah, this is not the organization that should be acting as de-facto curators of the Internet, I'm thinking. What's being described here isn't a cathedral or a bazaar, but a bureaucracy.

Re:Chief Architect of Google+ requests clarification on Goog... by waterlesscloud on Friday March 15, 2013 @03:10PM (#5382353)
Well, that sounds dysfunctional.
Re:Chief Architect of Google+ requests clarification on Goog... by snaky on Friday March 15, 2013 @03:50PM (#5382586)
OK, you don't get promoted etc. But promotion isn't one and only motivation, right? For two years there wasn't one Google employee who added one feature to Google Reader just for fun? Ouch.
Re:Chief Architect of Google+ requests clarification on Goog... by ChuckMcM on Friday March 15, 2013 @04:19PM (#5382753)
I reiterate :-) its hard to explain for folks on the outside. There are so many shiny toys inside of Google that yes, you could easily go 2, 3, even 5 years before you even thought to yourself "Hmm, I wonder if we could make Reader do this ..."

More often than not, if you had touched the code, it was because someone had decided to replace the way services do user credentials in an incompatible way and someone told you had to make this code work with the new scheme, by the end of the month because it was holding up shipping the new user credential protobufs... so you ended up in the code with a gun pointed at your head saying "go fix this code you've never seen to use this new API that the code never anticipated calling."

Probably wouldn't make you want to go back "just for fun."