1. for a project of less than 100 people, there is no need to use software engineering methods, it will only waste too much time, the method of using software technology may be faster and more efficient to complete the task.
2. Before a project starts, consider whether the software project is applicable.
3. Creating a "good enough" software is an excuse to find a low-quality software for yourself. There are inevitable bugs in a software, but this does not allow us to relax our requirements for testing. The purpose of testing is to find as many errors as possible and correct them.
4. The software process advocates the previous workshop-style development model, that is, one person is responsible for one piece. All the investigation, analysis, design, and final coding are done by one person. But the premise is that this person must be a very good person.
5. The biggest problem caused by the division of labor in software development is the waste of time, because communication has become one of the most important obstacles. In addition, communication may cause many misunderstandings and errors.
6. There are too many software developers, not too few, because there are too few excellent people.
7. simply increasing the number of people is impossible to complete the task, because excellent people need to spend more time to lead new people, and they can complete the task by themselves, and the quality will be high. Therefore, the development capability of five excellent people is much higher than that of 20 new users.
8. A person in the project should be an apprentice to a technician and then a master, but the time is not certain. As long as you have certain skills, you can upgrade.
9. For daily outsourcing work, the final consequence is that all people are bottom-layer apprentices without a technician. How can such an enterprise succeed?
10. As an enterprise, money should be spent in the most useful places, rather than as a training course.
11. What apprentices should do is to look at how technicians work and learn from them, rather than asking technicians to teach them by hand.
12. Do not allow a person to learn new knowledge at the apprenticeship stage because of work pressure, because the new knowledge learned by the apprenticeship may be something that technicians do not have time to learn.
13. If one person can bring another person together in Agile programming, they can give full play to their respective strengths. A person has enough experience and necessary skills, while another person is curious and skeptical, rather than forming a definite mind, that will surely produce better results.
14. The use of software to automatically generate code instead of the programmer's work is just a dream that will never be realized.
15. in the process of software development, the most important factor is that people, if everyone can do their best to develop, and have good experience and skills, it is a successful project.
16. A person may have to go through this process in the design process: No-> A method-> multiple methods-> NO.
17. The reason for the success of the limit lies in the fact that the building can spend most of its time in actual work and related tests, rather than on paper. Writing too many documents will only cause excessive waste in the communication process.
18. The human resources manager should be an extremely important role in the company. His task is to hire a small number of excellent talents for the company, rather than a large number of mediocre talents.
19. It is necessary to sign your own name in the written software, but the premise is that all work is done by one person, not just coding. This is fair.
20. in the course of teaching, if you can lead students to deeply analyze and understand the code of a project based on their own experience, the effect may be much better than simply introducing the content in books.
