Skip to main content

The Rise of Google, Part 19: The AI Pivot

The AI Pivot

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

Watch on YouTube ▶

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

For most of its life, Google thought of itself as a search company. You typed words into a box, and an algorithm ranked the web. That algorithm was clever — PageRank had, after all, launched an empire — but it was still rules written by engineers. Somewhere in the 2010s, the people running Google began to suspect that the future belonged to a different kind of software: one that learned for itself. This is the story of how a search company decided it was really an artificial-intelligence company.

A team that taught a computer to see cats

The pivot did not start with a grand announcement. It started with a small research group. In 2011, three researchers — Jeff Dean, Greg Corrado, and the Stanford professor Andrew Ng — began building a deep-learning team inside Google, the effort that became Google Brain. Their bet was unfashionable at the time: that old-fashioned neural networks, fed enough data and enough computing power, would suddenly start doing things nobody could program by hand.

In 2012 they proved the point with an experiment that became famous. They wired together a large neural network, pointed it at ten million still frames pulled from YouTube videos, and gave it no labels — no one told it what anything was. Left to find patterns on its own, the network invented, among other concepts, a neuron that lit up for cats. A machine had learned to recognise something without being taught the word for it. Inside Google, that was a lightning bolt: the same techniques could power speech recognition, translation, and image search.

Buying the future in London

If Google Brain was the pivot's engine, its imagination came from London. In January 2014, Google acquired DeepMind, a secretive research lab founded in 2010 by the neuroscientist and former chess prodigy Demis Hassabis, along with Shane Legg and Mustafa Suleyman. The reported price — around £400 million — was startling for a company with no product and no revenue. What DeepMind had instead was a mission statement that sounded like science fiction: “solve intelligence, and then use that to solve everything else.”

The purchase paid off in public and unforgettable fashion. In March 2016, DeepMind's AlphaGo sat down in a Seoul hotel against Lee Sedol, one of the greatest players in the history of Go — a game so vast and intuitive that experts had assumed a computer champion was still a decade away. AlphaGo won the five-game match 4–1. In the second game it played a move on the nineteenth line, “Move 37,” so alien that commentators assumed it was a mistake; it turned out to be brilliant. Two hundred million people watched a machine display something that looked unnervingly like creativity.

Giving the tools away

A quieter decision may have mattered even more. On November 9, 2015, the Google Brain team open-sourced TensorFlow, the software framework it used to build and train neural networks, releasing it free to the world under the Apache 2.0 licence. It was an odd move for a company famous for guarding its crown jewels. Why hand rivals your best machine-learning tools?

The logic was strategic. If TensorFlow became the language everyone used to build AI, then every student, startup, and university lab would be training a generation of engineers fluent in Google's platform — engineers who might one day work at Google, or build on Google's cloud. It was the same instinct that had made the company open early and often: shape the ecosystem, and you shape the future. TensorFlow quickly became one of the most widely used AI frameworks on earth.

“AI first”

All of this needed a leader who believed it. On October 2, 2015, as Google reorganised itself under the new holding company Alphabet, Sundar Pichai became chief executive of Google. Soft-spoken and product-obsessed, Pichai gave the pivot its slogan. The company, he said, was moving “from mobile first to AI first” — a world where machine learning would sit underneath every product, from Search to Photos to Gmail's uncanny ability to finish your sentences.

It was more than a marketing line. Behind it, Google was designing its own AI chips, weaving neural networks into translation and voice, and treating research labs as core infrastructure rather than expensive hobbies. The search box would remain — but it was now the front door to a company that had decided its real business was building intelligence itself.

The bet would soon collide with the messy realities of the physical world, of regulators, and of employees who did not all agree on where the line should sit. Next: the company's ambitions run into the questions of ethics, power, and trust.


🔗 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...