Skip to main content

The Rise of Google, Part 3: From BackRub to Google

From BackRub to Google

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

Watch on YouTube ▶

📚 The Rise of Google — a 20-part series. See all parts »  |  « Part 2: BackRub: The Algorithm That Ranked the Web

Every great company has an origin myth, and Google's has an unusually good one: a search engine named after a massage, a company named after a spelling mistake, and a $100,000 check made out to a business that did not legally exist. None of it was inevitable. In the summer of 1998, two Stanford graduate students had a brilliant algorithm, a growing pile of borrowed computers, and no real intention of becoming founders. Then someone wrote them a check they couldn't cash — and everything changed.

BackRub: the name nobody would have kept

Before it was Google, it was BackRub. When Larry Page began his 1996 research project at Stanford, the whole idea rested on backlinks — the notion that you could measure a web page's importance by counting and weighing the pages that linked to it. Page thought the name was clever. It captured the mechanism exactly: the web rubbing its own back, every link a small endorsement of another page.

BackRub ran on a patchwork of machines scattered around the Stanford campus, crawling the young web from a single starting point — Page's own home page. Sergey Brin soon joined, bringing the mathematical firepower to turn that tangle of links into the ranking system they called PageRank. The project worked almost too well. It devoured bandwidth, occasionally knocked Stanford's network offline, and steadily convinced its two creators that they had built something the existing search engines couldn't match. What it didn't have was a name anyone would want to type into a browser forever.

How a spelling mistake became a brand

The rename came out of a 1997 brainstorming session in a Stanford graduate lab. The founders wanted a word that captured the sheer scale of information they hoped to organize. A fellow student, Sean Anderson, suggested googolplex; Page countered with the shorter googol — the mathematical term for a 1 followed by 100 zeros. It was a perfect metaphor for a search engine meant to wrangle an unimaginably large web.

Then came the accident that stuck. Checking whether the domain was available, Anderson typed the word the way it sounded rather than the way it was spelled: google.com. It was free. Page liked the look of it, and on September 15, 1997, google.com was registered. One of the most valuable brand names in history began life as a misspelled math term — and to this day, "google" is the everyday word while "googol" is the trivia answer.

The check written before the company existed

By mid-1998, Page and Brin faced the classic Stanford dilemma: keep going as academics, or turn the project into a company. They were reluctant. They tried to license their technology to the existing search players and got little interest — nobody yet believed that better search was worth much money. So a mutual acquaintance arranged a meeting with Andy Bechtolsheim, a co-founder of Sun Microsystems and one of Silicon Valley's most respected hardware minds.

They met early one morning in August 1998 on the porch of a Stanford faculty member's home in Palo Alto. Bechtolsheim watched a quick demo, grasped immediately what PageRank could do, and — short on time — cut the conversation short. Rather than talk terms, he pulled out his checkbook and wrote a check for $100,000, made out to "Google Inc."

There was just one problem: Google Inc. didn't exist yet. There was no company, no bank account, nothing to deposit the check against. As the story goes, the check sat in a desk drawer for weeks while the founders scrambled to make the paperwork real. That single signature turned a research project into a startup almost against its creators' will. To cash it, they had to incorporate — and on September 4, 1998, Google Inc. was formally founded. Bechtolsheim's bet would eventually be worth billions.

A garage in Menlo Park

With money in the bank and a legal entity to hold it, the fledgling company needed a home — and it found one in the most Silicon Valley way possible. In September 1998, Page and Brin rented the garage of a house at 232 Santa Margarita Avenue in Menlo Park for around $1,700 a month. The landlord was Susan Wojcicki, then a recent business-school graduate who would go on to become one of Google's most important executives and, later, the CEO of YouTube.

The garage came with a few perks the founders appreciated: a washer, a dryer, and a hot tub, plus enough room to pile in desks, servers, and the occasional ping-pong table. It was cramped, chaotic, and unmistakably a beginning. The check had forced them into being a company; now they had an address, a name spelled slightly wrong, and a hundred thousand dollars of someone else's faith to spend.

Next up in Part 4 — The Founding: the paperwork becomes real, the first employees walk into that garage, and a two-person research project starts learning how to be a company.


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