Who moved the dignity of the programmer?-also talk about the management of the software development team.

Question: Who has moved the dignity of programmers? The essence is to encourage some frustrated programmers, to affirm their love for technology, and to remember a small part of their previous crazy pursuit of technology. It has nothing to do with managing a dime. In the reply, a small number of people talk about management means and management art. What string brother wants to say is that there is no management in essence. Core or middle-level personnel often have clear goals, to a large extent, it is self-management. The bottom-layer personnel only need to throw a few management tools, which does not play a decisive role. For example, the first time you open a room with MM, the person who installs 13 will tell you that it is art and requires a lot of skills and tricks. String brother will only laugh and speak, and tell you before leaving: "Follow your heart... ". The result is obvious. If you listen to the former, it will inevitably lead to too many distractions in your mind. If you are confused, nothing will happen after an hour, and you will finally get out of bed with a slap in the face of MM... management is like a lone sword. Once you have a "trick", you will be recognized and lost in the first place...

Who has moved the dignity of programmers? As a programmer and technician, we talked about how to actively face some setbacks. This article is about some issues that should be considered as technical team managers. First of all, I do not like the word "management" because no one will like "management ", at first, I thought it was caused by my unrestrained character and the fearless grassroots feelings of the ignorant... after receiving some formal training about the so-called management, this feeling became more intense.

For the so-called project management, I may have these learning backgrounds, corporate training: MBA panoramic tutorials, European Business School Series, Senior Project Manager exams, PMP exams, there are also trainings such as the art of leadership and the MOT popular in the world's top 500 (or brainwashing...) of the times ...) although I am not very interested in these things, I feel that they are all techniques in Western learning. I personally admire the Tao in Chinese learning, but they are not very excluded. I have basically gone through it. I have read it myself: the Mythical man-month, software engineering, agile development, code Daquan, software development as you want, and others are not in the stream, javaEye's software development and project management edition also have nothing to do with it; humanistic aspects: all kinds of Chinese normal history and wild history are incomplete, the main High School was influenced by Han and the 15th year of the Chinese calendar.) The various types of Confucianism, Buddhism, and Taoism are rough, and the western philosophy is concise... so we can see that I should not just be an excited enthusiast who will write code and colors .... -_-B: Let's get back to the point and talk about "management ":

1. First, there is no strict "management" for the software development team ". From agile development, you can see that Agility only allows one of your teams and no more than two new users. The requirements for other team members are basically from technical to professional quality. Many people are studying agility, What Is pairing, flat structure, standing meetings... those are all techniques, and they are all tricks .... For example, if your team of 10 members does not have eight programmers like God, they are all white blind ....But do programmers like God still need to manage them?I admit that agile has a lot of excellent ideas and practices, but if you put it in your own team, I think more results are tragedies, and comedy is because you are really lucky, your team members are strong enough to have nothing to do with your management level and agility...

2. The reality is that,A team of 10 members has only 2-3 backbone programmers. They solved 80% of the problems of the entire project, and the remaining 7-8 programmers were irrelevant. They mechanically wrote some modules with complete technical solutions, the worst case is that these 7-8 people cannot solve any problem and will create some problems under the original mature solution.. Many people may not listen to this section, but they cannot. Otherwise, this is a fact and they also ask themselves about their value in the team. In fact, you can see that many of Niu X's major products are actually written by several technical staff of Niu X, and the rest of the team is basically mixed, both at home and abroad.

3. speaking of this, as a team Leader, you should be aware that the first thing you need to do is for backbone programmers: the most important thing is that 2-3 backbone programmers will not think that you are a technical idiot. The better thing is that they think that you have made achievements in technology, the best thing is to use your personal charm to infect them.

4. For other 7-8 programmers, proper technical training is necessary, but we should not have too much hope for them, so that everyone will be very tired. Since they want to become coders, they can be well-trained.

5. management tools and management skills:Do not make everyone feel that they are being managed. No one likes to be managed.. You can introduce an avant-garde management tool first, and then let's take a look at it. If the effect is not good, you will not think that your management level is junk, but you will think that this management tool is not fun. If the effect is good, you can enjoy it, finally, you will find that your team members do not feel like they are being managed at all, but in fact there are a lot of management tools and management methods in your team. Sometimes you will feel annoyed by yourself, but everyone is still happy .... when the Human Resources Department evaluates the management level of your department, it will be really shocking...

6. If a team Leader or the company's technical director should have a deep understanding of the technology, I think there is no need to discuss it. This is necessary! For the company, the technical direction you decide determines the company's products and strategies for the next few years. If you have a thorough understanding of the technology, it is unimaginable, enough to destroy the entire team or even the company. For example, let a technical team use MOSS as a platform for development. For example, if the boss is attacked by Microsoft, or if IBM is a so-called chief scientist, he wants to develop a cloud computing center... if you do not know the technology, it means that you cannot really grasp the progress of the project. The so-called project management tools are full of clouds ....A project manager who cannot even master the project progress? Or a project manager?

7. you want to say that I have a management tool package, but I only need one problem to crack the management myth that you don't need technology. If the project is half done, I will encounter a technical problem, what should you do if all the technical staff tell you they cannot solve the problem? How can we ensure the duration? Outsourcing? Foreign aid? It will only make your project more risky and more uncontrollable. We have learned it, right?The problem is that your lack of technology leads to a decline in your technical risk prediction capability, and your technical solution capability is basically zero. You are an idiot in front of everyone ....

8. we often see a lot of problems and complaints from project managers of some teams. I am talking about the solution and simplicity. You can implement the code ....... you will implement rather than implement it, which is essentially different from your understanding of implementation.Just like the popular saying "Technology is not important, thinking is important", this sentence is for people who understand technology .... the Code has never been written into 0.1 million lines. In this case, it is ridiculous..

9. Keep your thoughts and opinions on the company and the team before you take the team to three or more projects that are truly successful.Even if you are in that position, there won't be too many people to listen to. The strength and respect are proved by facts..

10. If you really make money for your company and let everyone see your character and strength:Emphasize Technology for non-technical leaders and requirements for Team Technical Personnel.

　

Conclusion: The greatest truths are simple! Do not be too superstitious about the management tools and management skills of Western learning. Unless you learn about the history of Western philosophy and culture, you will onlyToddler, No essentials. Maybe you can look back at the things of our ancestor, but it will suddenly become clear?

For example, the object-oriented and process-oriented development methods in software development can be traced back to Aristotle at the earliest (it seems that in our textbooks, he is the academic authority to be defeated ..) classification and logic are two tools to understand the world... in fact, thisIt is also the foundation of Western science,When we learned programming that year, the cloud was in the fog... It was actually very simple after a few clicks, right? Everything is an object, and everything goes down first... to put it bluntly, it is classification and logic. Sometimes we advertise object-oriented and despise process-oriented. Is it silly?

For example, quantum physics is now at the end of idealism (of course, there are parallel cosmic statements...). Actually, observation will affect objective results! But in fact, Confucius once said to divination that you should not calculate it. In fact, the result has changed in the instant you calculate (it's just not enough ). It's really the same as the electronic two-phase wave...

Of course! These "ideas" are important, but please do not forget to write your 10 million lines of code first...

Some may ask, what kind of team did you talk about in the previous article? It is a pity that I am not allowed to do that in the corporate culture where all financial statements are needed in a large company. Many things in a large company are more complicated and need to be considered. In addition, the kind of team that requires me to invest a lot of idealistic spirit, energy and feelings does not seem very suitable for me to be a child dad. I would like to send it to the bright sword team of Niu B and the brothers in the team.