Summary at the end of 2015

After graduating from undergraduate and joining the job after the May Day holiday, today is 12.31, a full 8 months, more than half a year.
The direction is Java Web, although I still want to do Android.

Touched a lot of things piecemeal. I did a rough statistic, the classification is not accurate, but that's it.
Language: Java, javascript, html, mysql, unix;
plugin: Jquery, Echarts, bootstrap, trigger, Log4j;
software: eclipse, tomcat, jetty, workbench, Xshell 4;
framework: spring, maven, mybatis, svn.

It has not been used for a long time, and some technical things cannot be explained clearly in a year-end summary, so I would like to talk about some of my deeper experiences in the past six months.

1. Try to avoid affecting others, and consciously think about whether you will affect others by doing so.
This should be the most important principle at work.
It doesn't matter how you use your personal time, but because of your own mistakes, it took others an hour or two or even longer to solve it. Who will take the blame? In a harmonious team, not everyone in the team is born with similar habits, but everyone consciously considers others and the whole team.
Before communicating with others, sorting out your thoughts and organizing your language is a very pleasant thing for others and yourself;

2. Nothing is more important than solving problems. To be held accountable or to shirk responsibility should not be the first reaction.
Isn't what programmers do to solve problems? If you can solve it with code, then solve it with code. If there is a problem with the launch of the project, the team solves the problem together, even if the loss is not so serious, if the attitude of the parties is better, the team can tolerate it; on the contrary, shirk responsibility will affect the harmony of the team, and thus affect the efficiency of the team. A good team is not that they will not encounter problems, but when they encounter problems, they will solve the problem first.

3. Don't do things with intuition, list plans and steps, the efficiency is far higher than direct shots.
After a long service life, it is easy to develop a habit of thinking, and when encountering a problem, it will be solved subconsciously. For programmers with enough experience, it's a good thing, and their intuition is often accurate; for inexperienced programmers, such as me, don't follow their instincts. If there is a problem with the maintained code, don't look at the code directly. It is often more effective to spend ten minutes analyzing it. Before experience is not enough, solve problems with logical thinking, not intuition. If an error is reported in a certain file in the log, go to the corresponding file, which is a waste of time. It is more efficient to look at the overall logic of this business and think about the reason for the error than to look at the code directly.

Fourth, take some time every day to make plans and review, it will be much better than no plan. There are summaries to gain more.
I work 9 hours a day, and I usually don’t spend more than 3 hours writing code. Most of the time, I am solving various problems encountered, and I am also bragging in various groups and forums. Make a small plan for yourself every day, even if you can't complete it, you will feel that the day is full and people will not be so impetuous; and if you spend an hour a day summarizing, you will gain more. You can know the allocation of your time in a day, and what pits you stepped on when solving problems. Accumulate more, gather sand into a tower, these things, accumulate points every day, your knowledge and skill system will become more and more complete.