/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

The technology inside the Google self-driving cars

You've probably heard that Google has these cool cars that can drive themselves.  Above is a video of one of them driving down Freeway 280 that I shot almost a year ago (I had no idea I was driving next to a car that was capable of driving itself.

Scobleizer Robert Scoble

Context & Ripple Effects

Google's self-driving program went public in October 2010 when the New York Times reported that Google cars drive themselves in traffic, revealing a fleet that had been testing quietly for some time. Scobleizer's contribution is firsthand corroboration: footage shot on Freeway 280 almost a year earlier shows one of those vehicles operating in live California traffic — next to a driver who had no idea the car beside him could drive itself.

That gap between the footage's date and the announcement date is the story within the story: Google was accumulating real-world freeway miles long before disclosing the program, meaning its lead was built on public roads rather than closed tracks. The piece also lands amid a burst of Google activity that week — the Facebook data-portability standoff, new Chrome extensions, Gingerbread's InvenSense-powered motion processing — underscoring how widely the company was pushing into hardware-adjacent territory beyond search.

First-order effects

  • Scobleizer's video turns an abstract New York Times report into visible proof that Google's autonomous prototypes operate unannounced on public freeways among ordinary, unaware drivers.
  • Google gains a public-demonstration asset at zero cost to itself: independent eyewitness footage does the credibility work that a corporate press release cannot.

Second-order effects

  • Regulators and highway authorities now face questions about liability and oversight for a testing program that ran on public roads before any formal public accounting of its rules of engagement.
  • Automakers watching a search company validate autonomy on real freeways face pressure to answer whether their own driver-assistance roadmaps can match what Google has already demonstrated in traffic.

Third-order effects

  • If unannounced public-road testing proves out, the durable competitive asset in autonomy shifts from building cars to owning the perception infrastructure and software stack that accumulates driving data — a layer Google is positioning itself to hold.
  • A precedent forms for technology companies rather than carmakers defining the pace and terms of autonomous-vehicle development, forcing regulators to write rules after deployment rather than before.

The trend: Autonomy is moving from closed-track demos to quiet, large-scale testing on public roads, with technology companies rather than automakers setting the pace.