One thing that turns me off of seriously pursuing a career at Facebook is PHP.

I haven't learned PHP yet (and I'm only in college), but I've heard bad things about its design, and it seems to be overshadowed by Ruby and Python in my programming news sources.

Is PHP a dying language? Even if it is, it makes sense for Facebook to continue using it instead of throwing out all their code.

But it seems like it might be a waste to spend time at Facebook using PHP if the rest of the tech and start-up world has moved on.

I'm going to apologize in advance if any of this seems too stern or rude.

You seriously don't have the correct mindset about this. You are thinking in a way that a lot of other people share, but it's not practical. In the real world you have to learn new technologies and languages consistently. Every day something new comes out or gets improved that makes doing a difficult task easier, and people/companies that can adapt and not be left behind do well.

If I were in your position (which I guess I kind of am, I'm also college-age but I've spent just under half my life doing some level of professional programming) I would be learning EVERYTHING I can or at least everything mainstream I can so that if I come by a cool piece of code online or at work I can tell exactly what it does.

It's true that PHP isn't as a strictly written language as some of the other languages (by this I don't mean syntax, I mean that doing two analogous operations have completely different names/attribute orders in the standard library) but it's still used by tons and tons of people. PHP isn't dying. I hate the term "dying language" because there's always something else out there that's good for that each specific language.

I'm assuming that Flash is also "dying" in your POV but just today I had to whip up a quick SWF to allow copying something to a user's clipboard because it was the simplest and quickest way to allow one-click clipboard access that I could think of and I have spent time learning Flash/AS in the past so I had that knowledge.

Now, when you say:

  it seems like it might be a waste to spend time at Facebook using PHP if the rest of the tech and start-up world has moved on

I have no idea what you mean. Do you mean that Facebook not restructuring their entire codebase to a cooler and more popular language is a waste of Facebook engineers time? Or do you mean that you learning PHP to work at Facebook would be a waste of your time? I don't understand how either of these two statement could be argued so if you meant something else I'd love a clarification.

There is absolutely nothing that Facebook can not do with PHP that they could do with Python or Ruby. Any business logic can be written in a myriad of ways. And I believe to be a strong candidate for a "wow" employee after you graduate you should be able to drop head first into any codebase and at the very least quickly get a simple grasp of what's going on.

If Facebook gave you an internship today would you reject it because you've heard bad things about PHP?

Sorry about the rant, but I've spent a lot of time working to hire other developers and it really irks me when I hear something like "oh so and so's a dying language, it's useless to learn it" because it shows that you don't have the drive and love of technology that my ideal person would.

I do want to learn lots of different technologies, including PHP! That's part of the reason I read Hacker News in the first place.

But I'm doubtful of its real-world application these days. Most news I see never mentions it, but Ruby and Python are mentioned near constantly.

I'm sure working at Facebook would be amazing. I mean, it's Facebook. But if I also got internship offers at Google and other high-tech companies, then the language I use at work will factor in.

And PHP doesn't seem nearly as significant as these other languages, so then why take a job where I'll learn and use it in-depth for months when there are other languages?

You're going to be sorely disappointed when you find out that the majority of user-facing applications at Google are in Java, which you'll hear even less of on places like here.

The reason you don't see mentions of PHP all the time on places like here is that Python and Ruby are considered "hip" languages right now. Every one and their mother wants to learn it to show off how cool it is. Which is freaking awesome because the more people that learn nice scripting languages the better, but it means people aren't being driven to build new services on PHP to show off because instead of listing off 10-20 buzzword plugins by other people, you have a limited amount of mature things you can use to make a PHP application. This is not saying that Python and Ruby don't have mature platforms and extensions.

Have you done any professional programming in the past? I absolutely guarantee that even doing an short term internship at a company using a programming language you don't know, the nuances of that specific language won't be what you take away from you but rather the different ways to think about a specific problem.

Maybe once every month I face a problem at work or on personal projects where I can say "Hey, I remember this, it's a really obscure PHP fault!" versus many many times a times a day when I think "hmm I could build this as a singleton or a factory or a ....." and can use my previous experience programming in those fashions at previous jobs to figure out what the best way to do it currently is.

Learning a new language isn't about dedicating your life to it. It's about learning new methods of completing tasks, which you can almost always apply to other languages.

It's fairly easy to construct a portfolio of web applications in whatever language you want to use and/or demonstrate competency in a language (eg contribute to open source), but it's much more difficult to say you worked on an application at the scale of Facebook. That experience is invaluable and the lessons you learn there are applicable even when you move on to applications in other languages.

You should also probably look at surveys of language adoption b/c PHP has much greater market share. Hacker News is a very skewed sample.

Wow, this could be a troll.. don't know.. clever.

If PHP is putting you off considering working at Facebook, then it may be useful to know that there are many developers who hardly ever touch PHP at Facebook.

Most back-end services (ie, the systems that build your feed, or detect spam) are in C++. Java is used in some back-end services (including, for example, in Hadoop, Hive, HBase, and the messaging product) and for the Android app. Objective C is used for the Facebook app, Messenger, Camera, and so forth on iOS. Python is used primarily in the automation and operations space. You will also find a bunch of Ruby, Haskell, Scala, and so forth around.

I am not generally a fan of PHP and much of the ecosystem around it, but using it at Facebook is very different. I also would not say that time spent learning and using PHP is time wasted - the important things to learn typically transcend language, and learning anti-patterns / deficiencies is useful too. That is also why Facebook does not expect any particular language knowledge before you start/when you interview.

You are vastly overvaluing experience in a particular language or technology. None of the languages you mentioned are particularly hard for someone to pick up fairly quickly (even more so if you already know one of the others). Being a good software engineer is largely orthogonal to which languages you have experience with.

Try explaining that to startups who want rockstar, ninja, sith lords in language X. Libraries, on the other hand, do take some time to learn.

I felt the same way when I started at Facebook. The thing I've learned, though, is that your language choice is very far down the list of important factors. Most important: the problem you are solving and the quality of the engineers you work with.

Underlying your question is the idea that the specific language you work with is an investment that's critical to future success. Whether this is true depends a lot on what kind of career path you want.

I've found that lower quality jobs are the most specific about languages - "Must have 5 years of Java 1.5 or above experience" should be a huge red flag, because that place is hiring based on years-of-ass-in-chair rather than skills.

Some companies seem to be looking for specific language skills - "We're looking for great python hackers" it might say. But this is often just marketing and doesn't mean they won't take a someone who can show excellence in other ways.

There are exceptions of course - if you are doing low-level systems work, it would be expected that you know the ins and outs of C, and I'm sure there's other examples in other specialties.

One last thing: it's always useful to get experience with a range of languages, and that will pay off down the road when you have to learn language N+1. At Facebook I've written (in descending order of volume): PHP, Javascript, Python, C++ and Haskell.

PHP still runs most of the highly trafficked Web sites on the Internet.

Rails is a permanent train wreck. The other hundred of Ruby-based Web frameworks are adequate for small, CRUD-style applications. (BTW, I like Ruby. It's a neat little language.)

In the end, it's either PHP or J2EE in 90% of the cases for high-uptime, high-traffic Web destinations.

No one at Facebook is under the impression that PHP is a particularly good language, but it does the job. What really matters are a libraries and abstractions that you'll actually be interacting with. At Facebook these are leagues ahead of any other PHP codebase I've seen.

You should read what Andrei Alexandrescu has to say about the language here: http://www.serversidemagazine.com/news/10-questions-with-fac...

Unless you anticipate working for only the hottest start ups utilizing the latest buzzwords, dismissing PHP entirely might be a bit premature. It's still hugely popular with plenty of employers looking for developers with PHP experience.

There are plenty of eng jobs at Facebook that require no PHP. In more than two and a half years there I wrote probably 50 lines of PHP.

Thanks for posting this! That's what I was looking for I guess; people who actually have concrete points why they like this. I think Facebook is doing a great job at gathering talent and that's something I would like to learn about.

I like your work definitely. Guess a lot of engineers would; I'm curious to know how much significant work you'll be doing if you apply now (jump through the hoops), get in and want to work on HipHop (as recent graduate). What are your options within Facebook; how far can you grow?

Facebook, with few exceptions, allows you to pick your team. If you really want to work on something, you can. As for your last question, I joined a year ago, and from my experience, the meritocracy is extremely alive and well. You can go far, and get there very quickly, if the fit is right, and you are kicking ass.

Reading between the lines of your posts, I think you might have a pretty inaccurate view of facebook, as it currently is. Facebook has fewer engineers than you think, and it's -really- easy to have massive impact on features, or even the org as a whole, from day 1. Most of the teams responsible for major features/products are quite small. Some are frighteningly small. In many places, there are huge, ambitious, crazy ideas currently on the shelf waiting for 2-3 new people to join the team to take on.

Yes I think I have an inaccurate view; that's why I'm posting here to find out from the people inside and there are some really insightful points here.

One shall find happiness at all costs, anywhere it can be found.

But, I wish for brilliant, hardworking people a better endeavor than a CRUD Web site.

> work like animals.

This is good because?

Most large mammals other than humans sleep or relax a large portion of the day and are only active a relatively short time for hunting (work) and eating. So one could interpret his statement as saying that they work short, focused hours and then go home to relax.

My info is anecdotal from my wife, who has spent a significant portion of her life working with bears. But from the zoo keepers I've met, that mammal breakdown is true for most of the felines and primates as well.

My anecdotal evidence from the startup world, though, says that most people in a "startup" like Facebook work very hard and very long hours at the same time. I think your description is a very good way to work, but I sort of doubt that this is an accurate description of life at Facebook :P

Because I find it fun. If you don't, that's perfectly cool, too.

That is totally cool, however - just for perspective, other people are not in their early 20s, fresh from college with no experience in other large silicon valey companies for the past 20 years.

Others: they ave 2+ kids, have been through many IPO/M&A debacles and may have gone through ridiculous divorces, major swings in their marketability or simply been screwed over by certain companies...

They hype around making tons of money can be subdued by the realities of life in between these relatively rare miollionairing events.

Thus, qualities of work other than "working myself to the bone because this company will be the next google IPO" become a big factor. This is why HP, Yahoo, MS, and others continue to attact talent - although it might represent an aging trend.

There will always be more wily generations in the tech industry. Learn, earn and avoid smugness.

I am 35 and have a wife and family. And it is not my first time at the tech company rodeo either.

Avoid smugness indeed.

it's either evidence they're passionate or they're forced to work long hours. given the context i'm assuming the former. which is certainly a good thing...

"Passionate" does not necessarily mean you work long hours "like animals". Obsessive usually does.

Working pass the normal cut-off is a lose-lose proposition for anyone that puts in honest levels of work during the day. You burn yourself out, diminish your capacity, make mistakes, and most of the time don't even realize it. This can go on for years, sometimes even decades.

Most of the referenced-here "passionate" behavior is probably a combination of unhealthy focus (the obsessive type or the type you use to forget about your issues), self-image, having-to-prove-something, and outside-pressure (expectations for you, matching your co-workers, etc).

The better option is to work intelligently and maintain a healthy amount of self-awareness at all times. Then leave it, shut-off, or go enjoy something that matters.

You'll produce 200% the results of your "passionate" co-workers.

PHP is one of those "developer productivity languages?" I mean, this way be just a huge sin I'm about to commit, but really? I think most of the world see this whole HipHop deal as you guys had all this PHP and you need to optimize it. The idea that the syntax and style of the PHP language is one of the most well suited languages to solving general computing problems ... I just find that hard to take seriously.

Please don't mistake me: PHP-the-language is not well-designed. And we absolutely would never have gone down this road if we didn't have a metric ton of PHP to run and continue developing.

There are a few things PHP gets accidentally right, though, and one of them is the execution model. Each request starts with a brand new empty PHP environment; runs in a single thread to completion; and must keep persistent state off to the side in a database or memcache or what have you rather than in language-level objects. This turns out to have been a really good set of decisions. It lends itself to a nice tight development loop: instead of save/recompile/restart the server/test, you basically save/load the page. It's easier to remember what the heck you were doing when you get feedback on the code you wrote in 500 milliseconds.