The first visit to the law of construction, as this book gives us the concept of doing high school (learning by Doing). In practice, the book has repeatedly emphasized the simulation of actual combat, with objective data to score in the university biased teaching model, I think this teaching concept to bring me a great impact, although the reality of practice and the ideal situation in the book is very different, but also brought me a lot of benefits.
For this book, let me ask a few questions:
Introduction to the first chapter: teacher you tell us what is software engineering, and then put forward a lot of professional terminology, and then explain the concrete meaning of the pile of nouns. But as your teacher says, what we are concerned about is what do we get from these nouns to us?
Chapter II Personal skills and processes: This chapter gives the teachers think that we as a successful software engineer must have a few skills, and some correct ideas, how to think, do not stay in their own deviation of the mind. I have no problem with this chapter.
Chapter III The growth of software engineers: As the teacher gave examples: football has different shapes: 442, 433, 451 and other styles. A team of football has various roles, in the software engineering personal development we have to do a good role to do a good job of control, each project is mainly responsible for a module, or learn flexible, all aspects must understand, in the project to focus on a module?
The fourth chapter two people cooperation: the way of feedback is related to the innate character or the growing environment? Can you choose to discard the pairing after pairing?
Fifth. Team and process: What is the premise of the software team model? What makes the team's model into this model? Can you change it then?
In fact, a lot of concepts, practice to understand what should be given to solve the method. Thank you teacher!
Read the 1-5 chapter of the Law of construction