Live data from Hacker News

How Facebook pushes updates to the site

facebook.com

21–30 of 43 posts

Re: How Facebook pushes updates to the site

#22

I like how their entire development cycle revolves around people getting drunk on weekends.

It's their entire business model as well.

JWZ suggests:

"How will this software get my users laid" should be on the minds of anyone writing social software (and these days, almost all software is social software). "Social software" is about making it easy for people to do other things that make them happy: meeting, communicating, and hooking up.

http://www.jwz.org/doc/groupware.html

Re: How Facebook pushes updates to the site

#23
post #11

Was able to download this video with savevideo.me

This actually wound up being a helpful comment. After switching to HD in order to see his text examples more clearly, I found out that the session starts over from the beginning and you can't fast forward the video at all.

This meant that I had to either stop watching halfway through so that I didn't have to sit through the same half-hour again, or rip the video so that I can watch it like a human.

Re: How Facebook pushes updates to the site

#24
post #9

It's interesting that their entire release architecture seems to be focused on never pushing bad things out to production, whereas given their traffic they could probably push things out much sooner (minutes after they're committed) to small parts of their overall traffic, and slowly increase the traffic on those pieces of code as they prove themselves to be stable, or quickly revert them if they're not. That would m…

Cherry picking based on which engineers are around is much more about our daily releases. Everything checked into trunk on Sunday will go out on Tuesday. But if I've requested a diff be merged for the Wednesday release, it won't happen unless I've told request_bot that I'm around to support my changes. This also means that if there are merge conflicts, the engineers who wrote the patches will be there to help resolve them.

Re: How Facebook pushes updates to the site

#26
post #9

It's interesting that their entire release architecture seems to be focused on never pushing bad things out to production, whereas given their traffic they could probably push things out much sooner (minutes after they're committed) to small parts of their overall traffic, and slowly increase the traffic on those pieces of code as they prove themselves to be stable, or quickly revert them if they're not. That would m…

"they could probably push things out much sooner (minutes after they're committed) to small parts of their overall traffic, and slowly increase the traffic on those pieces of code as they prove themselves to be stable, or quickly revert them if they're not." The risk to user data is way too high. This could have serious consequences. You could push client bugs with erroneous API calls, or server-side bugs that cause…

This is correct, especially for a company under the level of government privacy scrutiny as Facebook. An erroneous push that exposes private user data could lead to a very heavy fine.

Re: How Facebook pushes updates to the site

#27
post #23
post #11

Was able to download this video with savevideo.me

This actually wound up being a helpful comment. After switching to HD in order to see his text examples more clearly, I found out that the session starts over from the beginning and you can't fast forward the video at all. This meant that I had to either stop watching halfway through so that I didn't have to sit through the same half-hour again, or rip the video so that I can watch it like a human.

i fast forwarded with no problem. just click to where i wanted to start watching in the video.

not HD mode. stable chrome for mac 10.6.

Re: How Facebook pushes updates to the site

#30
post #4

So they don't really test the code, they just push it out, and fix the bugs on Thursdays. Genius strategy. No wonder their platform breaks so often.

The code is tested. There are unit tests, Watir tests, tests written by the developer for that specific change, and all changes require a test plan from the engineer.

We prefer the term "watirboarding".
Post reply on HN