My plan for being hired as a Go developer. In 2017

I know it is 2020. But I am reading the notes of the plan I made in 2017.

I know this is 2020, but when I was doing spring cleaning on my computer, I stumbled upon the 2017 mind map.

According to these instructions,20162017I have a goal:Become an employee. Find a stable, high-paying job instead of becoming a contractor, and work on countless side projects that never seem to develop into a profitable business.

I want to be hired by a company as a Go developer. Although he is a skilled PHP/JavaScript developer, and has no experience in using Go except for personal projects. However, I am a little tired of using the same stack and want to try something new.

Today, this idea sounds crazy to me because

1) I have never worked as an employee 2) At that time, I had been a freelancer/contractor for nearly 10 years (now more than 13 years) 3) I can’t believe I don’t work on my own projects

However, you may be very interested to see how I plan to develop from an ignorant Go language into a Go language development company in a few months.

I bought the authoritative book on Go: the Go programming language written by Donovan and Kernighan. Yes, it is the same as Kernighan in the famous "The C Programming Language K&R" book.

By the way, this book is incredible and worth recommending.

I read each chapter diligently for a month. Every day I learn new things and summarize my notes in a blog post.

I publish blog posts every day, sometimes even more than one.

I am engaged in algorithm work and have worked on some small projects on those algorithm platforms.

I started my own project. this is a good idea. I still think it is. This is a web application that interacts with GitHub, designed to help visualize the progress of the project over time.

I built it using Go and it was a great learning process.

When you are working on a project that interests you, learning things is much easier than learning things, because you are asked to do so like in school.

I read other people's code on GitHub. I spent a few days on the Go forum, trying to understand what people were writing.

I looked at popular projects built with Go (Docker, Kubernetes, etc.).

I follow every major "influencer" in the Go world, and every famous Twitter account on the topic.

I subscribed to all the Go mailing lists I can find.

I subscribe to every podcast on Go and all the YouTube channels I can find.

In short, I live and breathe Go all day.

From early morning to late night.

This is a good plan.

It's kind of solved, because I'm in the late stage during several interviews.

It didn't work, which means I was not hired by the employer for one reason: I really didn't want to be an employee.

Freedom and independence and the motivation to build your own business is too strong, And my conversion from freelance/contractor/independent to employee failed.

In retrospect, I am happy about it.

In the long run, maybe I will not be an employee.

I still know Go, and I'm really happy that I spent all the time and energy to learn it.

Of course, this makes me a better developer.

More experimental tutorials: