As a result of the teacher's recommendation, I just read the "migration path: vsts Software Development Guide", I feel that the author explained to us the possible situation of software development in the form of small stories and vernacular,
I feel that software development has suddenly become easy to understand due to a deep problem. However, I still feel some problems during reading.
1. most of the work between teams mentioned by the author is proposed by PM, and the people who actually participate in the task are generally limited to a few people, in this way, although the salary and income are determined based on the workload,
However, for a few people, there are too many things, and there are too many negative effects. How can we change this situation and improve the efficiency of the entire team, so as to reduce the workload of team members by cutting corners or by hard work? Although it is common for the experts to work harder,
However, this does not seem to be a good phenomenon.
2. as a computer school student, I really want to improve my coding skills. After reading some suggestions from the author, I feel that a lot of code is not as complicated as writing, it may be better to use several of them as appropriate.
So how should we master this scale?
3. How should we become a qualified pm? Is it enough to fulfill all the requirements in the book? Where can I find such an environment?
4. Test and Development written in the book are very important. As a newcomer, is it appropriate to choose the development department first or the department responsible for testing?
5. The book contains the content that many teachers have already said, not only in software engineering, but also in many other disciplines. Have these ideas become outdated?
Reading Notes on the path to mountains