This article was created in spring 2018 and is now republished.

This article records my growth from Java beginner to focus on Java backend development technology stack, mainly related to blog writing, other content also includes internship experience, back-end technology learning process, school enrollment plan, I will publish and provide links.

I’m making:

github.com/h2pl/MyTech

The article was first posted on my personal blog:

H2pl. Making. IO / 2018/04/20 /…

More on Java backend learning can be found on my CSDN blog:

blog.csdn.net/a724888

Java back-end learning path blog.csdn.net/a724888/art…

Where dreams begin

It has been more than a year since I started this blog in early 2017. The first blog opened in blog Park, later felt CSDN ecology is better, so moved to CSDN. I was working on a school project during this period, so I recorded some problems and solutions in project construction and development at the very beginning. At that time, the technology was still relatively young, belonging to the stage of just getting into the Java Web. So the blog content is also relatively ordinary.

The blog records my growth

In the spring of last year, I joined the vast army of spring recruitment and determined the direction of Java development at that time. At that time, I did not know much about background technology, so I started a series of study and preparation mainly from Java and Java Web. This article is mainly about the experience of blogging. If you are interested in my learning experience, you can check the link at the top.

After the end of the project, I mainly reviewed the basics of Java, so I read a lot of related blogs and recorded a lot of basic knowledge points of Java, such as exceptions, reflection, serialization, collection classes and so on. Now IT seems a little naive. That’s why I’ve been deleting some of the low-quality articles so that people can see better content.

During the preparation for the spring recruitment internship interview, I spent a lot of time reading technical books and blogs, and summarized some of the interviews. At the same time, I posted some good summaries on the blog, so that I could read and review during the review period. Therefore, FOR a period of time, I posted a lot of blog posts, so that I was even afraid of myself. Of course, I do not recommend such a practice. In the later days, I usually send some articles of a certain quality regularly, and try to clarify the content of the article before Posting, otherwise there may be a situation of making up the number. In addition, I also recorded some engineering contents, such as the use of Maven, Git, Tomcat and IDE, as well as some experience in using MySQL. Since I had an internship in netease games for a period of time, I mainly recorded the technology stack used in the internship and relevant development tips.

After I left netease games, I came to Baidu. The department was mainly engaged in cloud computing, so I recorded some articles related to cloud computing, such as OpenStack, Docker, Kubenetes and so on. Baidu is a technology-oriented company, and it often holds technical exchanges and sharing meetings. I usually sign up for them, and have learned about the application and realization principle of AI and big data. Therefore, I will mainly post some AI and Hadoop articles during this period, so that I can have a more comprehensive understanding of related technologies.

Good at summary, after reading a book, the best summary is reading notes

During my time at Baidu, I realized that my foundation might not be solid enough. Because is trained, though it is master, basis but there are still some lack, this paragraph of time I see a lot more at the bottom of things, such as network, operating system, Linux kernel, among them that a deep understanding of computer systems, is indeed a good summary books, basic can bring you an overview of the computer system as a whole.

Therefore, DURING this period of time, I wrote a lot of summative articles such as reading notes, mainly covering operating system, computer network, Linux and so on. I found writing reading notes is a good way to deepen understanding of the original book, so I’ve seen some books take up and turned over several times, the JVM virtual machine, for example, Java concurrency of actual combat, large website, so I would put your other books reading notes also sort out, but there are some books are too difficult or too thick, Also draw lessons from the reading notes of some bloggers. Of course, many articles are not mature enough.

Accumulation is a good habit, details determine success or failure

Big company interview, will give you a feeling, is pervasive, details determine success or failure, often shallow summary is difficult to let you understand the underlying principles of technology, lack of practice or in-depth thinking, may let you miss a lot of important knowledge points, and often these knowledge points are big factory interviewers like to ask.

In the case of Java, the JVM garbage collector can ask deep questions about gcRoots, how many pauses, whether concurrent collections, etc., which may not be covered by a superficial summary of GC.

For example, JUC Lock, usually may only understand the use of Lock, condition, the use of concurrent tool class, but the underlying AQS implementation of Lock, may be little to pay attention to, AQS related source obscure, recommend to see the analysis of Daniu, can let you better understand the implementation of Lock class.

In fact, this idea is a while ago I just thought of, because see Ali’s practice, Java related principles ask particularly deep, not deep into the source code to understand, often will be asked. The result is predictable. So the main idea during this period is to only record high quality content and try to cover the important points.

The paper come zhongjue shallow, and must know this to practice

No matter how good an article is, it is on paper. Once I get started, it may be a different story. I read a lot of books and read a lot of good blogs, but THERE are some technical details that ARE still a little bit bad. In fact, memory itself is such a characteristic, only practice can make the knowledge of the book become your own. To have a say in the technology, you need to use it and understand how it works. So in the future plan, I plan to write more practical articles.

Go back to the beginning and start again

From the first time write a blog to now, experienced a lot of things, have a lot of feeling, with your mutual encouragement, as to my point of view identification or not, that depends on opinion. Don’t forget to look up at the stars. It is recommended that friends who do development should write a blog. There are many benefits of writing a blog, which is convenient for memory and communication. It is also a way to build a personal brand.

Recently I started my blog with B3Log Solo, and I’m going to start my blog with Github Pages + Hexo. By the time I get to work, I’ll probably only use my blog. The new blog will not only have technical articles, but also share life lessons. In CSDN’s case, it will mainly publish technical articles. So that’s it. I hope more people see it.