Be considerate about software-how to manage software enterprises

Be considerate about software

---- How to manage software enterprises

Wu Yu

Taiyan Network Studio

Lin Rui presented his new "how to manage software enterprises" to csdn's CTO club. I received a gift yesterday afternoon and went home to go to school at night.

Once the book was opened, I thought I had never seen such a management book that is easy to understand.

Looking at his high quality C/C ++ programming guide, it's not that popular. After thinking about the technology, it cannot be easy for a technician to write the technology. However, writing and management by a technician must be the essence of his own experience, he explained all the points he could understand and should all go through his hands-on practice.

He removed a lot of statistics and arguments, and even filtered out details of many management systems, such as the specific explanations of CMM/cmme and RUP, which he did not mention. It should be said that this is in line with China's national conditions. On the one hand, we manage a large amount of data just by copying the data, which cannot be absorbed by the introduction. On the other hand, most software enterprises in China are limited in size, they are still in the initial stage. We cannot copy the experience of managing 1000 people to a company that manages dozens of people and design so many architectures and departments. Therefore, his theory is almost two words: practical. He also raised his own feelings about the proportions of the legal system and governance of people.

I have seen many books that talk about specific reasoning details, but do not describe the corresponding usage and usage conditions. It gives people the feeling that everything is accurate across the world. In fact, it may be a trap. I personally think that management is more about the promotion of style and behavior patterns, rather than putting people's abilities together.

When I read half of my books, I felt that I had to be honest about software.

What he said as a software company doesn't mean to go away with earning money like doing stock market futures, but to open an old store more often. Therefore, his starting point is to make the enterprise and individual have a sustainable development ability, not a hammer sales, not a trap!

The software industry requires a lot of technical accumulation, especially the choice of business models and profit models. Companies that rely on fraud (such as fraudulent traffic using the mobile phone service) can either have a backend or earn a hand. However, as long as the time is long, nothing will happen.

Programmers must be generous and managers must be generous. Make the money you should earn. Do not think about the jobs that will disrupt your mind. Most technicians do not have such good psychological qualities.

Another honest saying is "win-win". For example, he said that you have to pay up to four times as much for work: one is your own, one is the enterprise cost, and the other is the enterprise income, one copy is the benefit of investors.

Another honest saying is that it must be effective without a false name. I have seen a lot of management and development practices for real failure, because enterprises think they are the most advanced stuff from top to bottom, failure cannot happen to you!

What is the level of responsibility for a job? Do you do what you can, or do it as your own? He said, treat it as your own child!

After reading the book, I think there must be ideas for software.

There must be political ideas for the revolution, or it will be no different from those of the mountain thief. The idea also needs to be built for software, that is, what kind of goal should be achieved (rather than what specific goal ), what method do you want to use.

Most people who have invested in the stock market can feel that there is no investment philosophy, or investors who do not execute it at all, most of them are chasing up and down, and all the operations are emotional, and orders are subject to impulse. As for the results, "Everything is God, everything is fate, and ultimately it is doomed "!

The concept should be a behavior, a value, a spiritual scale, rather than a stage goal. It is wrong to regard "becoming a CEO within five years" as an idea, but it is right to regard "having the same capabilities as a CEO within five years" as an idea.

To put it bluntly,Concept is actually a realm that determines the height of your life.

The same is true for software!