Thoughts on the construction method: Modern Software engineering

When I read the law of Construction: Modern software engineering, my greatest feeling is that she is not like a high teacher, waiting for the students to open their mouths and fill the brain with knowledge. And more like a person who has been hoping to make fewer detours, but also to chew on their own. So although it is the same book, everyone will have their own hamlet, everyone has their own harvest.

the opposite of skill

I have to say, before I read about it, I always thought that college was a technical school, and that it took years to teach you a technology. The first three years of the university also confirmed my vision. There is no reason to think, only the exam will not, we call this a skill. But when I found out that although I couldn't get the first few, I could just take a few days to finish a course. I was secretly pleased that I had mastered a terrific skill. But superficial understanding sooner or later to accept the reality of the blow, do not say far in this course I am struggling to think that I have learned C + + to cope with this course should be more than enough. The results can be imagined, every step has to "re" learned, not to ask classmates is to check the computer. Discovering what you call a skill is nothing more than a self-deception with exams. After all, just mastered the fur, even the first layer of the Rubik's Cube is not. In my opinion it may be that I think of the so-called skills as a panacea, but I do not know the so-called skills are only to deal with the opportunistic test. Even some of the courses are not in the door, only know how to back some formulas, how to set up to do, that's all. In the final analysis, teaching with the goal of testing (so-called knowledge) is contrary to the ability to really deal with problems, and we know only that it is far from knowing why. Of course, their attitude to face these problems is also the problem, superficial understanding is always the greatest enemy of knowledge.

you're going to make hamburgers.

For me, the most impressive is "to make hamburgers", because in my opinion, knowledge and skills can be learned to strengthen, but how to get along with people how to play 1+1>2 indeed we do not often understand but very important. Even the simplest 1:1 sometimes deals with a mess, not to mention teamwork. I have a deep understanding of this, I suddenly found that my feedback to others is actually the middle and the most inner layer, so that the other side has no retreat. There is no room left for the other to save the situation, and inevitably make the relationship stiff. This is certainly not to say that we should compromise or flatter, but that we need to know whether our feedback needs to be achieved. No one wants to be criticized by you slashing, so it's not as good as giving others a hamburger, but having bread (encouragement and expectation) while you need someone to accept meat (comments and criticisms) to make the hamburger swallow.

Thoughts on the construction method: Modern Software engineering