"The Law of construction"--I'll spend a semester reading you know you

Software

1: Why read the "Law of construction"

Take the time to see the software engineering this book, like the teacher said, "good books are wasted, how can also be a block." No, I'm sorry about our Grandpa Mao! When I first got this book, the "Method of construction" came into my mind and thought that this book was teaching us how to "build" good one software? How do you name it? At first I was only a task to read the fifth chapter, just a simple look and not too much thinking. Have to say, compared to other books, this is so dull, not a little bit of attraction, at a glance, are all theoretical knowledge, no actual related operations. It is very difficult to look at the heart, so for each chapter I have been a glance, think of just how to quickly read, and did not think of other. This is the first time I have read the idea and conclusion of this book.

But when I read the second time, I would otherwise and then change the kind of thinking, why the teacher asked us to read, I am afraid is not just to not waste money, more is to let us contact to understand what software engineering is. So there are some questions in mind, "What is software engineering, why do we need a semester to learn". With these questions, I re-read the "building method", with four words can be summed up "benefit".

2: The first feeling after reading the book

After reading one to fifth chapters, it is natural to put one to the fifth chapter string into such a line: What is software engineering, how to write code when the individual can write efficient and useful code. In the future as a software engineer and how to continue to progress, how to find a suitable position in the team. For one to five chapters, so crossed don't know right (first question).

3: The question solves, the heart is joyful. Rebirth question, how to answer.

Read the first chapter, suddenly, this is software engineering AH. All along, I thought that software engineering is the same as the structure of the building, but the system, mechanical, all the code is set together regularly, thus constituting a software. After reading the definition to know, software engineering is "the systematic, standardized, measurable approach to software development, operation and maintenance process." Software can be a commodity, but different from other products, it is a logical product, abstract and easy to replicate, by the program and software engineering. The software will also crack as slowly as the building, which requires maintenance to ensure its availability and durability. At this time the programmer will have to re-test their code where errors, how maintenance can be remedied. It is better to nip the problem in the cradle than to fix it, and the "Unit Test" appears. Unit testing can effectively guarantee the quality of the module. And so is the performance analysis test, which is

said that for the same function, in order to ensure that the function is not compromised, how the code can save the system overhead. For example, the for () loop condition in the page will just i<m_wordlist. Count to i<count,System.Collections.ArrayList_get_Count () The number of calls and time are greatly reduced, about this point I have been trying to understand, just change the conditions for what difference will be so big, this is what causes, in the future when we write the program how to avoid the emergence of this phenomenon. (second question)

4: "Unity is Power", good at using the team, Discover unlimited potential.

When the second job, when the teacher put forward the pair, I think it is just such a small program, there is no need to pair. When you start pairing a pair with a little resistance, the more you can find the benefits of pairing later. Especially after reading the book feel, knot pair is not pure from a person into 2 (fourth question)

The saying goes, "You have an apple, I have an apple,2 people together there will be 2 apples", thought is the same, but the idea should not simply add, should be a systematic convergence, become "thought crystallization." The production of the software requires a team, a person can write code, but write out is some relatively simple features, contain more bug code, but the team can not only avoid this situation, the team not only have a consistent goal, and a clear division of labor, Relying on each other to work together to complete the task, this can greatly improve the software production time and software utilization, which is why there is a team reason. In the fifth chapter , we begin to introduce several software team models, each of which seems to have its own advantages. How can I choose a reasonable and effective model for my team with no experience of teamwork? (question fifth). Is it based on the specific situation? Or listen to the ideas of the team members to determine the pattern. I don't think that's the way it is.

5: Inspire Life thinking, the future how to go, now how to do, what to do.

There is no way to anticipate the future. So we should grasp the current, for their own efforts. "The growth of software engineers" gives me a better understanding of how the road ahead should go. I enrolled in the 5 months of the soft test programmer, want to step-by-step efforts, and finally get the software engineer this certificate. Sometimes think, I just very simple to learn the software, just write a very simple code, and we are 2B School, and then go out to find a job really can find a good job? Although the third chapter explains how to become a "software engineer", how to detect whether you are qualified engineers. The first page of the book describes the "growth of Junior engineers" in detail, and I am also rethinking if I have done one of the books. Thought for a long time did not want to understand. What do I do to be a junior software engineer (the third problem). From the bottom of the soft test programmer over to the beginning of the software analyst, and finally test software engineer. Or that I follow the book's page on the introduction of junior engineers, accumulated relevant knowledge, and finally to soft test "software engineer."

6: Summary

Reading this book The biggest harvest is to know what a qualified software engineer is, how to do to improve. Books can be read many times, each time will have different feelings, will have different understanding of things. I think this may be a manifestation of growth, as the growth of our team will be a lot of things to think differently. For the "Construction of the Law", I also think so, now I just very superficial understanding of software engineering, not any actual, but a semester of quantitative changes can let me see qualitative change, then read carefully, may be more feel, more know how to learn what they want to do it.

Come on, boy! Wonderful Life is waiting for every one of us!

"Building the Law"--I'll spend a semester reading you know you