What is the BEST Way to Study Golang? (and get hired...) 

I hope you all enjoy the video! Let me know - it means the world

1:49 - "All links will be in the description down below" I'll pow the Like button when I see links, sir!

I heard the 100 Go Mistakes response is a must read. It's such a head question to answer because everyone learns different. But I think building projects is the best. Start small, temperature converter, calculator, etc... then work up to web server and toy database.

Another great Text Book to learn Go (if you already know other programming languages) is "Learning Go - An idiomatic approach to real world go programming" by Jon Bodner published by O'Reilly, helped me a lot, along with 100 mistakes and the other resources mentioned here.

Let’s Go and Let’s go Further are truly insane resources. The chapter on rolling auth was the clearest example I could find anywhere.

I think one of the ways to learn a concept is to create your own problem that using the thing you want to get good at as the solution sort of like a "coding challange" that you come up. I don't think you have to build a "product-like" project although its great, you can follow a go video of someone doing "xyz-from scratch" and delete and re-do the some parts over and over again. At the end it is like learning an instrument, programmers doesn't really get smarter overtime, just have more muscle memory. I personally learned go mostly from teej's "Learn By Building: LSP" video, i just copied and deleted over and over again (every 30 minutes of progress in the video ), until i memorize the code, but while memorizing the code line by line, you also memorize the intention of each line coming after another. "solve your problems" is a really good point in the video, for a project idea, creating a "tool" can be good way to start (maybe while learning/using charm.sh).

For me, what's worked was starting building a ORM package with the API that i like, toked me 6 months, i am almost finishing a first version and i am very proud of my self

Content is hard man. You got it! Just keep going

I just start with the basics of the language and see how things can be done, and as I do that and even produce what has already been produced, I get new ideas and start building my own things.

You're real in your perception man. Thanks for this honest video.

I just bought Let’s Go and Let’s Go Further after watching this and they look fantastic. I can’t wait to start working through them.

One of the trickiest parts of beginner go stuff is a lot of it is focused on web dev. I'm more on the game dev and syatems side of things.

I would really really like to see a top 5 things you dislike about Go.. a real talk about what you have had elsewhere, but is missing in Go or you wish would be better in Go... I'm trying to get into Go and I know you aren't a fan of TS, but it is quite a leap & there are things I know I miss or wish were different myself.

Recently I built an text-search engine with go, it was pretty shit, but thats okay, it does not need to be good the first time you build, work on something else for a while and then get back and iterate over it

Still binge watching your excellent content. Jonathan Hall recommends "Learning Go" by Jon Bodner

i am currently using go lang to build an AI project as a beginner

Great advice Melkey. I really want to learn go in the future!

Contributing to open source projects can also be a good way to learn a language and proof of work!

I’ve been doing let’s go and it is amazing.

Great answer! Also, an awful answer. If you have a problem at hand that you are passionate to solve, go ahead an solve it! Yet I still remember time when I was a beginner, and I had no real problem I wanted to solve. I wanted to So I googled some examples from other people and a couple grabbed my attention. If someone asks you for ideas, sure, tell them that the best way is their own ideas, also be ready to give some concrete examples that many beginners sorely need. One fun idea is to replicate command line utilities that you use, like grep or wget.

Thanks for the shout out to LGWT

Its always best in my experience to have something you want to do and figure/search it out as you go. Maybe you're frustrated by the lack of a handy web based tool to share files between you and your friends if you dont want to use a cloud service or you want to interact with some public webservice api like Spotify or something. The classicmake a to-do app stuff... just never does it for me.

I am doing my first golang project and I'm trying to get access to user email inboxes using microsoft graph api. Would you have any idea on how to start that?

What if the solution to my problem is already availiable but I just want it according to my requirements. is it still worth it to build that? for Example, I really loved the Code Snippet Feature of Pieces but it's too heavy for my laptop and it has all the AI features which makes it more heavy.

My problem with learning go is i can build shit but i cant validate or should i say dont know if what i build is optimized and uses idiomatic go.

I never really got this "solve a problem you have" What if I dont have any problems that I want to solve? what do I build then ?

Coding, coding, coding and after you will be master.

What happened the moustache?

ok so zig right...

I gonna be cruelly honest. Most people who have asked the similar questions in real life + internet, just want to get a good job with 6fig salary by picking up a "hot" language. They have no interests on solving any problems. That's why they keep asking what to build (so I can get a job within half a year). And that's it. I slowly refuse to answer these questions, instead, tell them pick whatever as long as you can get a programing job. 10/10 is what they are looking for. People who truly want to learn specific language is always asking something like "I try to build X with lang Y, it seems like the language doesn't reflect what people are excited about it. I got lots of troubles, what should I do?".

Please focus on just making projects instead of only studying

No using foul language is NEVER good advice - period.