Slashdot Mirror


Xooglers - Google Discussed by Ex-Googlers

perler writes to tell us that Xooglers, a relatively new website created so that ex-Google employees could reminisce and share, has been gaining a great deal of popularity recently. The website shares what went wrong, what went right, and all of the funny happenings in between. Quite an interesting piece of Google history.

23 of 211 comments (clear)

  1. Why "ex" googlers? by cytoman · · Score: 4, Interesting

    I assume that being a Google employee represents the highpoint of your career and you would never want to leave...like one of the xooglers says, why become a boring specialized cell when you can be a stem-cell and take on any and every challenge thrown at you?

    If *I* get a Google job, I am never leaving!

    1. Re:Why "ex" googlers? by Anonymous Coward · · Score: 5, Insightful

      If *I* get a Google job, I am never leaving!

      So easy to say about a company until you have actually worked there. Not saying that working at Google wouldn't be cool, but you never know what little things here or there might be a frustration at your job. What about an annoying boss? Hard schedule? Your employers aren't always going to accommodate you to fix a problem, no matter where you work.

    2. Re:Why "ex" googlers? by nandu_prahlad · · Score: 4, Interesting

      If *I* get a Google job, I am never leaving!
      Never say never. As Lennon said, "Life is what happens to you while you're busy making other plans". Suddenly, working for Google (or some other great company) may not seem like great idea as before because your interests have shifted, or you may wanna spend more time with your family.

    3. Re:Why "ex" googlers? by hyeh · · Score: 5, Interesting

      I'm a Xoogler myself, and personally, I find my current job more fulfilling from a personal/learning/growth standpoint. Just my two cents.

    4. Re:Why "ex" googlers? by roach2002 · · Score: 5, Informative

      From the blog (Ron's first post)

      I guess the #1 FAQ for people who have left Google is why did you leave. My main reason for leaving was that I was commuting from Los Angeles. I'd fly up on Southwest early Monday morning, fly back on Thursday evening, and telecommute on Fridays and weekends. That regimen was pretty stressful even under the best of circumstances, but when 9/11 happened it became completely untenable. I had already given my notice before 9/11, but I don't think I could have stayed on after that even if I had wanted to. But I'm getting ahead of myself.

      So that's why Ron left, I'm not sure if Doug's said why he left yet.

    5. Re:Why "ex" googlers? by moorcito · · Score: 4, Funny

      "....You know that thing on the internet you look at, I helped make that...."

      I don't think just ex-google employees will be the ones telling their kids/grandkids that. Just think about all the porn stars.

    6. Re:Why "ex" googlers? by koltrane · · Score: 5, Interesting
      Honestly, you people think working for Google is like playtime and that no one would ever have problems there. I felt the same way about working at McDonalds when I was 8.

      Any successful business is just that...a business, and all the adolescent fantasies of corporate ski trips and pool tables in the break room aside, work has to be done. A job at Google is not a panacea for the workaday blues. I'm sure it's a very nice and creative environment, but I remember a lot of dot-com companies that sneered at traditional business practices, opting instead for lavish salaries, non-standard work hours, jacuzzis in every office, and multi-million dollar IPO parties. We all know where they are now...how much is that theGlobe.com stock worth now?

      Not to say that Google is such a company. They obviously have their heads on straight, but don't kid yourself into thinking that no one in his right mind would ever want to leave, because Google ain't perfect.

  2. One line ... by RebelWithoutAClue · · Score: 4, Funny

    "How long does it take the sauna to get hot? You think it's okay to go in the women's locker room to get some towels since we're out in here?"

    --
    "However beautiful the strategy, you should occasionally look at the results" - Winston Churchill
  3. News? by logik3x · · Score: 4, Insightful

    So how is this news? this is just publicity for a blog. It's not because there is the word google in the story that you have to post it. You can mod me down if you want but this is true... maybe if the blog was something new ok but it's old... it's been around for a while...

    1. Re:News? by Tony+Hoyle · · Score: 4, Funny

      This is slashdot. Anything with google in the title is published - often before anyone's even bothered to read it.

      Future slashdot titles:
      Google to buy microsoft
      Google to buy AOL
      Google finds cure for cancer
      Google starts space programme

  4. Scroll down by rolfwind · · Score: 4, Insightful

    to the "Let's get a real database" comment. It's nice to see such a good comment over MySQL by pros. Back in 2001/2, when I was considering to start a DB project for my own amusement, I heard almost nothing but bad things over MySQL by PostSQLers or Oraclers due to missing features though I went with it anyway.

    BTW, it's not a slam on those others systems, but I feel the missing feautures debate usually gets out of proportion to actual use of said feautures by the average project by a small/mid-size business.

  5. Not quite by SuperBanana · · Score: 4, Insightful
    The website shares what went wrong, what went right, and all of the funny happenings in between.

    No ScuttleMonkey- it's what a bunch (more specifically: TWO. "Doug" and Ron") of ex-employees think went wrong, think went right. I've seen ex-employee websites/mailing lists and been on them. They're petty, rarely accurate (I saw wild claims made I knew were false) and so on.

    I am no fan of Google, but why is anyone giving ANY credence to what two guys have to say? I see nothing to verify they are who they say they are.

  6. Why they quit... by satchmodian · · Score: 5, Informative

    I browsed through the whole damn blog trying to figure out why each of the two guys that write the blog quit. One said "I guess the #1 FAQ for people who have left Google is why did you leave. My main reason for leaving was that I was commuting from Los Angeles. I'd fly up on Southwest early Monday morning, fly back on Thursday evening, and telecommute on Fridays and weekends. That regimen was pretty stressful even under the best of circumstances, but when 9/11 happened it became completely untenable. I had already given my notice before 9/11, but I don't think I could have stayed on after that even if I had wanted to. But I'm getting ahead of myself." From what I could tell, the other one, "Doug", made a decent chunk of change in stock options and doesn't have to work anymore. Probably the same is true for the first guy also.

  7. I'm sorry, I must have missed something here. by radiotyler · · Score: 4, Insightful

    I understand Google is a seemingly great company to work for and a pioneer in the search engine world. But why did I even waste the time to read though that "Back in ought one when I was still at Google.." garbage? I think I was hoping for some juicy tidbit that only blog readers would be privvy to, something secretive that I would never expect to happen to the employees of Google. Instead, I got a nice voyage down memory lane - getting to listen to people reminisce about things I was never there for in the first place.

    I don't know if this qualifys as either "News for Nerds." or "Stuff that Matters."

    --
    hi mom!
  8. well then by caffeinemessiah · · Score: 5, Funny
    I am an engineer at heart. I get a real kick out of watching something that I've built work. And the 'plex was the perfect environment, filled with smart, friendly people, state-of-the-art equipement, and half a dozen different kinds of coffee machines. (I actually had some interesting conversations about the finer points of espresso making, and at one point someone even brought in a book that was entirely devoted to the topic.)

    Well LAAA-DEEE-DAAAAA. Excuse the rest of us who couldn't get past the 3rd round of interviews! We'll just continue in our windowless labs/cubicles here, sucking down on 35 cent coffee from a vending machine perpetually on the fritz.

    --
    An old-timer with old-timey ideas.
  9. If you read the stuff by putko · · Score: 4, Interesting

    You'll see there's a lisper who left JPL because managers decided to follow "best practices" of industry and move to C++. This is despite the fact that programming a space mission isn't a "standard" problem -- it is, in fact, a problem that a language like LISP is excellently suited, because people can deal with unclear/dynamic requirements as a project evolves.

    So he goes to Google because they have some LISP guys there (not using LISP -- just smart guys) -- and then he gets told to do the first Java project. And later he gets told that LISP is out of the question.

    And in fact, he details how a race condition in the C++ memory management leads to them billing clients nonsense amounts -- a problem that simply couldn't happen if they'd used a language like LISP (or Java) -- because the GC wouldn't reclaim something if the thing was still in use.

    So Google can yet be beat -- they are not perfect. Of course, that doesn't mean there is anyone to beat them, yet.

    --
    http://www.thebricktestament.com/the_law/when_to_s tone_your_children/dt21_18a.html
    1. Re:If you read the stuff by putko · · Score: 4, Informative

      "According the blog, AdWords was written in Java, not C++. I didn't find the author said it's caused by race condition."

      I guess you missed this:

      Ron sez... oh wait, don't need that any more.

      OK, time to wrap up this little soap opera.

      The problem turned out to be something called a race condition, which is one of the most pernicious and difficult kinds of bugs to find. (Those of you who are technically savvy can skip to the end.)

      Most modern server code is multi-threaded, which means that it does more than one computation at once. This is important because computers do more than just compute. They also store and retrieve information from hard disks, which are much, much slower than the computers. Every time the computer has to access the disk things come to a screeching halt. To give you some idea, most modern computers run at clock speed measured in gigahertz, or billions of cycles per second. The fastest hard disks have seek times (that is, the time it takes the drive to move the read/write head into the proper position) of several milliseconds. So a computer can perform tens of millions of computations in the time it takes a hard disk just to get into position to read or write data.

      In order to keep things from bogging down, when one computation has to access the disk, it suspends itself, and another computation takes over. This way, one computer sort of "pretends" that it is really multiple computers all running at the same time, even though in reality what is happening is that one computer is just time-slicing lots of simultaneous computations.

      The ad server, the machine that actually served up ads in response to search terms, ran multi-threaded code written in C++, which is more or less the industry standard nowadays for high-performance applications. C++ is byzantine, one of the most complex programming languages ever invented. I've been studying C++ off and on for ten years and I'm still far from being an expert. Its designers didn't really set out to make it that complicated, it just sort of accreted more and more cruft over the years until it turned into this hulking behemoth.

      C++ has a lot of features, but one feature that it lacks that Lisp and Java have is automatic memory management. Lisp and Java (and most other modern programming langauges) use a technique called garbage collection to automatically figure out when a piece of memory is no longer being used and put it back in the pool of available memory. In C++ you have to do this manually.

      Memory management in multi-threaded applications is one of the biggest challenges C++ programmers face. It's a nightmare. All kinds of techniques and protocols have been developed to help make the task easier, but none of them work very well. At the very least they all require a certain discipline on the part of the programmer that is very difficult to maintain. And for complex pieces of code that are being worked on by more than one person it is very, very hard to get it right.

      What happened, it turned out, was this: the ad server kept a count of all the ads that it served, which it periodically wrote out to the database. (For those of you wondering what database we were using, it was MySQL, which leads to another story, but that will have to wait for another post.) It also had a feature where, if it was shut down for any reason, it would write out the final served ads count before it actually quit. The ad counts were stored in a block of memory that was stack allocated by one thread. The final ad counts were written out by code running in a different thread. So when the ad server was shut down, the first thread would exit and free up the memory holding the ad counts, which would then be reused by some other process, which would write essentially random data there. In the meantime, the thread writing out the final ad counts would still be reading that memory.

      --
      http://www.thebricktestament.com/the_law/when_to_s tone_your_children/dt21_18a.html
  10. Re:obvious question by greginnj · · Score: 4, Funny
    So I'll reserve my trust regarding this site... for the same reason that I can't imagine a blog site of my ex-wives to be perfectly honest about me.
    I find your ideas intriguing and I would like to Subscribe to your newsletter.
    --
    Read the best of all of Slash: seenonslash.com
  11. Re:obvious question by roach2002 · · Score: 4, Informative
    FTFB:

    From the blog (Ron's first post [blogspot.com])

    I guess the #1 FAQ for people who have left Google is why did you leave. My main reason for leaving was that I was commuting from Los Angeles. I'd fly up on Southwest early Monday morning, fly back on Thursday evening, and telecommute on Fridays and weekends. That regimen was pretty stressful even under the best of circumstances, but when 9/11 happened it became completely untenable. I had already given my notice before 9/11, but I don't think I could have stayed on after that even if I had wanted to. But I'm getting ahead of myself.

    So that's why Ron left, I'm pretty sure Doug hasn't said why he left yet. So no, Ron wasn't fired.

  12. RTFB by vectorian798 · · Score: 5, Interesting

    A lot of you are pointing out that these are just random ex-Google people (or even that we have no proof they ever worked there) but there are some good points brought out in the articles. I think the majority of posters who are complaining about the blog or the accuracy of a blog are just randomly posting in hopes of points/Google-whoring rather than actually reading what was linked to. That being said,...

    While those outside Google might disagree with the ultimate decisions the company has made, they should know that those decisions were not made without reflection on the consequences. One of my goals with Xooglers is to expose the nature of that debate. I agree with Matt that providing more transparency into how difficult decisions get made within the Googleplex can only enhance the brand. It's not enough to say you're not evil; you need to show the world how you define evil and how you choose to avoid it.

    Well put don't you think? Indeed a large portion of slashdotters tend to believe Google is the messiah and that they are not an 'evil' company. But let's face it, 'evil' is different from person to person and to vaguely portray one company as evil and another as not is ridiculous. To many, MS won't seem evil - after all, a lot of people use their products and are damn satisfied with them. To still others, the fact that Google supports OSS means nothing and they want only excellence of product (BTW don't start a tangential reply about MS products not being excellent blah blah).

    The moral of the story is that sometimes, and in particular with free software, you get more than what you pay for. There are a lot of companies out there paying dearly for commercial databases (and operating systems for that matter). As far as I'm concerned they might as well be flushing that money down the toilet. Actually, they might be better off. We certainly would have been. As an aside, there is a raging debate in the hacker community about the overall economic merit of the open source model. (Making money producing free software is quite a challenge.) I am not taking sides in that debate here. All I am saying is that from the end user's point of view free software is often much better than the producers of commercial software would like people to think.

    Again, a good point - there are some OSS that are good, others that aren't. But what I want to point out is that Google did go for non-OSS software at one point - suddenly, it seems like Google was making a decision from the standpoint of "What would be best for us?" (the fact that the ACTUAL decision they made was wrong and they returned to OSS later is irrelevant BTW) correct? Indeed, they are a business. While no one here can likely say for certain, we certainly shouldn't assume that because of Summer of Code or other opened material that Google is supporting OSS (btw I am not an advocate of OSS nor am I an opponent, so please don't think I am being biased) or that it is "not evil".

    My 2 cents

    PS: When people bring up databases and talk about MySQL, PostgreSQL, or Oracle, they often ignore some other big players: MS's SQL Server and IBM's DB2. Don't start a thread about the different relational databases half-assedly plz.

  13. Re:Opening a Window to Google.... by Drakonian · · Score: 4, Insightful

    Get real. That guy signed an NDA and posted sensitive financial information on his blog that was cleary marked as confidential. He deserved everything he got. This wasn't typical "my free latte was so great this morning", this was material information.

    --
    Random is the New Order.
  14. The trouble with Google: they're an ad agency by Animats · · Score: 4, Interesting
    Sadly, what Google really is an ad agency that uses a search engine as a traffic builder. It's a very good search engine, but fundamentally, Google is an advertising-delivery system.

    If they'd gone private instead of going public, they could have been a very profitable near-monopoly, sustained by the fact that it doesn't really cost that much to run a search engine, and thus, their ad content can be minimal. But now they have to produce a reasonable return on investment for their overblown market cap. So they have to add more and more advertising-oriented services, from catalogs to classifieds. This dooms them to become more like their competitors in those spaces.

    It's not going to be fun to work there as the profitabilty vise closes.

  15. Let Them Eat Google by TallMatthew · · Score: 4, Interesting
    The one thing that stood out to me reading this guy's blog was how nostalgic he was for the place. He was practically weepy. That attitude makes me nervous. Yeah, it's a company based on innovation with plenty of smart people running around being smart and acting silly. It's also a multibillion dollar corporation. That doesn't make it evil, necessarily. But being a thinktank doesn't make it good, necessarily. When I read accounts of this place that make it sound like heaven, I wonder what the deal is. Behind most panaceas is a bunch of people getting played. Is building a better search engine really such a noble pursuit? Maybe.

    Google is doing a fine job sucking up talent. Not just the big fish like Cerf, but the more clued individuals in our industry. Working at Google has become something of a status symbol, something akin to having a CCIE. Oh, you worked at Google? You must be good. I've noticed one thing that results from this. There seem to be more senior positions open in the Bay Area, New York, everywhere Google has significant footprint. Too, the annual salaries for these positions has risen about 20%, presumedly out of demand.

    For that, I can say ... thank you Google!