News for hackers. Stuff that matters.
Re:Working at Google - the first 6 months by adbge on Thursday June 17, 2010 @05:22PM (#1440395)
Google sounds more and more like a boys club lately. I think some of the employees need to come back down to earth and realize that not everyone at Google is a coding rockstar and there are people doing more important work than Google.

Of course, I've never worked at Google, so maybe they all are coding rockstars and save the world on a daily basis. I find that thought a little unsettling though.

Re:Working at Google - the first 6 months by angelbob on Thursday June 17, 2010 @05:48PM (#1440484)
The "boys club" analogy doesn't end there. According to several of my female techy friends who have worked there, it's a pretty awful place to work if you're female, in terms of sexual discrimination.

At least one of them experienced, consistently and repeatedly, behavior that she could easily have sued over despite multiple complaints to HR.

Re:Working at Google - the first 6 months by kenjackson on Thursday June 17, 2010 @06:03PM (#1440543)
One of the things I've learned is never report things like that to HR. Report them to the police.

The job of HR is not to help you, the employee. It is to protect the company. The more credible your complaints to HR look, especially if there was some negligence in your management chain, the more they will try to damage your story or credibility. That's their job.

Re:Working at Google - the first 6 months by dschobel on Thursday June 17, 2010 @10:52PM (#1441171)
Helping the company and helping the harassed are not exclusive. If there is someone who is truly harassing employees, it behooves the company to get rid of them as quickly as possible because people like that are a tremendous liability.

I know a number of people who work in employment law and I hear stories all of the time how getting accused of sexual harassment will get you rail-roaded out of any modern workplace.

I'm sure there are some totally degenerate companies which will try to cover it up and discredit the accuser, but I can't imagine a place look google is one of them.

Besides all of which, sexual harassment suits are civil suits so I'm not sure what you expect the police to do.

Re:Working at Google - the first 6 months by kenjackson on Friday June 18, 2010 @12:06AM (#1441298)
"Helping the company and helping the harassed are not exclusive. If there is someone who is truly harassing employees, it behooves the company to get rid of them as quickly as possible because people like that are a tremendous liability."

You would think, but reality is sometimes different. The problem is that these things are often he said/she said, and HR does not want to do anything that creates the appearance that one-side is telling the truth, because this opens them up. Or if there was negligence in the past, this makes them vulnerable to federal law. Or if they have a pending lawsuit. I'm not saying every company is out to screw you, but why take an unnecessary chance?

And sexual harassments suits are civil suits (that's kind of a tautology), but sexual harassment itself can be criminal. This is a common incorrect belief you noted. It can even be a felony in some cases. This is why I suggest talking to the police (or an attorney) as you're not likely to know the law in your state (and there is also federal law on the books too).

And why don't you imagine Google is the type to cover something like this up? Is it because of their motto? I don't have as much faith in multibillion dollar corporations as you do.

Re:Working at Google - the first 6 months by Jun8 on Thursday June 17, 2010 @10:19PM (#1441106)
That's awful! I hate HR, too, but to report what you perceive as harassment directly to the police seems so over the top as to be ridiculous.
Re:Working at Google - the first 6 months by hugh3 on Thursday June 17, 2010 @11:38PM (#1441249)
Unless it's actually, say, rape. In which case by all means bypass HR and go to the police.

Though you should probably report it to HR as well.

Re:Working at Google - the first 6 months by Jun8 on Thursday June 17, 2010 @10:21PM (#1441113)
It's 20K people and you're hiring the geek squad, there's bound to be weird people. However, from what I've seen, they were very sensitive about this, especially the women/men employee ratio. I was told during a visit some years ago that this was about 40%. I found that incredible.
Re:Working at Google - the first 6 months by nostrademons on Friday June 18, 2010 @12:28AM (#1441340)
It's probably 40% overall, but that includes large concentrations of women in HR and sales. I've heard that engineering is about 10% female. They also tend to clump together on certain teams, for some reason: my first two teams (and second cubicle) were each about 40% female, then my last two teams have been 100% male, at least among the engineers.
Re:Working at Google - the first 6 months by hugh3 on Thursday June 17, 2010 @07:38PM (#1440794)
I'm not surprised. I can imagine that many of those engineers cooped up in the googleplex for the vast majority of their waking hours, not leaving for lunch, not leaving for dinner, might kinda start to forget how to interact with women altogether.
Re:Working at Google - the first 6 months by nostrademons on Friday June 18, 2010 @12:25AM (#1441336)
You do know that there are women engineers, right?
Re:Working at Google - the first 6 months by martincmartin on Thursday June 17, 2010 @06:46PM (#1440677)
What are the great products to come out of Google? Search, of course. Google Maps, and with it, AJAX: pretty impressive. GMail too.

But Google Earth was an acquisition. So was YouTube, despite the effort they put into Google Video. So was Google Docs word processor, although the spreadsheet was home grown.

Google has, what, 20,000 engineers? That's a LOT of effort for what they have to show for it.

Re:Working at Google - the first 6 months by strlen on Thursday June 17, 2010 @09:57PM (#1441064)
> Google has, what, 20,000 engineers? That's a LOT of effort for what they have to show for it.

That criticism would hold true if Google were a pure product company. Salesforce is a great example of this: in their SIGMOD/SoCC keynote they've mentioned they only employ 200 engineers. They don't face the sort of scalability and algorithmic challenges that warrants developing custom infrastructure: they use of the shelf commercial products and open source products (Oracle RAC, Lucene).

At Google that great deal of work goes into amazing internal infrastructure that is rarely read about (I'd imagine the published papers are only the tip of an iceberg) i.e., people hacking on the kernel, on file systems, on databases, firmware etc... This infrastructure is their competitive advantage and their moat. At Salesforce, their ability to out execute competitors (via aggressive selling and marketing) on an innovative but not inventive business model.

In the case of Google, being a major contributor to the Linux kernel, they're effectively their own operating systems vendor. With BigTable, MegaStore, Spanner, their MySQL patches and more, they're their own database vendor. With Chubby, GFS, MapReduce, their own web server, etc... they're their own distributed middleware company. They're also one of the largest hardware manufactures, with themselves as their only consumer.

In terms of their core competencies (search/IR/ML), they're an incredible research organization. Not all research results in products, but they've been able to productize their research much more effectively than Microsoft has (perhaps at the cost of having a less theory and more systems focused research organization i.e., employing Rob Pike but not Leslie Lamport).

I have a feeling it's great to be a researcher or an advanced developer (working on infrastructure or algorithms) at Google: you have the capability to focus on actually building incredible pieces of software. In terms of application development, it might be slightly less appealing (although, I've been extremely impressed with Android, Chrome and Gmail as _finished products_ too).

Of course, if someone's _primary_ goal out of a job is to become an enterpreuner and found their own company, going to Google may not be the best place for this (other than for making connections and gaining credibility much like going to Stanford): building an infrastructure start-up is much more difficult than building a web application start-up. For those who are first and foremost technologists (that would be me), Google still symbolizes the "ideal" job: perform incredibly advanced development (implicitly frowned upon in most product companies) and build practical, working software that gets put to production use (implicitly frowned upon in research centers and academia). At one point one such place was AT&T Bell Labs, at a later point it was Sun. Now that place is Google.

Re:Working at Google - the first 6 months by mquander on Thursday June 17, 2010 @07:13PM (#1440744)
Google Reader is best in its class, in my opinion (although I have dozens of RSS feeds, not hundreds.) Google Books is great and represents a huge amount of effort. I don't know where Blogger came from, but Google has had it for a long time; Chrome is fantastic and getting better fast; Google's machine translation of webpages seems to be getting better constantly. Google App Engine, Google Scholar, Google Voice (acquired recently, though,) Google Code (good until Github ate its lunch in my opinion.)
Re:Working at Google - the first 6 months by hugh3 on Thursday June 17, 2010 @07:27PM (#1440776)
Okay, but apart from Google Search, Google Maps, Gmail, AJAX, Google Earth, YouTube, Google Scholar, Google Calculator, Google Apps, Blogger, Google App Engine, Google Voice, Google Code, AdWords, Google.org, Google Video, Froogle, iGoogle, Google Translate, Google News, Google Image Search, MapReduce, Google Finance, Google Calendar, Chrome, Android, Orkut, Picasa, Knol (OK, forget Knol), Sketchup, Latitude, and Google Pacman, what else has Google done for us?
Re:Working at Google - the first 6 months by moted on Thursday June 17, 2010 @07:45PM (#1440817)
Wave :)
Re:Working at Google - the first 6 months by mkramlich on Thursday June 17, 2010 @11:25PM (#1441225)
20k employees / ~30 products = 666 employees per product

that sounds about right! :)

Re:Working at Google - the first 6 months by slug on Thursday June 17, 2010 @10:08PM (#1441085)
Romanes eunt domus!
Re:Working at Google - the first 6 months by kprobst on Thursday June 17, 2010 @11:53PM (#1441277)
Blogger was an acquisition, Pyra Labs. App engine was also an acquisition, as is Google Docs (Writely, I think).
Re:Working at Google - the first 6 months by nostrademons on Friday June 18, 2010 @12:43AM (#1441362)
I think your perspective may also be distorted by all the famous products out there.

I worked on Google Wonder Wheel, which had a tiny, startup-sized development team. Probably 99.5% of you have never heard of it. However, the people that do use it really like it. Enough that they complained when we temporarily disabled it for the recent visual redesign, another project I worked on. It has orders of magnitude more users than Bingo Card Creator, and has generated orders of magnitude more revenue for Google. Yet you hear about BCC all the time on HN, while maybe once every 6 months somebody might mention Wonder Wheel.

Re:Working at Google - the first 6 months by pk2200 on Thursday June 17, 2010 @10:21PM (#1441112)
Here are a few enormously successful (and highly complex) products that you missed:

1-2) AdWords and AdSense revolutionized web advertising. Those two products generated $6.5 billion in revenue just in Q1 of 2010.

3) Android. Others have commented that this was an acquisition, but that happened in 2005, and it was a relatively small team. I'd wager that most of the current Android code was written after the acquisition, and by engineers who weren't from the original Android team.

4) Chrome.

Regarding the number of engineers, Google had 20,000 employees as of March 2010. You can make your own guess about how many of them are software engineers, but it's a lot less than 100%.

Re:Working at Google - the first 6 months by gthank on Friday June 18, 2010 @11:17AM (#1442452)
Chrome is built on WebKit, so it's not a Google-from-scratch the way search, etc. are.
Re:Working at Google - the first 6 months by shalmanese on Thursday June 17, 2010 @07:00PM (#1440701)
Google Maps was also an acquisition.
Re:Working at Google - the first 6 months by mikepurvis on Thursday June 17, 2010 @07:26PM (#1440772)
It was acquired young, though, and has been completely rewritten at least once. And as of three years ago, none of the originals were still working on it. Lars went on to build Walkabout/Wave, and I'm not sure what happened to Jens.

In any case, I consider Google Maps to be through and through a Google product.

Re:Working at Google - the first 6 months by hugh3 on Thursday June 17, 2010 @07:28PM (#1440778)
Does it matter if it was an acquisition? I assume they acquired most of the engineers with it, so it's a partial answer to "what the hell are all those engineers doing?"
Re:Working at Google - the first 6 months by cma on Thursday June 17, 2010 @06:59PM (#1440699)
Another acquisition, but how about Android?
Re:Working at Google - the first 6 months by rayval on Thursday June 17, 2010 @07:06PM (#1440720)
Android was also an acquisition.
Re:Working at Google - the first 6 months by cma on Friday June 18, 2010 @10:55AM (#1442386)
That's why I said "another acquisition". Android was presumably a less developed acquisition, and the team was significantly beefed up inside Google before producing any first results. Or is that way off?
Re:Working at Google - the first 6 months by nostrademons on Friday June 18, 2010 @12:33AM (#1441347)
"there are people doing more important work than Google."

I think there are people doing more important work than Google, but I think that very few of them are in the computer industry. I have immense respect for teachers, doctors, nurses, tradespeople, babysitters, etc. But people in financial software, SEO, Web 2.0, defense software? You think that what they're doing is more important than search?

Re:Working at Google - the first 6 months by e40 on Thursday June 17, 2010 @09:05PM (#1440962)
How about a "young, unmarried, with no kids boys club"? I can't really see having a family being compatible with this.
Re:Working at Google - the first 6 months by nostrademons on Friday June 18, 2010 @12:55AM (#1441382)
If you have a family, you simply don't stay for dinner. You work 9-5 and go home to your family at night. Oh, and take advantage of the awesome health plan ($0/month HMO, or something like $25/month PPO), long maternity/paternity leave (it's something like 6 weeks of paid paternity leave, and several months of maternity leave), flexibility to schedule your time so you can make it to all of your kid's events, free shuttle so you don't waste all your time commuting, job stability, and relatively generous salaries.
Re:Working at Google - the first 6 months by plinkplonk on Friday June 18, 2010 @12:57AM (#1441386)
"relatively generous salaries"

This seems new. Last I checked, Google offered (relatively) low salaries.

Re:Working at Google - the first 6 months by starkfist on Friday June 18, 2010 @12:57AM (#1441387)
It pays pretty well for experienced people.