3 ms·
Well, a lot of this is the flip side of FaceBook's "changes are pushed to the live site as soon as they're checked in" policy. That lets them innovate quickly,
by nostrademons 17y ago
Well, a lot of this is the flip side of FaceBook's "changes are pushed to the live site as soon as they're checked in" policy. That lets them innovate quickly, but also means that whenever anyone screws up, it's immediately visible in a very public way. Other companies have release processes and QA procedures to stop this.
- MartinCron 17y agoOn the whole, I think the rapid innovation model tends to make things safer overall. Tiny changes can be rolled back more easily, or patched more easily. Release processes and rigorous QA procedures seem more appropriate for client-deployed software like operating systems than for centralized web applications.
- u238 17y agoEvery single line of code is peer reviewed by at least 2 people before it can be pushed.
- studer 17y agoBut tested by nobody? What happens to the reviewers that let this thing slip through, btw?
- derwiki 17y agoFrom chatting with a few Facebook engineers, I'm pretty sure it's not quick to get checked in code -> production (unless it's super urgent)