A summary of software engineering practice

First, self-improvement

There are other things to do this semester, although not much time spent on this matter, but the harvest is still a lot.

Practice itself is of no use, but it can improve the understanding of the theory (in fact, the Book of the Law of construction). ）。 Design and implement our small project from scratch, let me know what is called requirements analysis, MSF, design patterns, PM, testing and so on these concepts, also have a preliminary understanding of them. It belongs to the programmer's entry stage.

Coding is mainly to do some of the android things, time is limited, there is no system to learn a language. But it will be good haha.

Learning habits are mainly used to git, blog use, in the Quora and other community attention to some cattle broke the Daniel, expand their horizons.

Team is to learn how to communicate effectively, how to efficiently meet, discuss, brainstorming, how to solve the problem of differences.

Two, my man moon myth

Look at things different from the perspective, for a project, before the project is engineering, now look at the time in the brain will automatically divided into various functional modules, user roles and so on. It's as if you've seen people before, and now it's gut, blood vessels, nerves. O (^▽^) o

Iii. Suggestions for Freshman

What you learn is useful, maybe some subjects look very silly, fart with no, but as in this field of continuous deepening, will find that these theories are still useful. Some books look tall, do not be known to be fooled, introduction to the algorithm, Dragon book ... Just a starter book, you just touch the door handle, even the door is not in.

Although now will point Android,ios, draw the page what can have a good income, but lining not, just play not deep, is can be replaced only. Two barrels, now loaded with 100ml of water, but one capacity is 100ml, the other may be 100L, which is good or bad is obvious.

Time allocation is very important, time spent on the theoretical effect is not necessarily good, learn something simple, can make the product is also an incentive for their own.

Iv. your expectations for the future

Interest-driven, perseverance, knowledge and the unity of the line.

The iron also needs its own hard. ---Kobe Bryant

A summary of software engineering practice