10 + years of Java Programmer Software Development Summary

In many cases, we always go forward but forget to make a summary of the past, continue to move forward. Re-reel this thing has been stressed, but few people do. here are some rules of thumb for Java software development that have been summed up over 10 years as a Java programmer: Java programming is really not an easy thing to do . no matter how much you like or do Java programming, there are always obstacles to learning and solving problems. The longer you work, the more you will understand this truth. But this is a chance to make progress, because you have to continue to learn to be able to solve the problem in front of you very well. If you don't have the gumption, you'll want to give up when it's impossible to solve. Java programming is also one of the most frustrating things to do The normal programming process is this: try, fail, learn, think, Inspire, succeed. In this long process, often people will feel frustrated is also very normal thing, if the final success, then you will want to challenge more difficult projects, of course, the previous frustration will be new, but also a new learning opportunities, in this process, we have to know how to adjust the good mentality, from the new hair. Way is always more difficult than through continuous learning, our programming technology will become stronger and more confident for ourselves. Everyone will have big and small trouble experiences as a child, but as we grow and strengthen our abilities, we seldom go to the wrong things. And now we have a way to solve our mistakes. Java programming is like magic, and each of us becomes a magician. through our efforts to learn the various skills of programming, when you make a variety of programming code, so that others can easily operate to get the effect they want, they will feel like a wizard, because we provide these features can make them easier, they also need our skills. architects tend to write code to make the best decisions in my run of tech lead courses, I'm advocating that technology leaders spend at least 30% of their time writing code. Spending time on coding helps build trust, respect and understanding of the current system. In making architectural decisions, it is often the case that the constraints of the current system do not take into account the decision of the beef plate surface. change takes courage . I remember someone who talked about XP values, one of which is courage. Courage is necessary for leadership, because you risk failure and try to risk/reward for something new. There is no risk, and often there is no great return. successful knot-to-Java programming is related to good collaboration While not all pairs of programming environments are healthy, I believe that when pairing programming works, teams often have a better culture of collaboration. Many developers prefer the (long-term) branch-based development anti-pattern because it delays feedback and potential sources of conflict. I used the (navigable) conflict as a health symbol for the collaboration team. Delayed feedback, such as long-term branch code reviews, often leads to more dissatisfaction as it is delivered so late. when Java programmers want to prevent the time, not a long working life, experience is rich, the ability is strong, the older the more difficult to find work. I have a friend who is joking with me, people who work for 5 years, may have a big gap in ability, why? Because the first year they do things are the same, all write procedures, 2 people may be due to different values, 5 years after the gap will be very big, even too big to catch up with the extent, why? Because there is still the factor of opportunity in the inside, some people to do 5 years, or in situ, and every day will only write those added, deleted, modified code. Then you have to pay attention to the need to constantly improve themselves, is the hard truth. For example, you will SQL Server, that should try to learn Oracle, you are doing C/s, that need to improve to B/s, you are doing stand-alone software, it needs to improve to network software, you only focus on their own work, need to learn to manage, care about other people's work. You are a programmer, to try to improve when the project manager, department manager, the director of the company, and so on, people have ambition and goals will continue to progress, the most vulgar in order to earn more money, improve job positions, work units, is also understandable. Health is the capital of revolution Remember the days when you used to work all night long to release the next version, but still feel energetic? Put on your headphones and immerse yourself in the ocean of code. Only the warm light from the screen, and the trash cans full of coke cans, and the messy pizza boxes. the days like that are gone. When you're old, if you're going to get a new project, you can't do it again. Because your physical condition has not been allowed. Your current body is more like a business partner, good cooperation can help you work, the cooperation is not good, will drag your hind legs. Continuous Learning we need to constantly learn and understand software development. You can try different programming languages and tools, read the software development books, and accept the MOOC course. Believe me, quantitative ability to achieve a qualitative leap, these small accumulation of learning, one day will greatly improve your knowledge and ability. want to know more about the "Power node Java Academy" public number, want to join the Java development industry, now the Power node Java remote Basic class free learning places, for the students who want to learn Java programming is undoubtedly good news, the opportunity is in front of you, come to register, a limited number of places, First come, first served.

10 + years of Java Programmer Software Development Summary