You're only coding between 9 and 5 in the morning, but are you worried it's not good enough? Do you see other programmers working on personal projects or open source projects, participating in programming marathons, and spending all their spare time writing software? You might think that coding only in your own working time, writing software for Nine to five, will never be very good. You may think that only those who are coding in the room of eating, sleeping and breathing can stand out. Wuhan Java Training Experts remind you, adhere to the 40 hours a week work time can still make you become a valuable, skilled programmer, together to see how to do it:
Working on an individual or open source software project will not make you a better programmer naturally. Programming marathons can even be a negative effect if they make you feel that building software has an arbitrary duration, while exhaustion is a reasonable way to produce anything of value. There are many inherent limitations in your productive working hours. If you do not like to go home and then take the time to code, then do not be too tired, do not drag the three-drag four and half-hearted.
Spending time on an amateur project does have some value, but the most useful result is more knowledge than practice. Building software projects often uses older technologies and processes, as these process technologies have existed for some time. The valuable knowledge you get from working on other software projects and interacting with developers outside of work is: a wider range of technologies and tools.
New technologies and processes. Your company may not have done too much testing, but you can learn about test-driven development somewhere else.
Having a wide range of tools and technologies is a valuable skill, whether for your current job or for a new job. But the actual coding is not an effective way to acquire this knowledge. Because in fact you don't need to use new tools and techniques, and no matter how you never really have the time to learn all the tools and all the technology in detail. You can only get the most valuable content by knowing what tools and technologies are popular today, what these tools and technologies can do, and under what circumstances they can play their greatest role. If you find a new tool that can be applied to your work immediately, you can learn the new tool at work, and if you can't apply it to your work, you'll have to categorize it in your brain and use it later.
Learning new tools can also help you find new jobs, even if you don't actually use them. Was asked in an interview about the difference between NoSQL and traditional databases. To be honest, I've never used MongoDB or any other NoSQL database at the time, but because I've known it, I know how to answer it satisfactorily. Being able to answer this question makes the interviewer believe I can use the tool when necessary, even if I haven't used it before.
By focusing directly on acquiring new tools and technologies, you can gain the same benefits and be more efficient than coding in your spare time. And because this knowledge will benefit your employer, you don't need to spend a significant amount of time on it to get that knowledge in your working hours. You don't feel like you have a real free time every day, but you always spend some time doing nothing on the Internet. Maybe you're surfing the web now! You can use this time to broaden your knowledge.
Wuhan Java training Experts believe that you should schedule one hours a week to learn new tools and techniques. Choosing a specific time can help you develop a habit. Personally, I will choose to be in the afternoon of Friday, because at this time I have nothing to do anyway. Do not skip this study time because the project deadline is approaching or you are tired. You will do better in the deadlines and not be so tired if you know the right tools and techniques to efficiently solve problems in your work.
Wuhan Java training: Tips for Java programmer skills Upgrade