Building Software Systems At Google and Lessons Learned

Why HN readers recommended it

HN recommends it as a classic look at systems engineering at Google, whose fundamentals have held up well despite its 2010 date.

This is a summary from the source dataset, not an endorsement by Hacker News or the video creator.

Video & recommendation details

Creator / channel

Stanford

Topic

large-scale systems design

Format

lecture

Level

intermediate

HN recommenders in dataset

4

HN mentions in dataset

5

Recommendation years in dataset

2012–2022

These counts and years describe the included Hacker News records; they are not YouTube views or the video’s publication date.

From the original HN conversations

Excerpts from the recorded comments. Follow each source for the full comment and surrounding discussion.

• In addition to Linus's git talk, I really enjoyed Jeff Dean's EE380 retrospective on Building Systems at Google ( [VIDEO] ). Many people have mentioned Jeff's basic premise elsewhere ("Design a system for 10x your current need, but not 100x, rewrite it before then") but …

• Also recommend Jeff Dean's tech talk Building Software Systems At Google and Lessons Learned which references those latency numbers. Slides: [LINK] Video: [VIDEO] Also, a previous thread on latency numbers: [LINK]

• There is a lecture from Jeff Dean about it: [VIDEO] It's from 2010, but the fundamentals probably haven't changed.