Java Programmer Five years work learning experience Summary

first send this paste not why, just want to summarize their experience of the past few years, but also feeling a bit, after all, after five years, after all, carding good their own, in order to better planning the future, but also let you take a few detours, although we are very young, but after all, time is precious, cherish the present, seize the opportunity is the
Over the past few years, my biggest feeling is a word: Read more, write more, think more, ask more, share more, optimize, multi-exercise ...
1. "See more"
read thousands of books and walk the road.  Read more books, read more people write code, look at other people's problems, read more related technical books, read more documents, see more ..... Many things need our eyes to see, of course, many people will certainly say, which have so much time to do these things, I can only answer: squeeze time. Whether you are just out of school is confused, and no matter you are working for a few years, the achievement is very expensive, "see more" absolutely try any stage of the person. Some people do not know how to solve the problem, it is because you encounter less, how to do: have time to look at other people's problems, more to see other people's technology sharing, there is always a suitable for you, or for your future will encounter problems (here more than technical aspects, including life aspects). Also have a look at some technical books, enrich their knowledge is really important. Here I recommend a few: "Refactoring-improve the design pattern of existing code", "Architecture exploration"-Starting from scratch Java Web Framework, "Java Programming ideas" (this is really a very good foundation of the book, although I did not read it.) ), "in-depth analysis of spring architecture and design principles", if you are interested in distributed, you can also look at "large-scale distributed storage System." And the most important: Read more documents, for development, combined with requirements and design documents to do, development can save 30% of the time (changes in demand often not counted ...) )
2, "write more"
good memory is better than bad writing, standing on the shore to learn not to swim. Just see certainly not, also need to write, for not understand the technology, find information, their code to knock over, first run up, and then step by step research principle, this will be more impressive. Far more than you all the research source strong. You can write down, blog, or log your own research skills, bug fixes, or solutions. I personally tend to write a blog, because I know that memory is limited, at this time I remember deeply, will always forget. But as soon as I write it down, and later encounter this kind of thing, I just turn over my blog, look at my previous records, can quickly solve the problem. I like to write a summary, whether it is a bug, technical experience, or the problems I encountered. I will also record it to motivate myself. Of course, this is why I like CSDN, because there are resources I need, I help others, but also help themselves.
3, "think more"
The idea is far more than your plan. The work encountered the bug is very normal, sometimes a solution can not, do not merely, may change a way to solve, the window is closed, we can still open the door? Encountered a bug can not solve, a way not we continue in a different way, there is always a suitable. In fact, before the procedure, to get the demand, we not only to see, but also to look carefully, seriously, in fact, the need to analyze everyone can do, as long as you dare to think, for business considerations, if required to do so, there will be any deficiencies, or there are several ways, why do this? There must be some of the merits, you want to understand, next time you know how to analyze what you need to do the functions, modules, and do more perfect, perhaps this will allow you to spend a lot of time in the pre-work to think about the needs, but once you complete the confirmation, the real development of the time, in fact, as long as the original agreed (except for certain special occasions)
4. "More Questions"
fools, humbly ask for advice. Work encountered problems, you do not always have to solve their own, check the data can not find the answer, how to do?  Ask! Ask who? How do you ask? That's a problem. Ask a lot of learning, for example, if the demand causes you not to go on, ask the needs analysts, or ask your manager, they must know, if they are not sure, then you can stop to rest, because you continue to do is also white. If it is a bug in the development of the project, cannot find the data can not be solved, then you can ask experienced colleagues, or to csdn to post for help, the vast ape sea, there will always be someone to meet or solve similar problems. If no one else can help, then another way to achieve it. Never be complacent, once I have been complacent, but the reality gave me a slap. It is never obsolete to ask and learn more. Here is a small idea: just enter a new company or a new project team, with colleagues must play a good relationship, perhaps he is a certain aspect of Daniel?
5. "Share More"
Give people roses, hand over incense, share their own technology, their solutions, their own problems, share all feel able to help themselves or others have knowledge or articles, are very good, the reason we can in Baidu, Google can quickly search the solution to the problem of the answer,  Is it because there is so much to share with the selfless program of our ancestors? For people to solve the problem is also a kind of sharing, I know that I do not know a lot of other people ask questions, I can not perfect answer, but I see the problem, I will go to search solutions, I will think how to solve, even if not solve the problem, at least I know that there is knowledge, I can probably know what solutions. Next time you meet a similar thing, do not save a lot of effort, and then for others to solve the problem, but also in the growth of your own experience ....
6, "Multi-optimization"
life is a process of continuous self-improvement and no end-point. I do not know if you have read the program/code you have written before, you will not have a day to write a bad, yes, is very bad. And then just want to optimize it. I am always like this, it is possible that I have just written a good function, project, only a few minutes I will be thinking to optimize. Borrowed the title of Spring official website: Let's build a better Enterprise, technology is always optimized to become more perfect, now the strong spring is also so, I certainly do not expect to reach that height, but I can do is to make their projects more perfect. It's okay. Multi-encapsulation, multi-structure of their own code, time will surprise you
7, "Multi-sport"
life is like a trip, do not care about the destination, care about the scenery along the way and the mood to watch. In front of the question of how to do so many techniques, and finally, the topic of ease, as a programmer, I clearly know that our industry is sick, so I try to avoid. What to do? More exercise, go out to walk, do not always stuffy at home to do a technology house (there may also be game houses), I also like to play games, including now most people play lol I also play. But I also like to go out for a walk and ride a bike on weekends. Riding is one of my hobbies, why? Because I have not only exercised the body, but also made friends, and can see the scenery that I want to see, enjoy the pleasure of reaching the destination, relax and enjoy the beautiful scenery, feel exhausted, tired and hope to get home at once, hysterical. This is not home tender experience, said so much actually just hope you have a good body, the body is the capital of revolution, take care of yourself, don't let the people who love you worry about you, this is a very happy thing, of course, no matter what, happy the most important ~

Java Programmer Five years work learning experience Summary