Re:Why I Like Google's Reorg and Why It's Only a Start
by Jabbles on Saturday April 09, 2011 @03:17PM
(#2427860)
Pretty much content free imo. His main point seems to be trying to tell Google "Don't just do search", which is odd, seeing as he opens with a description of the 7 key areas of Google.
I think the comment by spinchange sums this article up quite nicely "I think it must be much, much easier to write articles like this about managing Google than it is to actually manage Google.".
Re:Why I Like Google's Reorg and Why It's Only a Start
by lehmannro on Saturday April 09, 2011 @04:07PM
(#2427972)
The author procures a scenario in which Google is going to collapse rather sooner than later. The last numbers I heard from Google reported an upwards trend in revenue [1] and with their recent additions like Google +1 [2] and Google Connect [3] I don't see them ‘miss the big picture’. Am I missing some serious tech scene scoop (genuine question)?
Re:Why I Like Google's Reorg and Why It's Only a Start
by another_ali on Saturday April 09, 2011 @03:41PM
(#2427927)
I think google is heading the way of SUN, they now make many nice products that add no obvious revenue streams!
What google really needs is to make products that make money and the re-organization need to be based around that, employee compensations and incentive should be based around how much money they make for google.
for example, unless its clear how much money the go lang will save for google, they should kill the project and just use C++ or Haskell or whatever!
I think the comment by spinchange sums this article up quite nicely "I think it must be much, much easier to write articles like this about managing Google than it is to actually manage Google.".
http://news.ycombinator.com/item?id=2427093
[1] http://investor.google.com/financial/tables.html
[2] http://www.google.com/+1/button/
[3] https://www.google.com/support/websearch/bin/answer.py?answe...
What google really needs is to make products that make money and the re-organization need to be based around that, employee compensations and incentive should be based around how much money they make for google.
for example, unless its clear how much money the go lang will save for google, they should kill the project and just use C++ or Haskell or whatever!