Skip to main content

The Rise of Google, Part 17: Moonshots

Moonshots

🎬 Prefer to watch? Here's the 60-second version:

Watch on YouTube ▶

📚 The Rise of Google — a 20-part series. See all parts »  |  « Part 16: The Machine

By 2010, Google had already won the argument it started in a Stanford dorm room. Search was solved, the ad machine was printing money, and the company was big enough to buy almost anything it wanted. So Larry Page asked a stranger question than "how do we grow?" He asked: what would we build if failure didn't scare us?

The answer was a semi-secret lab called Google X — founded in January 2010, tucked into a building about a mile and a half from the main campus in Mountain View. Its first hire was Sebastian Thrun, the roboticist who had won the DARPA challenge for self-driving cars. Its mission, in the lab's own words, was to "invent and launch moonshot technologies that could make the world a radically better place." Not better products. A radically better world. The bar was deliberately absurd.

The moonshot formula

X didn't chase random sci-fi. It ran a formula. A true moonshot, the lab decided, sits at the intersection of three things: a huge problem affecting millions or billions of people, a radical solution that sounds like science fiction, and a breakthrough technology that gives you at least a fighting chance of actually building it. Miss any one and it's not a moonshot — it's either a fantasy or a normal product.

The man put in charge of enforcing that discipline was Astro Teller, whose actual job title is "Captain of Moonshots." (Yes, really. He rides a rollerblade around the lab.) Teller's genius wasn't picking winners. It was building a machine that could kill losers fast, cheaply, and without shame — before they burned years and hundreds of millions of dollars.

The one that flew

The lab's founding project became its crown jewel. The self-driving car effort, which began in earnest as the Google Self-Driving Car Project on January 17, 2009, was exactly the kind of bet nobody sane would fund: cars that drive themselves, on real roads, with no one touching the wheel. For years it looked like a very expensive science experiment. Test cars logged millions of miles around the Bay Area while skeptics rolled their eyes.

Then, on December 13, 2016, it stopped being an experiment. The project graduated out of X and became Waymo, a standalone Alphabet company. A decade later it wasn't a demo anymore — it was a paid robotaxi service running in multiple U.S. cities, carrying hundreds of thousands of riders a week in cars with no human driver at all. The moonshot had landed.

Waymo wasn't the only graduate. Wing, X's drone-delivery project, spun out in 2018 to fly packages to people's backyards. Verily left in 2015 to become Alphabet's life-sciences arm, working on everything from glucose sensors to surgical robotics. When an X project worked, the reward was independence — it got pushed out of the nest to become its own company.

The glorious failures

But most moonshots don't land. That's the point, and X built its whole culture around it. Teller preaches that if you want big wins, you have to make it safe to fail — so the lab celebrates the teams that kill their own projects. People get applause, and sometimes bonuses, for proving their idea won't work. Killing a doomed project early is treated as a victory, not a defeat.

The graveyard is spectacular. Project Loon spent a decade (2011–2021) trying to beam internet down from stratospheric balloons drifting 20 kilometers up, steered only by riding different wind layers. It genuinely worked — it delivered emergency connectivity in Puerto Rico and Peru — but it could never be made cheap enough to survive, and Alphabet shut it down in 2021. Makani chased clean energy with kites: a wing tethered to the ground, flying in circles to generate wind power. Google bought it in 2013, tried for seven years, and grounded it for good in 2020.

And then there's Google Glass — the face-mounted computer that launched to developers in 2013 and became a cultural punchline. Wearers got branded "Glassholes," privacy fears piled up, and the consumer version was shelved by 2015. (Glass quietly lived on for years as a factory-floor tool, proving that even a "failure" can find a smaller, useful life.)

Here's the thing critics miss: none of these were embarrassments to the people who ran them. A balloon that spanned continents, a kite that made electricity, a computer you wore on your face — each one pushed the edge of what was thought possible, and each one taught the next project something. X's bet was that a factory built to fail cheaply and often would, every so often, produce a Waymo. So far, it has.

Next time: the moonshots got so big and so strange that Google needed a whole new shape to hold them. In 2015, the company reorganized into something almost nobody saw coming — a holding company called Alphabet.


🔗 Explore more from Syncster

Comments

Popular posts from this blog

Cursor AI Review: Is the AI Code Editor Worth It?

I've been using Cursor as my main code editor for a while now, and enough people have asked whether it's worth switching to that a proper review felt overdue. Short version: for me, yes — but with caveats. What is Cursor? Cursor is an AI-first code editor built as a fork of VS Code. That means every extension, theme, and keybinding you already use in VS Code works here, but with AI woven directly into the editing experience instead of bolted on as a plugin. It's made by Anysphere and can run models from OpenAI and Anthropic under the hood. What I like Tab completion is uncanny. Cursor predicts your next edit — not just the rest of the line, but the next change across the file. Once you get used to hitting Tab, going back to a plain editor feels slow. The Composer / Agent mode. You describe a change in plain language and it edits multiple files at once, showing you a diff to accept or reject. For refactors and boilerplate, this saves real time. It unde...

MacBook Pro M5 vs M5 Pro: Which One Should You Actually Buy?

Apple's latest 14-inch MacBook Pro comes in two very different flavors: the base M5 and the step-up M5 Pro . On paper they look similar — same gorgeous Liquid Retina XDR display, same design — but under the hood the gap is bigger than the names suggest. Here's a clear, no-hype breakdown, with concrete use cases so you can match the chip to your work. Quick spec comparison Spec M5 M5 Pro CPU 10-core (4 performance + 6 efficiency) Up to 18-core (6 performance + 12 efficiency) GPU 10-core Up to 20-core Neural Engine 16-core 16-core Memory bandwidth 153 GB/s 307 GB/s (roughly double) Unified memory 16 / 24 / 32 GB 24 / 48 / 64 GB Max storage Up to 4 TB SSD Up to 8 TB SSD Battery (video playback) Up to 24 hours Up to 22 hours Media engines Single encode/ProRes engine More encode/ProRes engines (higher configs) What actually changes between them More cores — the M5 Pro nearly doubles CPU cores and adds GPU cores, so sustained, multi-threaded work finishe...

How I used Google Sheets and Apps Script

Google Sheet is one of the most powerful spreadsheet application that exists online, rivaling with Microsoft's Excel. One of the main strengths is its strong support for collaboration with other users, much easier and popular than collaboration tools with Microsoft Office. Aside from plain spreadsheet, it also supports extensions such as macro. If you are familiar with macros on other office tools, they work almost the same. However, the most extension I use and tinker with is the Apps Scipt . Apps Script Extension One of the challenges I faced recently is how do I track or monitor reports in our department if they are submitted on time or worst, forgotten due to lack of better monitoring tools. So I thought if there can be simple applications that can be deployed or use by a more general user to allow reminding periodically what reports are approaching due dates or those that are past dues. Then I looked for a way, instead of creating a full blown app from scratc...