10 Things I Love About Engineering at Facebook
summary
A dev server exists from day one so work happens over SSH and an Atom/Nuclide remote IDE without cloning or installs; the codebase lives in a mono repo accessed with hg and arcanist diffs reviewed in Phabricator; releases use feature flags via Gatekeeper to change exposure in minutes; internal beta testing on employee devices called dogfooding exercises thousands of devices; hackathons run several times a year, teams own dashboards and weekly on‑call rotations catch and fix production issues.
AI-written summary · about
chapters (35)
- 0:00Intro
- 1:28Starting at Facebook
- 1:57What is a Software Engineer
- 2:23Disclaimers
- 3:15Dedicated dev server
- 4:24Web Browser
- 4:48Remote Access
- 6:03Mono Repo
- 6:56Cochairing
- 7:18Team Collaboration
- 8:27Ifs
- 9:08Web Tool
- 10:01Summary
- 10:47Logs
- 11:19Feature Gating
- 11:37Conditions
- 12:04Gatekeeper
- 12:58Stacking
- 13:24Dogfooding
- 14:30Communication
- 14:49Workplace
- 15:49Celebrations
- 16:17Instant Messaging
- 16:55HPNS
- 17:53Hackathons
- 18:39No hackathon organizer
- 19:23Fixer thongs
- 19:46Tech debt week
- 20:26Oncall shifts
- 21:46Bug reporting
- 21:58Porting
- 22:25Feedback
- 23:04Employee Feedback
- 23:31Peer to Peer Reviews
- 24:00Outro
related talks
01h 03mDeveloping C++ @ Facebook Scale
10mOpening Remarks
32mCode First, Ask Questions Later
40mMove Fast and Ship Things
35mThe importance of Engineering Systems: How to Build Efficient ...
46mWhen Software Becomes Everyone's Job
59mTech leadership, one year after
36mThe Production Engineering Lifecycle: How We Build, Run, and Disband Great...