Earlier quoted context omitted.
I thought he said perforce and git, not subversion and git.
Then corrected himself to subversion and git.
How Facebook pushes updates to the site
21–30 of 43 posts
Re: How Facebook pushes updates to the site
#22I like how their entire development cycle revolves around people getting drunk on weekends.
It's their entire business model as well.
"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.
Re: How Facebook pushes updates to the site
#23Was able to download this video with savevideo.me
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
#24It'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…
Re: How Facebook pushes updates to the site
#25Does anyone know if a non-video summary or set of slides for this video exists?
Re: How Facebook pushes updates to the site
#26It'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…
Re: How Facebook pushes updates to the site
#27Was 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.
not HD mode. stable chrome for mac 10.6.
Re: How Facebook pushes updates to the site
#28 git pull
lein uberjar
sudo restart myprjRe: How Facebook pushes updates to the site
#29This is how I push updates for now: git pull lein uberjar sudo restart myprj
git push web
http://toroid.org/ams/git-website-howtoRe: How Facebook pushes updates to the site
#30So 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.