Every time I write an article, I always don’t know what to write at the beginning. All right, I won’t write it this time.

Good luck

July will be one year after graduation. Well, how can I put it?

  1. I learned a lot
  2. It doesn’t feel like more and more

I feel more like I’m lucky,

Graduation to find a job, from Java -> go, so the biggest harvest of course is to learn to go. One of the lucky ones, after all, the company let me learn while writing (touch fish), but 3 weeks after coming to the company began to start the project development, to be honest, I did not know anything at that time, just stick to the head.

Written document

Write documents. That’s the first thing I did when I first joined the company.

It was researching a new CDC middleware: DeBezium. Describe your situation at that time:

  1. clickhouseI have no idea what it is. Column save? I have heard of it, but how do I know
  2. dockerIt was only known at the time, but it was not used further
  3. debeziumI have no idea what this is

Yeah, that’s the thing about not knowing anything. I completed my first job at the company: Building CDC synchronization process documents with Debezium.

At that time, I did not know how the team leader would comment on submitting the documents to the team leader.

Group leader: The document is well written. Go ahead and deploy this, do a demo, show you how it works.

I guess we made it through. But in retrospect, maybe that’s what made me less afraid of new technology. To summarize my exploration of this new middleware:

  1. docker-composeFirst a wordy frame up
  2. Single-machine mode is used
  3. Test it in the language most commonly used today
  4. Follow the website, try each step, observe each steplog output
  5. Lenovo previously learned technology, comparative study
  6. See if there are any official discussion groups, be open to asking for advice, ⚠ note the Art and Attitude of Asking questions

But most of all: get over yourself and try using documents + search engines to help you explore.

For fun, when researching Debezium, I also saw the official Gitter (you can search for it by yourself), in which the core developers will answer your questions, which can be said to be very patient. The developer also asks certain questions, specific to their own procedures, operation logs, errors, and their own guesses. It was asked with questions and ideas that I felt were better than some of the open source communities in China (case in point).

So I hope you will: ⚠ pay attention to the Art and Attitude of Asking questions

This was the beginning of my documentation. Later, I participated in writing go-Zero documents and sharing source code analysis articles.

Hard Wide, Direct Interplay: Go-Zero is a Web and RPC framework that integrates various engineering practices. The flexible design ensures the stability of the large concurrent server and has been fully tested in actual combat.

In fact, the beginning of the idea is very simple: is to feel that they write a source code analysis, since you want to see, naturally to clarify and tell you how the framework is designed. Yeah, that’s the idea.

Up to now, I write source code analysis of the original heart is still this.

To borrow the words of Teacher Luo Xiang: sometimes your success is not your success. You should thank those who have helped you. So I am very grateful to my CTO for giving me this platform and opportunity.

Writing articles and sharing and doing open source, the original idea was to give back to the community and help other developers like me.

entertaining

I have been in Juejin for several years, but I started to post on Juejin this year. The post is mainly source code parsing, and the overall reading and likes are not very many (in fact, very few, HHH).

That’s why I say I entertain myself. Later he simply ignore, because the estimate also few people see. But why write at all?

  1. See if we can white the perimeter of piao’s gold dig
  2. Learning notes

So my article is basically source code parsing, and it is estimated that the source code parsing class will be shared. It doesn’t matter whether or not people read it, the study notes will not be broken, if you can resonate in my article, that is very good.

There is a saying called: inadvertently willow willow shade

The company share

HHH, this is nothing to do. Thinking of their own learning mysql booklet before the process and read the source code notes made into PPT, share in the company. It is also like I can tell my colleagues, and he can gain from what I say, which shows that MY knowledge is almost in place (salute feynman learning method).

However, after sharing, I asked everyone’s response is: it’s too deep, too much code, can you give some previous synopsis and bring in. Later, CTO also suggested to me that I should introduce more scenes, explain less code, expand my thinking and explain less rules. People want to know how close it is to their work, not to know something for the sake of knowing it.

But also read the process of mysql source code to recognize the K boss. After communicating with him, I also communicated with him about the source code of mysql. This is also the first time in the network and source level players exchange, very excited to also give a lot of hints.

In the process of communicating with him, there is a sense of making friends with time. After all, it is only with constant precipitation that you can gain a deeper understanding of the code and even the entire system. (Also give big K a hard shot, his mysql article is very NB)

Itself source reading is a very long, even a bit of a thankless thing. Enjoy yourself and enjoy yourself.

Second half plan

  1. Continue togo-zeroThe source code to share
  2. Continue to completeThe Kafka source code project
  3. startClickhouse source code project
  4. k8sLearn about containers
  5. Learn more about storage…
  6. .

Anyway, there are so many more to learn, not to list… Keep rolling…

Hopefully you can (and probably can, 😂).

conclusion

Thank you, thank you, thank you.

There are so many people to thank, I won’t list…

That’s it. See you at the end of the year, 👋👋👋.

The nuggets years | 2021 theme activities I grow half of the campaign is under way on the road…