Learning Golang. Day 1

Learning Golang. Day 1

For the longest time, I’ve been meaning to learn another software development language in-depth, in addition to my primary development language, PHP. I’ve decided that the language is Go.

There’s a lot to learn. So, to not get overwhelmed and to make it as simple as possible, every weekday, I’m setting aside 30 minutes to study. Then, after the half hour is up, I’ll be sharing something about what I learned here on the blog, as well as on LinkedIn and Twitter.

What Did I Learn Today?

Today, I started the Go Tour to reacquaint myself with the core of the language. I say "reacquaint" as I’ve started to learn Go a few times over the last several years, but never stuck with it.

The tour is a very clear and well-structured way of understanding Go’s foundations. It helps you learn in small, bite-size chunks, which is excellent when you’re time-boxing as I am.

In addition to starting the Tour, I made a small refactor to my test-bed Go application to avoid it initialising a database connection on every request to the default route. It now initialises the database connection once, on application startup.

After day one, while I appreciate that there is still so much to learn, and that I have a long road in front of me – and that some of the syntax is a little new and confusing to me – I think it’s going to be a very fun and educational journey.

See you next time!

You might also be interested in these tutorials too...

Learning Golang. Day 2
Tue, May 10, 2022

Learning Golang. Day 2

Today was a slightly slower day for learning Go than was yesterday. However, I learned about flow control statements, and defer, panic, and recover.

Want more tutorials like this?

If so, enter your email address in the field below and click subscribe.

You can unsubscribe at any time by clicking the link in the footer of the emails you'll receive. Here's my privacy policy, if you'd like to know more. I use Mailchimp to send emails. You can learn more about their privacy practices here.

Join the discussion

comments powered by Disqus