Programmer, have you done it? -- Reading the cultivation of high-performance programmers

Author: larryzzl

When I was in college, my computer science was too hot. At that time, a large proportion of students who graduated from that major (including other related majors, such as physics and electronics) became "programmers ". Many companies give it a better name-software engineer. What a lucky job title is there. In particular, the "engineer" in it adds a big and bright HALO to this job.

Of course, this is what others see. We (as we can see, I am also one of them), but we call it "codenong ". Why? It's nice for engineers. Why not call it. No way. You are not qualified. Software engineers, you think it's so good!

My boss gave me a book titled cultivation of high-performance programmers a few days ago. Its subtitle illustrates everything: software development is far more simple than code writing ......

Want to be a programmer? Do you want to develop software? Well, writing just a few lines of code is far from enough. (It's really hard for us to say that. It is not easy to write code. You need to learn so many "messy" other things to deserve this position .)

I open a book. Oh, I have a lot to learn. From psychology to team management, from recruitment to user experience, from team collaboration to marketing, from system security to code testing, we even need to care about what kind of chair we are sitting in, the size of the monitor. I just want to be a programmer. Easy!

However, people always need to develop. Are you willing to write Hello World for the rest of your life? Only by enriching your experience and opening up your own horizons can you not only seek product perfection from the code point of view, but also from the user's point of view, so that you can be sublimated, turn your code into art. There is a saying on the Internet: we are not programmers, but art craftsmen who are pursuing them.

Only know if... Else... It is not enough. It is no longer feasible to develop close-doors software in the current era. Programmers need to know how to communicate with people, including other programmers, including their superiors and subordinates, and even customers. Listen to others' voices, get others' feedback, and win others' support and trust. This way, programmers can develop the products they need and love in this era.

This book contains 12 chapters. They have never elaborated on the qualities that a "high-performance" programmer should possess. In my opinion, it is communication, analysis, and code writing.

(As you can see, I listed "write code" at the end)

Communication

Most programmers are actually quite comfortable. Especially programmers in China. He is not good at expression. He asked him to write a line of comment to show that the function is more difficult than making him write 100 lines of code to implement this function. I want a programmer to give a PPT to introduce those functions. Oh, I'm dreaming!

As we have mentioned above, today we cannot complete a project by one person alone. We rely on a team. A team is composed of people. People need to communicate with each other. Those people are "programmers ". If we cannot accurately and quickly let others know what they are thinking and what they want, things will often be blocked. This reduces efficiency and increases costs.

Having good communication skills is the first step for programmers to achieve "high performance.

Analysis

The analysis mentioned here includes the demand analysis, market analysis, priority analysis, and self-analysis.

If you want to develop a software and want it to be accepted (or even liked) by the public, you need to know exactly what features it should have and what interactions it should use, who is the target customer group and when it will be released. These require excellent analysis capabilities to give answers. It is undeniable that these tasks will be completed by different people (such as product managers, marketing personnel, and project managers) in the current era of "specialization in the industry, programmers are only required to implement specific functions. But this does not mean that programmers can only keep their own three-acre land. The programmer needs to use his unique and keen sense of smell to help others complete their work and ensure the successful release of the product.

Programmers are very busy. One day, I need to write a lot of code and perform various analyses. From time to time, there are also irrelevant meetings to attend, and some irrelevant persons to serve. You need to know which one you want to do first, which one you want to do later, which one you want to do, and which one is not suitable for you. A brain will not refuse, but smiling face will only bring a lot of trouble to yourself.

With excellent analysis capabilities, programmers are the second step towards "high performance.

Write code

A programmer can't write code. Is that a programmer? However, "writing code" here is not as simple as "Hello World. You need to know how to write elegant and beautiful code and use a flexible and secure architecture. Let's take a look at the author's recommendation code Daquan (second edition. It tells you everything that is related to "writing code.

With the first two steps, if you write code again, congratulations, you are a "high-performance" programmer.

The book finally asked: programmer, are you happy? In fact, programmers are very hard-pressed. If you encounter any problems, you may go into the middle of the night. users who have worked so hard to write functions do not buy the funds, but the product release is hard to get credit from some people. But programmers are also very easy to feel happy. This is because happiness is too easy during software development. The unit test is successful and happy. Killed a bunch of bugs, happy. I wrote an algorithm that cannot be used by Nb, so I am so happy. If I can get my colleagues' approval, I will be happy in the sky.

Turn yourself into a "high-performance" programmer, so that happiness is doubled.