For the last couple of days, I’ve felt my enthusiasm for sitting down at the keyboard each day, for the 30-minute Learning Golang sessions, waning.
It’s not that I don’t enjoy learning Go. Far from it. It’s that I feel that reading about one concept after another and not diving in to any real degree of depth to be rather pointless.
What’s more, it’s starting to remind me of my time in high school, which was quite a frustrating time. Back then, I learned about a lot of things. But since how I was taught the topics was, largely, devoid of any practical context, I forgot so many things soon afterwards. Without the required context, it was hard to appreciate why I was learning said topic, nor why I should commit it to memory. So, too, have these sessions started to become.
Given that, I’m going to take a bit of time out in the next 24 hours to figure out a new learning strategy. There’s nothing wrong with the Go Tour. It’s a decent, well-structured resource with copious links to lots of excellent information. It’s what it says on the tin: a tour.
However, now that I’ve been learning Golang for almost 2 weeks, I need to change tack and do what’s always worked for me: I need to apply what I’m learning, and want to learn. I need to use the knowledge for something meaningful.
Gladly, I do have something meaningful, which is the weather station app I’m porting from the PHP original. Actually, maybe I don’t need a day to think about a better direction to take. Perhaps that’s the new direction.
Are you learning Go? What’s your approach? Please share your it in the comments.
One other thing that’s been increasingly getting to me is that I feel, despite having been a developer for years, there are so many things that I just don’t know and struggle to grasp in a meaningful period of time. What’s more, it’s hard to grasp the requirements of the Go exercises at times and to complete them within a 30-minute time window.
Some days, most of what I’m doing is searching the net for how other people implemented a solution, for further information about a given feature, function, or library, and to troll through the code of a given function, method, or library. Basically, anything to help me have a greater sense of understanding about what I’m being asked to do.
Hey, it’s rewarding to learn and to see how others approached a situation. It’s just frustrating not to grasp concepts as quickly as I’d like to.
Anyway, that’s me for today. See you, next time!