Earlyish facebook engineer here. Early days FB php was nothing like the php used to template websites. All kinds of specialized libraries to enable a much more sophisticated programming style. Think functional helpers, and asynchronous execution on thousands of cores, spanning trees across data centers using ssh etc. As a tangent a lot of the good stuff I used was written by Evan Priestley, who also did Phabricator and lots of other strong systems.
Can you speak to the onboarding and learning curve in that environment? What was the training like? What kinds of timelines did you experience regarding expectations as a new hire?
Asking because I’m curious about these early stage mega-tech companies that are working at a scale I can’t fathom.
>Early days FB php was nothing like the php used to template websites. All kinds of specialized libraries to enable a much more sophisticated programming style.
No idea if this was a credible leak of actual 2007-ish FB php, but it doesn't look like what you're describing.
I'm of course speaking from an outsider's point of view, but do you think PHP was a good option, or was it a "fitting a square peg into a round hole" situation?
> but do you think PHP was a good option, or was it a "fitting a square peg into a round hole" situation?
Facebook was founded in 2004. Whatever fancy tech you're thinking that would fit the round hole, it didn't exist then. They also never thought it would serve a couple billion of users one day, so they built it in whatever they had and knew at the time.
Same for Instagram and Python (they started with Django).
How they have used Instagram with Django is that they have replaced pieces of Django over time with custom parts which is a benefit of the design of Django.
Random question... whatever happened to that visual friend/network graph that used to load on a separate window? I always thought that thing was pretty neat to see
