It’s May again, and a large number of computer students are about to flood into the workplace again. The cowhide has already found a job early, but no matter how skilled you are, in the programmer’s workplace, technology alone is not enough. You must understand some minefields and rising skills in the workplace.
I have been a programmer for more than 20 years, and I have stepped on a lot of minefields. Today, I will share my experience with you. I hope you can be more successful in the workplace!
Article directory
1. Programmer's workplace experience in life
1. Moments
Don't stay at home alone all the time and rush home after work. This is actually called "closing the country".
It is very important to get in touch with the company or people outside, especially not programmers. Even if you go out to start a business in the future, if you recruit a group of programmers and recruit talents from different fields to work together, the probability of success is different.
Whether it's operations, sales, anchors or HR, say hello and make friends, and they may give you some non-technical help in the future.
.
2. Actively communicate with superiors
Regardless of the superior's style, whether it is strict, kind or sheep-herding, we must regularly or irregularly communicate with our superiors about our thoughts and wishes on work tasks. Listen carefully to what your superior has to say about you, and try to get his guidance. Your most important resource in the workplace is actually your direct superior.
Remember one sentence: In the workplace, you should not only "lower your head to pull the cart", but also "look up at the road".
.
3. The object of the confidant must think well
It is inevitable to encounter turmoil in the workplace. It is okay to confide appropriately, but think about who you confide to. Don’t naively regard the personnel department as your confidant. Think from the perspective of your boss, what will he think of you? Tell the content.
4. Do business well and do less chores
If an employee does chores very well, there is a high probability that the boss will entrust him to do chores of the same kind every time he encounters them. If an employee does not paste invoices well, but the core business is done well every time, there is a high probability that the leader will leave more core tasks to him.
You will understand if you taste it carefully.
5. Treat promotions correctly
Some people are eager to be promoted every quarter. In fact, promotion to a new position is not necessarily a good thing. A higher position means higher requirements. Therefore, candidates must either have more than enough ability in the original position, or have more time and energy. Can you understand?
2. Code and projects of programmers' workplace experience
1. Learning should be practical
Novices always have a good drive and a sense of urgency. It is not wrong to want to learn more things to improve themselves. Not quite right.
My suggestion is to focus on learning the knowledge you use at the junior and intermediate levels. Human energy is limited. For the junior and intermediate levels, the underlying knowledge does not refer to the basic knowledge of the industry, because learning this underlying knowledge at this time is not enough for you to be competent for the job and not There is not much help. For example, if you work on the front end, your study of compilation principles will not help your work much.
But when you reach the intermediate and advanced level, these low-level knowledge will play a major role in your further performance, stability optimization, and industry technology direction judgment. At this time, you need to make special breakthroughs. Of course, you feel that you do have more time and energy, so feel free.
.
2. Open source
Young people today may not have experienced the tragic situation that programmers will lose their jobs at any time. But even in the darkest of times, anyone who works on an open source project can always find work again the first time. Just make sure that the open source code you write is relevant to your dream job. Believe it or not, the market is huge and the prospects are bright.
.
3. log
The log is not very eye-catching when there is no problem, but it is very important when debugging and troubleshooting once a problem occurs.
I was very impressed by this loss. It was a few days before the project was submitted. At that time, I was leading the project for the first time, because I basically did not add any logs in the program. At that time, no problems were found during the test. Then there was a problem. Since no log was added to the function at that time, it was very difficult to find the location of the problem. As a result, the project was overdue. Fortunately, Party A was easy to talk to, and it took a few days to resolve it.
Since then, I have always maintained a habit, that is, I must write a good log when developing.
.
4. Good at using tools
Everything is very tiring, why use your feet to walk when you can take a car? A simple tool can solve very complex problems, and it is time-consuming and labor-intensive to code them line by line. Do you think that good programmers have faster brains than others? Not necessarily, but he must be more efficient in doing things.
3. Long-term habits of programmers’ workplace experience
1. blog
I found that many excellent employees in the workplace are writing blogs while working, such as Ao Bing on CSDN, RabbitMQ and others. Because they insist on blogging, their careers and lives have received good bonus points.
And in some big first-tier factories, the technical department will require employees to write a technical blog every week or every month, and then share it with colleagues. By blogging, you will deepen your understanding of technology, and at the same time, you will gain a lot from the interaction with many big shots or fans, and even have extra income.
.
2. Reasonable career planning
After entering the workplace, you must do career planning. Programmers should not be machines that can only type codes.
There are too many things you don’t understand in the first year. You can follow the boss’s arrangement, knock on the code, look at the database, and test your own and other people’s code; but in the second year, are you still like this? Impossible, you can enter the industry with one year of experience, it’s time to learn how to conduct requirements analysis, how to design databases, how to write various documents, and how to write better codes? This is a requirement for advanced programmers.
Secondly, I want to say that your career plan must be reasonable. I personally don’t recommend setting a five-year or ten-year career plan. It’s unrealistic. Why?
1. Five years and ten years are too far away. Except for the nine-year compulsory education, it is hard for me to imagine anything that most people can persist for so long. If they can’t persist, they will only talk to you more frustration.
2. Can your current level predict five or ten years from now when technology iterations are changing with each passing day? I am afraid that very few people can do it, so what is the significance of this plan.
I personally suggest that career planning is best within three years. This is the most reasonable. You can definitely know what is helpful to you now and in the future.
Four. Conclusion
Since you have chosen the path of programmers, you are destined to keep a learning attitude to engage in technology. If you can combine technology with the sophistication of the workplace, then you will definitely be able to thrive! come on!
Thank you for your reading and liking. I have collected a lot of technical dry goods, which can be shared with friends who like my articles. If you are willing to take the time to settle down and learn, they will definitely help you. The dry goods include:
Click on the business card at the end of the article to take it away
