Skip to main content

Personal: Working at Google--the Hard Way

I've always wanted to go work for Google the hard way--i.e. to work at a company and get acquired by Google. Metaweb just got acquired by Google. This is the second company that I worked at that got acquired by Google--after I left. The first was Mochi Media. Ugh.

Congrats to the guys at Metaweb! They have some really exciting technology.

Comments

metapundit.net said…
No no - think of this as a marketing opportunity!

I knew a guy growing up who was engaged three times and after the engagement was broken off the girl got married right away to somebody else. We always joked he ought to market himself as the cure for the single lady... Date me and you'll be married shortly after (just not to me)!
Anonymous said…
Do you think you could come work at our company for awhile, and then leave? ;)
jjinux said…
Haha. That's the laugh I needed. Thanks guys.

Darrin, that sounds like a good idea. However, if I decide to stay, it'll be a sure sign that your company isn't going anywhere ;)
jjinux said…
My buddy Krishna pointed out that Mochi Media wasn't bought by Google, but rather by a Chinese company:

http://techcrunch.com/2010/01/11/mochi-media-acquired-by-shanda-games/
jjinux said…
Oh, great, it just happened again!

"Google Buys Slide for $182 Million, Getting More Serious about Social Games": http://techcrunch.com/2010/08/04/google-buys-slide-for-182-million-getting-more-serious-about-social-games/

I interviewed at Slide years ago, and they made me a really solid offer. I decided to do something else mainly because I wanted to play around with TDD at a younger startup.

Ugh.

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p