/
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

Twitter by the Numbers

Yesterday I gave a talk at UC Berkeley as part of Twitter's recruiting efforts (known as @TwitterU).  I was asked to put together a tech talk, so I wanted to use this as an opportunity to de-mystify Twitter a bit.  A lot of people ask me “what's so hard about sending 140 characters”?

mehack Raffi Krikorian

Context & Ripple Effects

When commentators asked how basic Twitter really was back in 2007, the question was about the product; three years on, the question a Twitter engineer fields is why sending 140 characters is hard at all. The company's answer is now part of its campus pitch: a @TwitterU tech talk at UC Berkeley frames Twitter's infrastructure problems as a reason to join rather than a liability.

The timing matters because Twitter has spent August and early September 2010 tightening its platform — an OAuth mandate that stripped stored passwords from all third-party apps by August 31, a new Tweet Button for sharing links, and an iPad app — while CEO Ev Williams reported sharp usage growth and counted roughly 300,000 registered apps, commentary notwithstanding that few of them matter materially.

First-order effects

  • Twitter's recruiting arm gets a direct pipeline into UC Berkeley's engineering talent, with the demystified scale story serving as the hook for candidates weighing offers.
  • The thousands of third-party developers who scrambled to meet the August 31 OAuth deadline are the audience whose reliability concerns this kind of public engineering transparency helps reassure.

Second-order effects

  • Bay Area competitors hiring for the same distributed-systems skill set now face a rival whose growth curve — per Williams — makes hard infrastructure problems a selling point rather than a warning sign.
  • If the talk lands with students, Twitter's campus brand compounds the developer goodwill built by moves like the Tweet Button, lowering the cost of both future hires and future platform decisions.

Third-order effects

  • Should the pattern hold, consumer web platforms will increasingly treat engineering-scale storytelling as standard recruiting currency, the way product launches once were — a shift visible in how Twitter pairs platform control (OAuth) with openness rhetoric (300,000 apps).

The trend: Fast-growing consumer platforms are converting their hardest infrastructure problems into recruiting narratives, making engineering credibility a competitive asset alongside the product itself.