1. Have a solid foundation and deep understanding of OO principles
For Java programmers, a deep understanding of the concept of Object Oriented Programming is a must. Without OOPS’s solid foundation, you can’t appreciate the beauty of an object-oriented programming language like Java. Learning the definition of OO principles isn’t much use; the key is learning how to apply those principles to design solutions in an OO way. Therefore, we should have a good understanding of object modeling, inheritance, polymorphism, and design patterns.
2. Master core APIS
If you don’t know the language structure and the core API, then no matter how strong your theoretical knowledge is, you won’t succeed. In Java, it is desirable to have strong hands-on experience with core apis such as java.lang.*, I/O, exceptions, collections, generics, threads, JDBC, etc. When it comes to Web application development, JSP is a must no matter how servlet-specific the framework you use.
3.Keep coding
Lu You once said, “the paper come zhongjue shallow, must know this to practice.” It’s easy to think of a solution in theory, but when it comes time to implement it, you realize how difficult the problem is. At this point, you will understand the language limitations of the coding process and design best practices. Therefore, Keep coding.
Subscribe to community forums
We are not alone. A lot of people are working on the same technology that we are. It’s easy to just validate a framework concept, but when you apply those concepts to a real project, all sorts of problems arise that you can’t find solutions to in official documentation. The first step in learning a new technology is to subscribe to the relevant technology community forums. No matter what your problem is, there’s always someone who’s been there before you and probably already found a solution. Photoshop, can also answer other people’s questions, and it does not feel too good oh.
Follow blogs and add your own comments
As I said in the previous point, we are not alone. Thousands of technophiles from around the world post their technical insights on blogs. On blogs we can find many different views of the same technology. Some people will see this as a powerful technical feature, while others will see it as a silly framework. So you’ll hear two different voices on blogs about the same technology. When you see a good blog, you can write your own opinion, reply and comment.
6. Read the source code of the open source framework
Good developers always know how to use frameworks. But if you want to be a good developer, then you need to study the source code of various successful and popular frameworks to understand their inner workings and best practices. This is an efficient way to use a framework.
7. Understand relevant technology trends
In an open source environment, software development techniques are constantly evolving. The new framework, as it is now called, may become obsolete by then. Problems that cannot be solved in the current framework may not be a problem in the new framework. So be aware of the birth of new things and the death of old things.
8. Have common code snippets/utilities handy
Sometimes we may need to copy and paste/write the same snippet/configuration over and over again. So it’s good to save configuration fragments such as log4.properties, JDBC configuration, and utilities such as StringUtils, ReflectionUtils, and DBUtils. None of these things in and of themselves might make you special, but imagine if your co-developer wanted you to help him get a list of property values from a collection of objects and you could just use ReflectionUtil in a matter of minutes.
9. Learn about different development methods
Familiar with different development methods such as Agile, SCRUM, XP, Waterfall, etc. Now, the choice of development method is up to the customer. Some customers prefer Agile, while others prefer the Waterfall model. So being able to dabble in a variety of methods is definitely impressive.
10. You’re not afraid to fix bugs
Sometimes we have to deal with a lot of bugs when we are working on a project, but after the fact, you will find that you can only improve your level by constantly fixing bugs. What great god doesn’t start by fixing bugs? Only by constantly fixing bugs can you become a god.
11. Document/blog your thoughts on technology
In our daily work, we may learn new things, new ways of doing things, new forms of practice, and new ideas about architecture. Share your thoughts on a document or blog. Because your current solution to a problem could be another developer in another part of the world “looking around” for a problem, you will share nothing less than a long drought.
\