That’s how most people work
At the end of the year, I believe that everyone is busy, but we have a holiday or tidy it up before the next work plan and learning goals, after all, are programmers, more or less is hard to keep technology capability, and also recently in the company to arrange all the progress of the project and technical problems of docking, so get a general idea of the company’s core business and project problem, Most of our company is still in good condition. 80% of the project-based projects have been completed, but the operational ones are not mentioned here. However, some delays are due to software development problems, such as the sudden problems of our own RESEARCH and development, and the mistakes made by external research and development without understanding the business, etc.
In the morning, WHEN I went to the r&d department to ask the project manager about the progress of several delayed projects, I noticed that several colleagues in the same department were wearing earphones and were focusing on the code. In fact, I also like wearing earphones when I was typing the code.
I used to work in the R&D department. I used to listen to music and write bugs, hahaha. I felt like I needed a programming space and I was used to working with headphones, which made me feel relaxed and I could focus on the functions I wanted.
Really think all programmers should be wearing headphones before work, but this two days feel don’t have such a habit, it may be my own feeling, I communicate with colleagues, of course, they also have the same feeling, especially your job function change, or don’t wearing headphones as well.
Not yet in communication
Most programmers are nerds (or women), and they are not good at communicating or expressing themselves. They only need to complete requirements daily and weekly. The problems they have to face may be: changing requirements, fixing bugs, writing bugs, career pressure (learning ability), etc.
They need to communicate, but all of them are targeted. For example, they know the core of the business, the demand and the process of the business from the people who need the product. In their mind, they are thinking about how to achieve it and how to change it, as well as their infinite hatred of the proposer.
Listening to music, with headphones, can take their mind off the office environment, away from project pressure, etc.
Instead, I’d advise against it. Why is that?
1. Try to improve your role
No programmer wants to write a lifetime of business code. You need to make some fake upgrades. If you are your current direct manager (up one level), observe how he works and what you would do if it were you, after all, you might have to do the same thing in the future. Knowing the difference, how would he communicate?
2. Do you love the company and the team?
Many young people are easy to quit and change jobs. Do you really know your current company? Can you introduce your company’s business, history, environment and future development path? Do you know everyone on the team? The workplace is also a small social circle, you can not turn up alone. If you were lucky enough to represent r&d and go out and introduce your department to a client?
3. Do you know everyone’s job functions?
The guy next door, the guy next door, what does he do? Good for what? What should be done? Try to get to know each and every one of your coworkers. You might even be asked, “Who do you think was the best performer this year? Why is that?”
4, final coding, you are not for high function and authority?
Can an employee who doesn’t know the company, doesn’t fit into the team, and doesn’t work with autism, really get a big job?
The headset here is actually a metaphor, I hope you can work, sincerely to understand their own business, their own backbone!
And, if you were the boss, would you like them?
Know the secular and not the secular
New Year, my boss and I said a word, “know secular but not secular”.
He said, “You and I are the ones who don’t want to do it. We have to do it because we know we are doing it to achieve some project or event.” We are still not secular.
Yes, our company or department department leaders are going to send some human feelings, at least I don’t yet have a headache because of this, most programmers should don’t have to have a headache, you may be considering years ago how to give the BUG to handle, but we might be thinking about how to make the party a agrees to acceptance of the project, how in the New Year renewal projects, etc.
Sooner or later, we all have to think about these things, for whatever reason, whether we’re in the same job or not, but at a certain point, I think we all need to be secular for something.
Try not to wear headphones and be prepared in advance.
Preparing for the transition to the workplace
From programmer to architecture or technical management, I think you also need to deal with interpersonal relationship and project business more. You will find it difficult to start at the beginning, but you still need to gradually adapt to it. I hope you can prepare in advance to improve your comprehensive ability.
My boss was not a skilled person, but he had experience, but he was not skilled. At that time, he did not need to manage us very much. What he required for himself was that the department would continue to operate day after day when he was gone.
I have been learning some non-technical things from him and deepened my understanding of technical management.
I’ll leave it at that. I haven’t written it in a very systematic way, but hopefully you get the metaphor.
2019, don’t wear headphones to work
Improve your overall ability, whether you can give a presentation of your project, whether you can write a technical report for the project, whether you can do technical pre-sales and after-sales consulting, whether you can quickly learn the new framework or language, whether you can reach consensus with your boss.