“Live up to the time, the creation of non-stop, this article is participating in 2021 year-end summary essay competition”

I was wondering if the Nuggets would have an annual payepage-like summary of all the articles posted this year. Then the Nuggets came up with this activity, so I will use this essay activity to make a summary of my 2021.

My year with the Nuggets

I met the nuggets

The first time I heard about the Nuggets was in February when a friend recommended it to me, saying it had a lively community.

I joined the Nuggets on February 22 of this year…

After registering, diving for less than half a year without doing anything (T_T)

First blog

One day wrote an algorithm, with several methods, wrote a problem solution in the force buckle, so I whim, the problem solution content to dig gold, this is my first blog: several methods of daily temperature.

At the time, he posted a circle of friends, which was also a diversion for the Nuggets.

First time to be pushed to the front page

Not two days later, I wrote a second article, which was also an algorithm solution: matrix minimum path sum of progressive optimization, this time unexpectedly received nuggets pushed to the home page of the news, which made me very flattered!

A little excited, posted a friend moment…

Got the nuggets award

In October, I participated in a performance optimization campaign, which produced a blog post: Gunicorn vs Flask’s Own Server: Performance testing, and finally won a lucky prize.

The prize is a Bytedance battery.

Of course I’m going to post it on wechat again

Actually, the nuggets staff asked me to participate, probably because my writing is better, haha

The most recognized blog

To be honest, I don’t have any blog that I’m particularly recognized for. My blog only has 11 likes at most, and one of them is my own. However, the two posts were relatively well received: Java parameter passing and Java Concurrency Learning Notes: ReentrantLock.

The most time consuming blog

ReentrantReadWriteLock, “TreadWritelock” Java thread pool source code: task execution, worker management. Which belongs to the source code parsing classes, Java, speaking, reading and writing lock and the thread pool the source code itself can be difficult, I understand the two source each spent five words of writing each and spent three or four days, the two have spent 10 days to make (not 24 hours a day, that probably spend three or four hours a day), but the last response.

Nuggets more on that

Not counting this one, I have written a total of 24 blog posts so far. Each blog has been read about 300 times and collected nearly once. I have a cursory look, out of 24 articles, 12 are source code analysis, and then algorithms, practice records and insights on small knowledge, 4 each, roughly this distribution. Then 22 of the 24 blogs were pushed to the home page, indicating that the basic quality of my blog is still guaranteed O (￣▽￣)ブ ブ.

This year’s study situation

I have always been interested in back-end development, and my study basically follows the back-end route.

Brush the topic

Since April this year, I have written 283 posts, almost one a day. This part of myself has been relatively nervous, brush is also very slow, many questions have done several methods. But it is estimated to do a lot of not.

Reading a book

I have read some technical books on and off this year. Here is a summary:

Java

  • “Java Core Technology Volume I”, read once, part of the content read several times; “Java Core Technology volume ii”, read the flow, IO, files, network programming that several chapters, this knowledge is not too familiar.
  • “The Beauty of Java Concurrent Programming”, basically finished reading, while reading while knocking code, feel good book; “The Art of Concurrent Programming in Java”, read the first two chapters, feel that the writing is not very good, chapter arrangement is not reasonable, so I stopped reading (personal opinion, do not like it).
  • “Understanding the Java Virtual Machine”, read it before class loading, did the experiment with memory allocation and GC, and wrote a blog: JVM Practices: Memory allocation and GC, very well written.

MySQL

I mainly read chapters 1,4,5,6 of “MySQL must know, must know” and “high performance MySQL”. The former is a pamphlet, not much to say, but High Performance MySQL is a really good book.

Redis

After reading the book “Redis design and Implementation”, a very good book, after reading the Redis underlying data structure should be no problem; I also read the book Redis Deep Adventure, about 60 or 70 percent, which introduces some applications of Redis. Personally, I think these two books can be read together, so I have a better understanding of Redis.

Algorithms and data structures

I read the first two chapters of the Orange Book algorithm, but I didn’t read the rest because I was busy with other things. This writing is also simple, simple.

architecture

This feeling is eye-opening, I read teacher Li Zhihui’s “Technical Architecture of Large Websites”, about half of it, the book is also quite good.

Design patterns

First, I read the highly praised “Head First Design Mode”, but I felt that it was written in general. When I saw the chapter of factory, I did not understand it very much. The example it cited was an example of making bread, but I did not understand it very well, maybe I was not good enough.

Later, I went to douban to search for design patterns, and accidentally found a very unpopular book: “The Art of Design Patterns”, written by Teacher Liu Wei, said to be the teaching material of Tsinghua University, I feel this is written very well, at least three factories told me clearly. I’ve read the first eight chapters of the book so far.

I feel like a lot of content is just after I read it, I forget it in a week.

The nuggets pamphlets

I mainly read two small volumes, “In-depth Understanding of RPC” on the front of the theory part, the back of the actual practice involved to write code did not read; “Hello, distributed lock” in front of the Zookeeper have seen, the front is mainly with Redis to do distributed lock, this free I practice, write a blog.

Outlook 2022,

Blog plan

2022 is expected to be busy, the frequency of more posts is likely to be 1 or 2 a month, the content should be more practical, the source code parsing class is too time.

A tough 2022

In 2022, I will have to find a summer internship, autumn recruitment and mid-term defense after graduation, which is expected to be a very difficult year.

For me, no matter the road of technology (back-end technology is extensive and profound, and I only know 1/10,000 of it), or the road of life (looking for a job and finishing design), it will not be too smooth. I hope I can overcome the difficulties and have a good result.

I see a long way to go, I will search up and down, I hope I can go a little further on the road of technology.