How Facebook Engineers work

Now if you mention Facebook, then I think no one knows its existence and its value. The world's largest social network application company is already on the Nasdaq IPO. Although you can learn about their work environment and corporate culture from many tech websites and even gossip magazines, I don't think you know how the Facebook engineers actually work. And as the most attractive high-tech talent of this company, they have what fan son?

I can be sure that the most valuable property of Facebook is engineers. They have been using high-quality code to create a different user product experience. So what exactly is a Facebook engineer like? A Google employee, Yee Lee, once posted a post on Facebook, and to talk to everyone about the topic, the post was lengthy and widely watched by netizens, with thousands of employees involved in the discussion. They also share what Facebook employees like to do, what they don't like to do, how powerful they are, and so on.

Most of the 1.Facebook employees are engineers

Facebook's employees come from two big teams-engineers and OPS. They occupy the general number of the company.

2. Have a large number of product managers

The responsibility of the product manager is to ensure that the project is completed on time, and 7-10 product managers are required for each project to achieve this goal.

3. It all started with the "new Staff training camp" (Boot camp)

All new recruits have a 4-6-week training period during which they need to learn Facebook-style corrections and listen to senior staff lectures.

In addition, Facebook's new training camp has a high rate of elimination, with about 10% of people unable to pass or being told to leave.

4.Facebook employees gain access to the database

Having greater power means great responsibility, which Facebook employees agree on, because any engineer can check the code and arbitrarily modify the database.

In addition, employees have a special power, similar to sharing user data. But Lee says there are still a lot of security measures to prevent this from happening.

5. Like Google, here is an engineer-driven culture

"Product managers are basically useless here," says one engineer, Lee writes.

Engineers here are very powerful, a project in progress can be arbitrarily modified, reschedule work item specifications, add new function concept, these as long as the engineers feel the need, at any time can be.

6. Engineers meet every month to show their work across departments

Product Marketing managers and product managers attend these meetings, but do not encourage speaking out. "In fact, if you say too much, it will delay a lot of time, and feedback to the leadership of the problem is basically the original has been made clear."

Facebook wants engineers to be able to share their products openly, and that's why the products they create are more inspirational and humane, Lee wrote.

7. The collection of project resources is purely voluntary

Engineers basically decide what they want when they work at the company. If they need anything, they need to talk to their manager and say, "These are the five things I want to do at work."

The product manager lobbied the team's engineers to try to get them excited about the project, but most of the engineering management engineers had a very strong preference.

8. Whether engineers design prototypes are worth arguing for different implementations

It takes a week for engineers to build a feature on Facebook, and then they need to rely on more sophisticated tests to decide whether it's worth it. Usually the testers are Facebook employees.

This is an important part of Facebook's "hacker" culture-quickly building and delivering products, but running is not their job.

9. Everyone wants to work on Facebook's back-end process

On Facebook, scalability and basic work are the most interesting questions that engineers find.

So those former products, such as news stories, are hard to get excited by engineers, Lee writes, and instead, every engineer likes to study the problem of news algorithms.

10. Mark Zuckerberg will review the news feeds for every code update

This is one of the most important features of Facebook. All major updates require mandatory code review, and all changes are attended by at least one person. But Zuckerberg will also review the feeds for each code update.

11. No formal Quality assurance team

Engineers are responsible for testing product features, bug fixes, and post release maintenance, but this is not a formal quality assurance team.

Facebook still has QA engineers and strongly encourages all engineers to report errors.

12. By default, the code is updated in Tuesday

If you work hard enough, your code will be published, but you can change it in a day.

Facebook has thrusters for code changes, but it's risky for code risk, so it's more risky to be mature.

13. The Operation team introduced a slow code update

Facebook has about 60000 servers, so the operations team will gradually use the code from several servers to ensure it works properly.

But at first 6 servers were shut down, and then there were more, and engineers were needed to fix the necessary problems.

14. Ignore the results of the operations team and openly humiliate

During release, if a code needs to be submitted for modification, the operations team uses IRC and other forms of messaging to communicate with the engineer.

By joining you with the code, and not around them, they will publicly humiliate your code, Lee wrote, although there are many details about the issue, but if the company found a similar situation, it can be dismissed. (Wang Chunlong/application state Via BI)