The review, analysis and summary of this course of software engineering

First of all, in this earnest: to the author of the Law of construction to give 100,000 points of appreciation, as well as the software engineering This course of teaching teachers to give 100,000 points of appreciation, but not least, the software engineering This course of teaching assistants to 100,000 points of appreciation.

Why thank the author of the Law of construction?

Since reading, I have read a lot of textbooks. The textbooks of the past are very dull, like the heavenly Book, look at a long time will fall asleep. On the contrary, this textbook of the law of construction broke through the shackles. To be honest, the first time I opened this book, the vivid image and interesting content in it have attracted me deeply. In addition, the most attractive feature of this book is: the use of virtual characters (such as small fly) dialogue and activities, software engineering-related content to display the image.

From that moment on, as long as there was time, I would go through the law of construction. Because often read the "Construction of the law", to understand the software engineering related content has a great help. Remember the first homework "college Professional and employment sentiment" in this blog, I wrote that "people in the IT industry have to delve into the brain capacity needs are particularly large, which for our girls may be unbearable." So I think I will not be in the IT industry. "That means I'm not going to work on software engineering until I read the law of construction." However, after slowly reading the "Law of construction" and learning software engineering related content, now if you really want to say that their future engaged in the industry, I am not sure, because it is really difficult to choose, but, at that time the idea has slowly changed.

So, to thank the author of the Law of construction has brought us such a great book, it is good to read such a great book, thank you, really thank you.

Why should I thank the instructor for this course of software engineering?

A semester down, the teacher carefully prepare lessons, serious teaching, painstaking, hard-work to accompany us for a semester. Also, we have witnessed the stumbling and persuasion in the course of software engineering. She's like a light in the dark, illuminating the way we're going, and guiding us in the course of software engineering. This can not help me to associate with the "teacher, so preach bred doubts also" and "to Steed first Way", the teacher said also.

So, to thank teachers this semester since the painstaking, hard-to-do teaching, thank you, really thank you.

Why should I thank the teaching assistant of the software engineering program?

The communication between the TA and us is generally done through the Internet--and in real life it is usually impossible to see him except in special circumstances. Remember the first time you actually met the TA because you wanted to teach us about Git hub. To be honest, at that time, after listening to the whole not understand, mainly because we first contact git this tool. Later, after reading the assistant's Git Hub in the group, I didn't understand it, but at least it worked. The second time is to teach us about unit testing. At that time, when hearing the unit test, many students thought it was to test it, after the teaching assistant, know that unit testing is testing software. This lesson taught us a lot about the template of unit test, very practical, still vivid in the present.

After a semester of cognition, probably understand the TA is a serious work, high efficiency, dedication, meticulous, knowledgeable and more knowledge ... of people. I am very happy to be able to study with the help of the people with positive energy, thank you, really thank you.

Just a few lines of text is not enough to express my gratitude, but I believe this gratitude has been achieved.

Then, this semester's study, the project practice carries on the review, the analysis and the summary.

Honestly, the Software engineering This course gives me the feeling is to tell us what to do, and did not detail how we do, how to achieve, as to how to use the program code to achieve the corresponding functions, or rely on our own research.

Remember, I wrote three times in the summary of compound interest in the blog "Compound Interest Calculated 1.0: Just beginning to even what is compound interest do not know", which also shows that the beginning is not very suitable for the course, the requirements of the completion of the work is not very satisfactory, after a period of "baptism", began to slowly adapt to such a course, Have a certain understanding of the work, the completion is also so-so! In the third chapter of the Law of Construction, this blog wrote, "I am confused, even if the future is to engage in software engineering related to the work there are many problems," at that time I did not write out the confusion, but now, I very clearly know what I am confused. To put it simply, I was terrified, frightened, and not a little confident about my work in software engineering. Sure enough, time is the "killer" that changes everything.

In the fourth chapter of the Law of Construction, this blog reads, "Is it possible for programmers who write software with strong abilities to write software that will be less efficient?" Also, in this premise, should not pair programming it? "In fact, in this case, we still have to pair programming, so far it is still very puzzled by this practice." After this, the experience is closed to programming. In general, the two pairs of pair programming left a deep impression on me, not only to some extent to avoid some ridiculous low-level errors, but also can analyze and solve problems, as if it is through the two people constantly brainstorming and knowledge collision to solve the problem, but also let me obviously realize the superiority of the end of programming. Most importantly, pair programming is enjoyable!

Experience team work after pairing programming. Started our scrum journey, and then the team was with me through Sprint 1, but unfortunately ended up with split up. In two development 2.0 this blog reads, "Is it really complicated to finish a team project?" First of all, the team means not the individual, and secondly because the team has different abilities, so cooperation can be difficult, there may be many problems exist ", now, I am still at that time of the mood. How to say, this kind of mood is very complicated, perhaps this is one of the reasons that slowly turn into later split up.

After the team split up, I started the Sprint 2, Sprint 3 journey, feeling, experiencing, growing a lot. In Sprint 2, the blog concludes that "at the very beginning, there is no confidence in what can be done, which step." However, my heart has repeatedly appeared that sentence: Before the dawn is the darkest, but do not close your eyes, because dare not look directly at the dark person, also can not see the first ray of light tomorrow. So, I always say to myself never give up! Looking back at the whole Sprint, it can be said to be full of sweat. But, after seeing the results, the kind of joy that cannot be spoken, it dilutes the bitterness and sufferings that have been encountered in this period. So, all the effort is worth it, and now I'm still the idea of that time. This kind of mood can support me to walk how long, walk how far I do not know, but, I can be sure that this mood is to support me to go down the motive force.

Looking back throughout the semester, I really experienced a lot from the very beginning of the Mengmengdongdong to the subsequent series of changes. This process has sweat, tears, also have laughter, I think more is sad and suffering it! Maybe for some people, it's the end of the semester, for the time being, instead, for me, it's the beginning of a new journey of experience. A long time ago has been planned, this time, must be good to achieve. "Face, not necessarily the most sad, lonely, not necessarily unhappy." "The most important thing is to believe in yourself, pick up the courage, face the difficulties!"

Finally, give feedback on the work of the TA.

When it comes to teaching assistants, the first impression is that work is a serious study, high efficiency, dedication, knowledge, and many other advantages. However, no one is perfect, everyone has a little more or less a loss of the shortcomings, of course, our "perfection" of the TA is no exception. Frankly speaking, the work of the TA is really impeccable, if hard to find a little flaw, I think it is about writing academic integrity and professional ethics that blog. How to say, at that time, his kind of practice, I completely puzzled. It's strange, why do that, I have no idea what special meaning is inside. In addition to this little bit, all the work of the TA has done well in detail and I hope he will keep it.

The review, analysis and summary of this course of software engineering