Read Note 02

Reading the third to fourth chapter of the Law of construction

Read time again, open the mobile phone reading software The third and fourth chapters of the Law of construction were read in detail. It mentions a long-lost and deeply confused problem, and that is the growth of our software Academy students in this field.

As a software engineering student, the students are puzzled by their own growth and future appearance. So, if you are positioning yourself as a software engineer, how can I grow. First of all, to accumulate knowledge of software development, improve technical skills. Second, accumulate knowledge and experience in problem areas. Then is the general software design thought and the software engineering thought understanding. The software on the journey is the upgrade of professional skills. Vocational skills are distinguished from technical skills, including self-management ability, ability to express and communicate, ability to work with people, and execution of tasks by quality. Finally, the main description of the qualification of a software engineer-the actual results. This is how a software engineer has grown up in the general history. With regard to career development, I think this is also the problem of most students majoring in general. We can choose the grade of the road or into the major companies to temper development or other channels, the choice of course diversity, but the same point, the real engineer level is that he got a project, can accurately analyze the difficulties in this project, can write a detailed document to allow several team members to complete the project according to the document writing. Such a level of course cannot be innate. Learning life in the middle of a bit of accumulation, not to get the problem according to other people already have code to copy it again, maybe you just understand. To do something, you have to experience it and end it alone in a series of torment, so that you can truly call it a harvest.

The personal growth of software engineers is to practice summing up the experimental programming practice summary, which is the basis of personal development, but we end products are dealing with people, when in the future engineering practice encountered big problems can not be solved independently, we not only have personal ability, but also need teamwork, Two or more people work together but end up with an interface to stitch together into a complete project. This involves the code specification, the exchange discussion, this pair programming is also the perfect way to temper ability. The book emphasizes the cooperation of the two people to pay attention to the code, and indeed I am in cooperation with peers to write programs, encountered the code is not standardized to bring serious consequences. I usually write the program although the parentheses can be written in pairs, but do not pay attention to the matching brackets, so often do not know where to end the loop, the output is often the error, often because this wasted time. And I used to be the program before the comments, and only a cursory write some, because the teacher asked. But this time and companion write procedures, I deeply realized the consequences of not seriously write notes, my companion can not understand my algorithm, and I explained when I also forget the idea of the time, do not understand their own procedures, visible note is not only to let others understand their procedures, but also to prevent themselves from forgetting their own procedures. The most impressive thing in this chapter is the handling of the error, we now write the program can only be entered according to their own requirements, but we do not know what the user will enter, when the user input does not meet our requirements, we must have a corresponding program to deal with it, and this ability we have to practice from now on.

Code specification is a programmer's fundamental, so, to start from the specification, bit by bit progress.

Read Note 02