The method of construction read Note 06

Reading the law of construction is nearing the end, and this book gives me great inspiration.

It is important that our software is not for everyone. Although everyone wants to make their own software for everyone, but in the software, we can not consider too many types of users, but need to consider the main use of our software typical users, we should focus on solving the user's pain point. This type of user is our core user. We develop software for a typical user. Because many users express unclear, we are prone to communication problems, it is easy to deviate, to find the motives behind the user, mining out the user did not express the meaning of the implementation of the function is always unable to obtain the user's satisfaction, so that the product may have to rework several times.

In this book study, I learned what the code specification is, how to be considered the code, Code space requirements and other related issues. Learning to test by writing unit tests, the quality of the module can be stable, quantitative guarantee. I learned how to test the use case to ensure the quality of the program. I also have a clearer understanding of teamwork. After reading this book, I knew what the project manager was and what the role of the Post played. Although there are different roles of pigs, chickens and parrots in a team, you may have conflicts, but at the end of the spectrum, we strive to meet the requirements of our clients by focusing on the core point of team work. There is in the software industry, an ignorant imitation of others can not let you grow into a good software engineer, but also learn to innovate.

The method of construction read Note 06