Practice of project managers (2)-books that must be read

There has always been a rumor in the software industry: It doesn't matter if the project manager doesn't understand the technology. Some people say this is an advanced foreign experience, but I suspect it was fabricated. The sub-lines of this point of view are as follows: the project manager is a manager, and only the subordinates can be directed. Why do you need to understand technology! This is as ridiculous as saying that the shift leader does not need to take a gun on the battlefield. Remember this: "General

There has always been a rumor in the software industry: It doesn't matter if the project manager doesn't understand the technology. Some people say this is an advanced foreign experience, but I suspect it was fabricated. The sub-lines of this point of view are as follows: the project manager is a manager, and only the subordinates can be directed. Why do you need to understand technology! This is as ridiculous as saying that the shift leader does not need to take a gun on the battlefield. Remember this: "General

There has always been a rumor in the software industry: It doesn't matter if the project manager doesn't understand the technology.

Some people say this is an advanced foreign experience, but I suspect it was fabricated.

The sub-lines of this point of view are as follows: the project manager is a manager, and only the subordinates can be directed. Why do you need to understand technology!

This is as ridiculous as saying that the shift leader does not need to take a gun on the battlefield.

Those who hold this point of view can still remember: "The General started from xingwu, and the Prime Minister was from the State-gun.

In my opinion, the project manager must understand the technology and have a solid foundation, although not necessarily an expert in specialized fields.

In this article, we will list a few books that are used to lay the foundation. These books should be carefully read without turning them over.

The use of these books is not at present, but ultimately determines your growth height.

Without these foundations, if the station is too high, it may be like a building in Shanghai. Maybe it will fall down that day.

1. Languages + platform books

The language and platform books vary based on different languages and platforms, and classic books are also different. I think it's best to choose the most famous one. Just read one copy.

For example:

I spent almost one year studying C ++ and read Bjarne Stroustrup's C ++ programming language repeatedly. I really benefited a lot. When I learned other languages later, there are basically no obstacles. After reading Jeffry Richter's "Windows core programming" several times during Windows programming, the context of various Windows problems can be quickly clarified.

Even now, all the problems in such projects can quickly grasp the crux of the problem.

There are many famous books like this, but it does not seem very profitable to read multiple books. Read this book thoroughly, and you can learn it from other practices.

If you are focusing on system programming, the above two books are still suitable for you. If you are using another platform, select a famous one!

2. If you have a technical foundation, read a book to cultivate a global technical perspective.

At this time, I feel that the best option is code Daquan. This book covers almost all aspects of coding design.

After reading it, it may be difficult to remember the details of a specific link, but you can at least know the issues that need to be considered in software development.

3. When the technical perspective is wide enough, read a book (including demand development, management, estimation, and process) that looks down on the whole of the software ).

In fact, we need a classic soft engineer book, but unfortunately there are a lot of good books in this field, but the classics are almost useless to a certain extent.

The Mythical man-month is too old, and the man-piece is almost not suitable for national conditions, while the software recording is too fragmented.

(If you have a Chinese software company assign an office to every programmer, the boss will be crazy .)

If you have to recommend it, the level 2 and 3 process domains of CMMs are not bad, so you can read the SEI standards.

4. Study estimation and read a book related to estimation.

If estimation is accurate, problems in software development may be reduced by half.

It is natural that a problem may cause the team to work overtime, internal tension and enthusiasm to fade away.

Therefore, you must have your own estimation methods. At this time, you can read "software estimation-Black Box decryption".

5. Change your horizons and patterns, and read a book without any relation to programming.

For example, Tang inbi's historical research.

In the previous article "Practice for project managers (1)-modeling for software development", we mentioned that you should have an overall model for software development.

This model can be ugly and simple, but it must be yours.

This is like a pearl. It can be a small stone or a bird's shit in the middle, but it must have,

If there is, the subsequent secretion can ensure the production of pearls; if there is no, then the Pearl will not know where to start.

I don't have my own understanding of Software Development. I have read too much and cannot absorb the knowledge. I will read my mind out of the box.