Personal summary of introduction to software engineering

A semester is about to arrive at the end, immediately I also want to enter a junior, Wang Jianming teacher told us that the real University study time only left this year, can look back to sophomore this semester, there are too many shortcomings, is summarized as follows.

Winter Vacation Teachers decorate the task, but also said that the first class will be checked, I can imagine, my results are bleak, the first class of class test took 0 points, which also let me know more, this lesson is not can mix out.

Teacher Wang's class is really good, language humor, voice loud, each class is sitting in the first row of I can seriously listen to this minute. The introduction of software engineering is not as I originally thought, to learn some code knowledge of programming software, but focus on software development and the whole project engineering, human, team, and software aspects of the appearance of knowledge.

The first class, the teacher told us our major, no matter what class, or even the future after the employment, we should learn to "do high school", the teacher will be the idea of the implementation of the good in our body. In addition to listening to the professional knowledge of each lesson, there will be class assignments and homework, which is my favorite aspect. Because we do not learn more about programming in this semester, and for our programmers, programming is the foundation, the code can let us grow, so every week this practice, so that we better consolidate the existing programming ability, but also continue to learn new code knowledge, new language.

Just started to write two pillars, it is really annoying, because the beginning of programming we still only realized the function, a lot of software needs to do is not only the implementation of the function, there are many details of the problem, to the first mention of the bracket problem, division sign before and after the problem is not 0 , and so on, We realize the function at the same time, but also to think about the software itself, software inside, become cool, function, value and so on, there will be a lot of problems. Through the continuous "two pillars" of the preparation, these capabilities are also constantly improving.

When it comes to team development, there is only one concept before the beginning of the course, and we know that our personal strength is not enough when we face ambitious projects in the future. So is team development just as simple as writing a code together? The answer is definitely negative, do software, do projects, not just to co-author code So simple, everyone's division of labor is different, responsible for different modules, and the team's development process is not just write code every day, we need to meet, need to summarize every day, need to understand what each team member has solved, what is the problem, Team cooperation will not be so smooth sailing, so how to write their own procedures, but also in the team and others to work together happily, we need to learn.

The first team sprint, to tell the truth, we have completely in accordance with the requirements of the teacher to do, the daily stand-up meeting is not so formal, but when the program began, gradually we began to work together in the team to the right track, the development of their own daily summary of the author, We also know what we need to do in our team in the future when we get into work.

As a software engineer, the most important thing is not the writing of the code, but the writing of the document. For us, we not only have to write the program, but also in the popular language to write all the project into a document, the code of their own programming process, problems encountered in the solution, as well as with the team of other members of the cooperation, and their own growth in this, should be able to reasonably classify and document writing to save. This will not only allow us to see in the future our own growth process, have a detailed understanding, but also to let others read our program documentation unfortunately very thorough understanding of our programming ideas and ideas.

To the "Construction of the Law" This book is not thorough understanding, but has benefited, for programmers, we can not follow the only in the classroom to learn knowledge, more in the spare time to read more books, read information, enrich their professional knowledge, the real learning "to do the middle school."

Personal summary of introduction to software engineering