"nanny" Software Development

The so-called "nanny-style" software development is - I just eat, no matter how to wash dishes, like - clothes to reach out, rice to open the mouth. This situation is often seen in the relationship between development and testing, development and operation and maintenance. Many companies, testing and operation and maintenance have become the nanny of development.

I can see that many developments are quickly submitted to QA after testing the code. QA is a test, I am grass, various problems, and only the black box QA can not be immediately Can determine whether it is a code problem or an environmental problem, so it takes a lot of time to eliminate the problem that is not an environmental problem before giving the development report BUG. A lot of problems, you may just need to do a Code Review, you can find a single test, and you have to hand it to QA. The operation and maintenance is the same. The developed software does not consider what is the operation and maintenance of the software. Because there are operators, I will not consider it.

This is the same as the principle of taking children. For children, the more parents do to help their children, the more they feel that they should be, and the less they will do .

"Nanny-style" development generally evolves into "security-oriented" development .

  • Because your team's developer's ability is not good, the design is not good, Code Reivew / UT does not do, you can only find a pile of QA to look at him.
  • Because Dev/QA only manages functions regardless of operation and maintenance, it is necessary to find a group of maintenance personnel to look at them.
  • Because your technicians don't understand the business and don't understand the needs, you need to find another BA and find a product manager to direct him.
  • Because your technicians don't manage the project, then get a project manager, find an agile coach, and SQA to manage him.
  • In this way, you can't, I am looking for someone to look at you, people who look at you can't, I will find someone to look at your people... Layers of babysitters, layers of security. Then, you will find that there are more and more people in the team or department. You are in a meeting all day, explaining each other all day, quarreling with each other, and more and more people will be nonsense. There is still the efficiency of a fart.

1) Don't recruit "code farmers" who only write code.

2) The best management is not to find someone to manage people, but to manage yourself .

3) The fewer people who support the work in the organization and the team, the better .

4) Service. My service to you does not mean that I want to help you work, but on behalf of - I want you to work better .

I said the following on Weibo (you can understand the difference between babysitter and service)

Operation and maintenance should be done with the idea of ​​“cloud service”. If an operation and maintenance team within a company develops a bunch of tools, it is easy for an application development team to apply for resources such as machines, storage, networking, middleware, security, etc., and it is easy to manage, monitor, and deploy applications. U.S. Instead of helping the application development team work to wipe the butt as a babysitter. Then, the company will inadvertently make a cloud computing platform.