Three-month summary of LinkedIn work

Time Flash, already spent more than three months in the new company. Nothing special happened during the period, that is, it is more busy and the rhythm is faster.

The first code changes were submitted in less than a week, and the second week was reviewed to push the changes to the existing code base. For three months, several Starling have been built, new features have been added, and nearly half of the code has been refactored, and unit tests have been added. The middle also time to take effective Java second Edition read again. Overall the harvest is very big. It also made some low-level mistakes that the old programmers see as common sense, with two main ones:

1, if the method is public, do not change its signature. Even if you change everything you see in this way, there might be someone else in a secret corner with this method, which will break the code of others. The better way is to deprecate the current method and write a new method. After a while to delete this deprecated method. Be aware of the change's forward compatibility (backward compatibility).

2, (Java only) if there are multiple synchronized methods within a class, be careful about the deadlock problem. It is best to avoid sleeping in the synchronized method. If you can, use synchronized block instead.

In addition to this, some LinkedIn design on the process of deploying services are observed. Although most technology companies may be like this, but for my little white, it is an eye-opener. First, before the code churn is formally generated, a test is conducted, including a comparison with the previous version code, and a compatibility test for all the places where the code was used. If passed, the code base will generate a new version based on this change, and then save the package to a specific place. In the future, all the code needs to be used directly from this place to download the latest version. If the code is deployable, it is first deployed in a test cluster for a two weeks or longer, and then in the nomination to the production environment.

Some non-technical topics:

Grade

LinkedIn work environment is more formal in Silicon Valley. In the style of doing things there will be more obvious difference between managers and yards, there will be high-level scholar-bureaucrat and ordinary programmers. But from the office environment, people are sitting in cubicles, few offices. For example, my big Boss, a senior director, is also sitting in a cubicle not far from me, a table as big as me, two monitors ...

Interview

LinkedIn style is full interview, each employee will have to interview at least one person per week, up to three people. I have interviewed seven people this month. Although a bit of influence work, but also more interesting, look at the average level of interviewers, talk about their work experience, will also think about the question whether they will do or the like.

Food

LinkedIn breakfast and lunch was really good. There is a special person in the morning for you to fry eggs, or do omlet, there will be grapes, oranges, blueberries and other fruits, as well as yogurt, white boiled eggs, smoked salmon and so on. My favorite thing is to have breakfast. Lunch is also good, there are often beef and mutton, as well as pizza, ramen, fried chicken and other options. There is also a small window offering American Chinese food. Dinner is bad, and it will start 7 o'clock. But it's all free and it's perfect for single people. There will also be a variety of snacks, instant noodles, drinks and fruit in the small kitchen in the office building.

Three-month summary of LinkedIn work