Java growth path [download u]

Share Summary
The road of Title:java growth
Tags
Grammar_cjkruby:true

• Experience differences
  • 1-3 years
    • Requirements
    • Suggestions
  • 3-5 years
    • Suggestions
  • 5 years +

Experience differences

The last year was a busy one, experiencing the collapse of a startup company. This time came to a start-up company. Because I want to share experience, and have not written a blog for a long time. So just put this share to write about it, hope that can continue to persist.
To do Java. There must always be a learning route. There is an outline of what a few years of experience should be, not a muddle. To remember
Working life! = Experience

1-3-year Requirement

• I used to interview 1 years of experience, basically do not ask the framework, will only ask some API, such as: [email protected], how to extract the user name. How to find whether 123 contains 1 this word and so on simple. If the API is not familiar, you may not have really written the code before.

• About 2 years of working experience, the main question is the use of the framework. It's spring MVC now. Ask how to use the usual, and commonly used frame annotations. and find out what ORM framework he uses in his work. Therefore, 2-3 years of experience of the people, for the framework will have a certain grasp. It is better to know the principle.

• SQL is also a must. The ability to write out the desired SQL without regard to performance.

Suggestions

• Write and write, practice makes perfect.

• When faced with a problem, the first thing to do is to solve the problem by themselves. I believe this is a difficult process for beginners, but it is also an accumulation. After solving this problem, write the question to the cloud note. Make a record.

• For beginners, the best teacher is the search engine, not the forum or bar paste

• For the new entrants, the most important thing is a change of thinking. Turn a person's mind into a machine mind. You know, the world is made up of rules, and every bug you encounter in your programming is the result of a failure to follow the rules in front of you. The emphasis here is on logical thinking. There must be cause for the fruit.

• 工欲善其事, its prerequisite: tweak a good programming environment (Idea Community Edition). Choose a good cloud note.

• Forget the mouse and try to do a keyboard stream. I think the keyboard speed is always faster than the mouse. If possible, learn vim.

• Feynman skills: A way of learning, recommend your own search, I think it is a very good method.

• Efforts to improve themselves, not their own 3-5-year period of effort, if this stage does not work hard, then 3-5 years of the stage, you enter a well-known company opportunities will be very few. If you want to get into a good company, you can get some 3-5 years of content to learn now.

3-5 years

• This is an intermediate level. For the framework is the ultimate, it is best to build a wheel. For example: Write an MVC framework yourself. In writing this framework, you can master a lot of knowledge, including reflection, custom annotations, reading annotation values through reflection, line Cheng, etc. or write an ORM framework yourself. Take a look at how the transaction is implemented, or how hibernate can automatically generate tables and so on. is to be in-depth to understand. Instead of just stopping the surface, it will be used.

• Useful for a git of your own. You need to know that all of your code is wealth. In this network, do not put on the hard disk. Put it on git.

• Have their own common tool kit. For repetitive work that often works, you need to have a tool to solve them. Write the code and put it on git.

• 3-5 years should be able to achieve the standard is to see the problem can quickly locate the problem. and understand the JVM principle. And the performance has certain requirements.

Suggestions

• It's past the stage of writing and writing. At this stage, you should focus on your code style. Recommend to look at the code neat way code Daquan

• Deeply understand the DRP principle and apply it in practice.

• There should be a blog. Tidy up your initial stage and the problems you are experiencing. then share it.

• You can study the design pattern, which is about to start in about 4 years. Design patterns you may have to look at it for a long, many times.

• In the past few years, choose a good industry to do it. Don't keep switching to different industries. Accumulating some industry knowledge will be of great help to you after 5 years.

5 years +

• This stage is basically a senior engineer. If you have been in an industry, I think you can already call it a domain expert. Of course, if you change a different industry and keep progressing rather than moving the code, then maybe you're already called a programming expert.

• 5 years at this stage, no matter what you are an expert, it is important to choose a good company, how big the company is, how fast you can grow. If you have been in a small company, there is no access to large concurrent class systems. Then your development will be greatly constrained.

• Learn more about architecture related work, because this stage of people, the basic coding ability is no longer a problem, more is to broaden their horizons. Grasp the current popular knowledge, understand the difference between SOA and microservices (2016 stage), Springboot,springcloud,dubbo,dubbox,mysql master-slave, Docker,vue,mongodb,redis, Nginx, etc...

• Remember: A good platform is the key to your future growth ...

Java growth path [download u]