bar.foo

So now I finally know who made that awful smart compose thing in gmail [1] (the one that hides all but 2 lines of the message that you&#x27;re trying to write, most of the time): Maria what have you done ?!!!<p>[1] <a href="https:&#x2F;&#x2F;bar.foo&#x2F;gmail.html" rel="nofollow">https:&#x2F;&#x2F;bar.foo&#x2F;gmail.html</a>

&quot;It&#x27;s really an exciting field because you can have a group of 2, 3 or 4 people produce something that is used by hundreds of millions or billions of people using your software and benefiting from the capabilities that it has. There are very few careers where small groups of people can have this kind of influence...&quot;<p>Why do they need tens of thousands of engineers, then?

Nice try, Google, but most of us are not willing to relocate to the overpriced and not very family-friendly areas where your offices are.

As a correlation to this site, there is a secret programming challenge within google at: <a href="http:&#x2F;&#x2F;www.google.com&#x2F;foobar&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.google.com&#x2F;foobar&#x2F;</a><p>You have to get invited to it (via searching the correct keywords, etc. I got invited when googling about dependency injection). It is a series of programming challenges that get really difficult. But after completing them, I got a final round interview at Google, which was pretty cool.

Maybe it&#x27;s too early on a Monday and my reading comprehension is off, but I&#x27;m not sure I get the point of this. Is this just a fancy blog for engineering stories as a means of hiring more engineers? If so, I&#x27;m not sure the magazine-like reporting style is speaking to me here. I&#x27;d much rather see these types of stories in a first-person, conversational blog format. But maybe I&#x27;m missing the point, or I&#x27;m the wrong target.

To me the most interesting of these was the solution to collaborative editing in Google Docs. Sadly the description provided is a helicopter view. It appears to reference OT[1] and is suggestive of the event sourced pattern[2]. My interest is piqued; can anyone reference an in-depth publication&#x2F;paper on the D&amp;I of their &quot;collaboration engine&quot;?<p>[1] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Operational_transformation" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Operational_transformation</a><p>[2] <a href="http:&#x2F;&#x2F;martinfowler.com&#x2F;eaaDev&#x2F;EventSourcing.html" rel="nofollow">http:&#x2F;&#x2F;martinfowler.com&#x2F;eaaDev&#x2F;EventSourcing.html</a>

Minor factual correction: The Google Docs article on this site says &quot;When Google launched Docs in 2012&quot;... but Docs launched way earlier than that (Feb 2007 according to <a href="https:&#x2F;&#x2F;www.google.com&#x2F;webhp?q=when%20did%20google%20docs%20launch" rel="nofollow">https:&#x2F;&#x2F;www.google.com&#x2F;webhp?q=when%20did%20google%20docs%20...</a>).

Such hover, Much animation.

Someone should tell those bright engineers that hover doesn&#x27;t work on mobile.

How do I register a .foo domain? Namecheap asks me to &quot;make offer&quot; and various other domain registrars ask me to &quot;pre-order&quot;.

Cool site, but it&#x27;s really too bad Google isn&#x27;t willing to open up offices outside of California (like, say, Portland? :) ). I&#x27;d like to see them innovate the remote teams space, but maybe that&#x27;s too difficult a challenge for them?

where can you get a foo domain... all my google searches came up with nothing.

Regardless of the content the design of that website is pretty great. The pages load almost instantly! Can anyone with more front-end knowledge tell me what&#x27;s going on under the hood?

Off-topic in a way but discovered through this domain&#x27;s nic.foo : Interesting that Google now has .google but search.google isn&#x27;t a thing yet. :)

Must be getting desperate to find talent.

This fails to resolve for me:<p><pre><code> Host bar.foo not found: 2(SERVFAIL)</code></pre>

they really needed to register a .foo TLD for this?

Your comment follows a worrying trend I&#x27;ve been seeing on HN:<p>1) Start humbly by saying you might be wrong &#x2F; you&#x27;re not sure &#x2F; ...<p>2) Criticize the work showed in the link from your personal opinion, without real arguments.<p>3) End in the same way: &quot;Just saying.&quot; &quot;I hope I&#x27;m wrong&quot;.<p>Yes, this &quot;just a fancy blog for engineering stories as a means of hiring more engineers&quot;. I&#x27;m not sure how one can say such a precise thing without being sure.

Headline should be:<p>bar.foo: Stories from software engineers at Google

Most comments here are so off topic. No one has so far discussed about opportunities at Google and how can one get in.<p>Let&#x27;s take this as a challenge guys