@ParanoidxProd
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.
@cdvillard
1:49 - "All links will be in the description down below" I'll pow the Like button when I see links, sir!
@edgarsilvax
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.
@laurosantana1418
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
@MrJannieboy
Content is hard man. You got it! Just keep going
@jakajhah-0
Please focus on just making projects instead of only studying
@kevincodes674
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.
@SvarturVetur
100 Go Mistakes is a great secondary book. With the golang website in mind, the faq, you want to take notes on the finer details. I made a condensed, organized checklist. Built a performance/debugging/testing folder in my Obsidian notes. Basically, the dark arts of good coding, info on how interpreters and compilers really work, and what fails and why.
@kayjeeouss
Great video! I have some of those resources lined up, and I can definitely relate to the advice, re: building something that’s meaningful to you. I’ve failed miserably at trying to get started on other projects that seemed like they might make a good addition to the SWE portfolio, so I’m instead going to focus on one that’s probably way more complex than I should be tackling right now, but that I’ll be more motivated to continue building on and refining over the coming months, after I’ve built the solid foundation in Go.
@selflearner-ai-era
You're real in your perception man. Thanks for this honest video.
@LengCPP
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.
@iwantfrens5804
Great advice Melkey. I really want to learn go in the future!
@MichaelVash7886
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.
@Whiterqbbit
Knowing that to build is the hardest part. Most of my "problems" can be solved in bash, I don't want to be a programmer but I want to know how to program if that makes sense. I am a cybersecurity student, but building things is super interesting to me, one day I would like to solve bigger problems. As for learning, I am looking forward to the Advent of code, going to use C or GO since those are the 2 languages I have been working on the past few months.
@lucaspinheiro7754
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
@rgcottrell
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.
@everyhandletaken
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.
@kaandesu4881
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).
@anshumansahoo256
Contributing to open source projects can also be a good way to learn a language and proof of work!
@MelkeyDev