News for hackers. Stuff that matters.
Re:Why I Don’t Work At Google by adityakothadiya on Friday May 28, 2010 @07:35PM (#1387970)
I think the correct title would have been - "Why I won't work at Microsoft, again.".

I don't think it's a valid argument against Google without having any data-points. I've seen many Startups also don't finish their features/products and throw away when they realize this is not the right thing to do.

Overall, don't generalize too much. Experiences are different for different people at different places.

Re:Why I Don’t Work At Google by antirez on Friday May 28, 2010 @07:47PM (#1388003)
Right, but look at google's recent history: more and more people, and in some way, less and less signal generated.

This is some truly unavoidable thing I guess, unless you do some radical stuff like splitting apart your company in different pieces, like anti trust itself would do?

Also for me is truly disturbing the idea of being able to select people that will do great stuff just using an interview. You can just check if they understand big O, can design things, and are actually able to code. This is already a result, but I bet this also creates a monoculture as this way you create a filter that is not just cool, but also bad in some way (IMHO this is why Google fails when trying to design stuff that are designed for the masses).

disclaimer: I got a request for interview from google two times and refused it, so I'm not frustrated about that or alike.

Re:Why I Don’t Work At Google by tensor on Friday May 28, 2010 @10:54PM (#1388256)
I disagree on the less signal part of your comment. To me, it looks like more and more signal. Since search, we've seen maps, mail, reader, chrome, android, app engine, big table, google docs, wave, google voice, a google branded phone, google fibre to the home for those lucky enough, prediction api, charts, dns services, @font-face directory, google home page, and others many others.

Sure, some of those have been buyouts. But overall that is a lot of signal as far as I'm concerned.

Re:Why I Don’t Work At Google by dangrossman on Saturday May 29, 2010 @03:50AM (#1388499)
Some? Only one or two things in that entire list originated at G.
Re:Why I Don’t Work At Google by xenomachina on Sunday May 30, 2010 @06:19PM (#1391211)
First, why does it matter what "originated" there? Many of the projects that didn't originate at Google wouldn't have seen the light of day if Google or someone with comparative capital hadn't acquired them. And actually, it's a bit ironic that you make this complaint here given the subject of the article, since acquiring startups is a way to hire people who are both smart and get things done.

"Originated" is also somewhat ambiguous. There are at least a couple of examples where Google was working on a project internally and saw a similar external project that they decided to acquire and merge with the internal project. Did the resulting project "originate" at Google? Even if you answer no, I think at least half of the items at that list still "originated" at Google.

Re:Why I Don’t Work At Google by studer on Saturday May 29, 2010 @03:46PM (#1389171)
Really? Just one or two things? Which ones?
Re:Why I Don’t Work At Google by babycakes on Sunday May 30, 2010 @11:01AM (#1390566)
[citation needed]
Re:Why I Don’t Work At Google by moultano on Friday May 28, 2010 @08:00PM (#1388031)
Google's strategy for most of it's projects for the last few years has been to subtly improve them without anyone noticing. Typically a half-dozen changes a week to search alone: http://www.nytimes.com/2007/06/03/business/yourmoney/03googl...
Re:Why I Don’t Work At Google by strlen on Friday May 28, 2010 @08:11PM (#1388056)
Google and Microsoft both do a great job shipping certain kinds of products. The teams that work on these products have influence, autonomy and ability (without middle management or PM interference) to ship products.

For Microsoft it's Office tools, development tools and operating systems. We may not like those products, nor wish to work on those teams irrespective (I'm a UNIX hacker, there's no way I'd be happy at Microsoft, lest they bring back Xenix), but I'd imagine those teams are great to work on.

For Google, it's obviously search, infrastructure (incredible competitive advantage for them), advertising system and other things Internet or networking (including Android, Chrome etc...). It's not their office or enterprise offerings (Google docs are useful, but they're popular because they're only game in town so far).

I wouldn't join Microsoft to work on online services or join Google to work on desktop or enterprise products (with exception of Chromium). I would imagine I'd be sidelined by management or technical leadership who is just not used to that particular type of software (e.g., if you make shrink wrap office software you'd be hesitant to adopt methodologies that involve daily pushes of code or see the value of making services highly available and fault tolerant).

Of course, I am open to hear arguments to the contrary (do you work on online services at Microsoft and find that you're able to "get things done" without interference? Ditto for desktop software at Google).

Re:Why I Don’t Work At Google by kenjackson on Friday May 28, 2010 @09:10PM (#1388152)
I don't work for MS, but I must admit I'm impressed with Bing. Is it better than Google? Maybe not, but it's still impressive. And they certainly seem to rev changes to it just as fast as Google is doing nowadays.

We'll see how Office online plays out. And don't forget that MS Online Services has like 40million paying customers.

They also do something called XBox Live and even Hotmail has gotten a little better over time. And I find Live Mesh to be the best cloud sync'ing app I've ever used. All in all, I think they're doing OK (not great, but OK).

Re:Why I Don’t Work At Google by strlen on Friday May 28, 2010 @11:25PM (#1388288)
> I don't work for MS, but I must admit I'm impressed with Bing.

That's not surprising, given the person running Bing is Qi Lu. There's a reason they brought in an outsider: they just couldn't afford to screw this attempt up.

I've had the enormous privilege of working in his organization at Yahoo (I still have no idea how I was able to fool my interview panel into hiring me straight out of college and into that group).

That experience gave me an extremely highly bar in terms of choosing engineering organizations to work for. There's only a couple of non-startup companies I am willing to work at after this experience: most everyone else - including non-search parts of Yahoo - just does not get how to run an online service and are unwilling to listen to a young punk like me :-)

Re:Why I Don’t Work At Google by jacabado on Saturday May 29, 2010 @06:12AM (#1388589)
So what do you look for when choosing those organizations? (And if possible how to do that, multiple interviews, experience period?)

Being in my second job right now my heuristics are: - Strong and clear team leadership - Fitness to value proposition, besides my work as a developer how well can I contribute to help improving the organization

Would love to hear from you how to be more selective.

Re:Why I Don’t Work At Google by holygoat on Saturday May 29, 2010 @02:03AM (#1388428)
I can't give details, but in my experience your view of Microsoft is incorrect.

If anything, the converse is true: core business teams offer less opportunity to do something great, because they're bigger and less flexible.

I didn't choose Microsoft, but I had an overly simplistic view of things.

Re:Why I Don’t Work At Google by olliesaunders on Saturday May 29, 2010 @07:52AM (#1388645)
Perhaps the more valuable takeaway from this piece is not whether Google or Microsoft have good hiring practices but how academic intelligence might be insufficient for success.

As someone who struggles to attain academic intelligence, I've focused on the other types. I've seen how that has held me back but equally I've seen how people stunning more bright than myself never reach their full potential and sometimes fail entirely.