[alejo]

Back in the day when I started coding in Go, I basically did the Go Tour on the official website, and watched some of videos.

I paid close attention to learning how to write idiomatic Go. I also read a bunch of code from the std lib.

Then after a few days I jumped right into coding. I started with a simple CLI to do some heave lifting in our Ci/CD pipelines (for work) and then I also started coding some web apps for my perdonal use.

After this, I started designing and building a few systems that were needed internally at my workplace and I also started training other folks in Go.

That was back in 2017. Today we have several big systems running in production and a strong team of engineers all working and enjoying Go :)

I would recommend to anyone a similar path:

- learn the basics

- build and release things

- teach others who may be interested

At that time my background was as software engineer (~17 years) mainly writing Java and some Javascript