I learned this in Microsoft's eight months.

 

--- Note: This article does not mean finding a balance in your mind (but it actually balances some human nature). More importantly, it basically writes my feelings in the company, but I did not summarize it. Awakening is more about motivation. you can change yourself if you cannot change others. In this article, always remind yourself.

The original article is as follows:

 

Today, two years ago, I graduated from college and started my intern job in the Microsoft Windows azure department. I spent eight months in that team.

I decided to summarize what I learned during my work over the past eight months. This may sound like a bad job, but it's not actually that. I have learned that, to some extent, a person should look at the problem from the company's perspective. Most of the problems are not the company's problems at all. Every company has its own problems. I am not here to blame others. These are purely important courses I Didn't Realize in College (the contrast between expectations and reality ).

Read the following:

Expect no files in the enterprise.Most of the knowledge transfer I see in my company is through conversation and practice meetings. Some parts of the knowledge base are generated only by email and will not be permanently saved. This will prevent the flow of information from entering the digital world. No one else can continue his work after leaving, but this is acceptable at Microsoft. (It Doesn't Matter.) If this is my own company, I will definitely ask him to write a bunch of wikis during the development process to ensure there is an ICP filing.

What you do is not important. What matters is what you sell.It takes several days for you to create a better code library, write more health code, and fix other errors. But as long as there is no big business impact, you cannot sell it, which means it is worthless. No one will appreciate you because you have a fixed software development model or research on the architecture at their core. In fact, they are not convinced of you at all. I didn't realize this when I was a student.

Not everyone is enthusiastic about engineering.Do not always create wonderful software with enthusiasm of others. It is not imperative to write better code. People usually have many other things to do (such as family and children ). In short, I already know. Don't expect everyone to be enthusiastic.

It takes 2-3 hours to program every day.Before taking over this job, I could spend 8-10 hours coding my personal projects every day, but in Microsoft's work environment, I could barely find two hours coding. I spent most of my time trying to figure out how other people do the code work for non-comments/non-files, how to adjust things other than work, and attend daily meetings. Obviously, it is not just that I am confused that a team may not submit signal tasks to source code control for several days.

It is normal that you do not give back to the technical community.I have hardly seen any blog or open-source developer in my organization who is willing to give their time back to the Organization. Everyone loves to find the stack overflow answer in the search results, but no one is willing to contribute those answers. I can understand them now.

We know little about the outside world.I bet that the latest technologies and tools you read every day are on blogs, Reddit, or Hacker News. This is not so common here. I am surprised that none of the people I met in the Windows azure team have heard of their direct competitors Heroku and rackspace. This is understandable, and not everyone needs to know this.

It is most important to complete tasks in the company.If your manager needs a button that is being done, no one cares about your mess. You only need to have the complete functions. At school, I thought that the quality of code is as important as the result, and the result proves that I was wrong.

Copy and paste the code.If someone sees that you are copying and pasting code outside the company, you will inevitably have to eat your fist. I have seen the source file copy and paste throughout the project, as long as it can finally complete the task (as mentioned above), no one cares whether you have created an unmaintainable code.

Code review can be skipped.Code review can be skipped for agility. This is part of my team culture. If you mess up others' code, the code review will be sent out. Normally, it won't stop. You can wait for a while until the sound of it gets the attention of others, and someone may reply.

The latest software.Not everyone here enjoys the latest software version. Almost 90% of colleagues use earlier versions of office, windows, Visual Studio, And. NET Framework. A general idea is that the latest version breaks the existing workflow. This may be the same reason why some enterprises run software on Java 1.3-1.5. So I understand that in such a work environment, don't count on the latest software.

Your expertise is usually useless.Every year, thousands of college graduates are hired by enterprises and often assigned to a team randomly (which cannot be changed within 1.5 years ). Whether you have mastered MongoDB, created iOS development, Apache committer, or created your own web library, and designed the user interface. You are hired to do what you need to do. I don't want to do that, because it is difficult for enterprises to find jobs that match your interests.

Finally,I didn't realize this fact when I was in college: You work for your boss and for money.

From: http://www.csdn.net/article/2013-06-13/2815752-8-months-in-Microsoft

Ahmetalpbalkan.com/blog