[Reading Report] Construction of the law (i)

Today I read the Xin Zou Teacher's "Construction Law" from the preface to the 66th page of the text, some thoughts and experience are as follows:

1. Preface

From the preface, it can be seen that Xin Zou Teacher's orientation to the software engineering course and the evaluation of this book as a textbook are still very high. From the preface can know this book is Xin Zou teacher combines the software engineering teaching experience and own experience in some colleges and universities, writes out a teaching material which emphasizes through the hands-on practical study software project.

2. Advice to teachers and teaching assistants

This part can read Xin Zou The teacher is very demanding to the students, expecting each student to spend 8 hours per week in this course. Personally, I spend more than 8 hours a week on personal projects and team projects. In a team project, it is more than eight hours to count the time it takes for a meeting to discuss a transaction. In the team project, the time to write code is not very stable, some weeks more than 8 hours, and some weeks are not enough.

In the face of the software College teacher's complaints, Xin Zou Teacher asked the problem of the solution is to first let the students maintain the existing procedures and gradually incremental development of the way. I think that's a good idea. At that time the golden point game our group got the second place, the priority of the selection project is still very high. At that time, with the naïve recognition of the existing project, including all of our forward-leaning groups have opted for the development of the existing project iteration. But it turns out that we really are too young to naive, because the process of getting the hand is not a complete program at all, what about iterative development? This has largely dispelled my enthusiasm, I have a strong resistance to the mentality.

Xin Zou Teacher's discussion on the relationship between teachers and students Roger teacher also talked about it in class. The coaching/learner model is really appealing, but in the actual development process, I think it is the students who are fighting on their own, and the help they get from the teachers is extremely limited.

I think the former is too cruel and the latter is too idealistic for the 1/n scoring method and the team contribution mechanism given by Xin Zou teacher. Perhaps the society is actually very realistic and as a student I am also too naive.

3. Chapter I.

The first chapter mainly introduces some conceptual things. It may be more important to have several formulas.

One is the formula we knew very early on:

program = algorithm + data structure

The other two I think are books that remind us to pay extra attention to:

Software = Program Plus software engineering

Software enterprise = Software + business model

For these three formulas, I have my own ideas:

Procedures on the relationship between the least involved, software and software enterprises on the relationship between people and people to explore more and more.

It seems that people are still the most fundamental. For example, Xin Zou in the book, many software features similar, but the user experience will open up a huge gap.

It seems that the game is the game of man and person in the final analysis.

4. Chapter II

The second chapter is about personal technology and process, and the content of comparative practicality includes unit test and effectiveness analysis.

It is interesting to compare the time-consuming comparisons between seniors and three-year-old software engineers in Xin Zou.

The most obvious contrast is that SDE has a 60% more time spent on demand analysis and testing and 1/3 less on coding. This reality of professionalism has a prominent feature is the normalization.

5. Chapter III

This chapter is about the growth of software engineers, I think every student will be very concerned about this topic, I certainly no exception. This chapter still proves that the outstanding characteristic of professionalization is normalization. To be a good software engineer, a lot of things can not be described in terms of approximate, similar words, but should be recorded in real data to speak. And the real project is the only way to improve the ability.

I was very impressed by the example of the Rubik's Cube, which Xin Zou teacher mentioned. How to improve the skills, Xin Zou teacher to give the answer sharply: through constant practice, the low-level problems are solved, into the automatic operation without the brain, and then have the time and brain to solve the higher levels of the problem. In fact, this model of the formal middle school era model: All the knowledge points have reached the level of memorized, and then in the process of dealing with a variety of problems in the free and unrestrained display.

But this is probably the biggest problem that many of my classmates and I are facing. I want to mention the object-oriented class under the sophomore. The object-oriented class really speaks about object-oriented thinking and writes a lot of code. But more often than not object-oriented, we are struggling with the details of the code. Can use the specified Java language to write the basic functions of the program to meet the job has been very tangled, who has the kung Fu to control what object does not object it.

Now the soft work lesson, is also this feeling. Another big job in this semester, the database, too.

So although compiling the course design is the most difficult, but the most comfortable to do. Because as long as you have figured out, you can write, you will not ask yourself: my vision needs some things language support is not supported, because you are very clear, what this language can do, how to do.

We do learn a lot of languages, compulsory C, elective has c++,java,c#,ruby, but with the proficiency of really limited.

It may be that our efforts are not enough.

[Reading Report] Construction of the law (i)