PRAGMATIC DEVELOPMENT AT STACK OVERFLOW
summary
Stack Overflow measures everything and optimizes where the data proves it matters: live per-request timings via MiniProfiler, HAProxy log queries, Bosun GC graphs and SQL-server query-plan monitoring catch hotspots. Generating specialized methods for tag-filtered lists speeds pages by about 20% over a generic check for 10 million questions. Deployments use git → dev → canary servers, per-server feature switches and an alpha channel for limited rollout across 150 sites; SQL tuning and GC reductions repeatedly cut latencies in production.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:00Public Announcement
- 1:17Pragmatic Development
- 3:59Architecture
- 4:51Why Is It So Complicated
- 5:52Coding Style
- 9:46Batch Processing
- 14:40Premature Optimization Is the Root of all Evil
- 15:17What Does Premature Optimization Mean
- 16:38Stack Overflow
- 26:46Exceptions
- 27:22Sequel Server Monitoring Tool
- 31:37Jon Skeet Problem
- 32:53Garbage Collections
- 44:44Pluralistic Management
- 47:41Jobs
related talks
45mStack Overflow - It's all about performance
25mHow to win at StackOverflow
45mStack Overflow - It's all about performance
28mGetting the most out of Stack Overflow
01h 00mScaling Silos: Distributing Knowledge
24mBottom up org change and evolution
29mSearch-First Writing for Developers
31mThe future of Stack Overflow as the most vital source for technologists
