I once went to a info session that Facebook put on at our school (this was trying to attract coop students). One of the things that the previous coops, as well as the recruiters/presenters emphasized was the lack of formality and 'set' procedures. One coop recalled how he was directly responsible for a 20 minute downtime in facebook because he pushed something to production after testing it locally a bit.
Yeah, no real testing servers (they exist, but aren't actually required), no real dedicated QA, none of the usual trappings. The coop laughed it off. And the recruiter did too, and pointed out that a lot of responsibility is placed directly on whoever is coding the code. They're even the flexibility and freedom to do what they think they should do, and if it causes a little downtime? As long as its short, and nothing is lost, no problem. It's something to laugh at at the bar.
Now, I'm sure there's some embellishing going on there to ensnare more young minds, but I even if its half true, I think this anecdote provides a lot of insight into how facebook works. Perhaps many of the little privacy things isn't the result of Zuckerberg deciding that everyone doesn't need control, it's just the individual programmer placing it lower on their priorities to even think about, and there being no real overarching structure to impose these privacy concerns.
Until it gets released to production and 'blows up' in their face.
Yeah, no real testing servers (they exist, but aren't actually required), no real dedicated QA, none of the usual trappings. The coop laughed it off. And the recruiter did too, and pointed out that a lot of responsibility is placed directly on whoever is coding the code. They're even the flexibility and freedom to do what they think they should do, and if it causes a little downtime? As long as its short, and nothing is lost, no problem. It's something to laugh at at the bar.
Now, I'm sure there's some embellishing going on there to ensnare more young minds, but I even if its half true, I think this anecdote provides a lot of insight into how facebook works. Perhaps many of the little privacy things isn't the result of Zuckerberg deciding that everyone doesn't need control, it's just the individual programmer placing it lower on their priorities to even think about, and there being no real overarching structure to impose these privacy concerns.
Until it gets released to production and 'blows up' in their face.