Using laravel’s author as an example, he came to the point when he already had clear understanding of what he needed, what was not enough for him. This knowledge is received through practice acquiring experience and often unavailable for learners.
@@MelkeyDev I didn't particularly like it. I think you are super knowledgeable on all things golang and I guess that is how I see you. Happy to see you grow and try out different things.
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.
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
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.
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.
I bought them like 2 weeks ago, and I almost finishing the first one. Love all the explanations, the comments in the code, the reason about what to use and why, etc.
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.
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.
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).
Hell yeah man, thanks for the insight. I totally agree with you, but I will say although the video-copy-style worked for you, my personal experience is that it didnt work for me. Thats why I said solve your own problem!
@@MelkeyDev Yeah yeah, love that approach, now that I realized that solve your own problem was the way I learned most of the languages I learned before, but for Go video-copy-style happened to be the effective way. Again, great video will definitely check the links you mentioned, also enjoyed style of the previous one! keep it up
@@MelkeyDev I think its a good idea if you dont have any problems you want to solve, you just find some one elses problem and solve it, having a "problem" that you come up with on your own doesnt mean you are going to be passionate about solving that specific thing, that is forcing it. sometimes its better to find something interesting that others have built and just try to build that yourself, its more important to build something interesting and fun than forcing you to figure out a problem to "solve" I tried that before I built a scheduler before and it was one of the most boring things I ever built..
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
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.
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.
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?
I often can't think of problems I have that would be solved by building things with code. I get that this is good advice and you see it said often but idk
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.
Some advice here would be to find some open source go tools your already using, and learn their code base. Build the project yourself and make tiny changes and you’ll get experience with more structured code bases.
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?".
![[FINALE] 💸ที่แท้พ่อเป็นผู้ถือหุ้นบริษัทพันล้าน เขากลับใจตอนนี้ก็สายไปแล้ว🙇🏻♂️#ละครคุณธรรม #short](http://i.ytimg.com/vi/yFwgjTFISUI/mqdefault.jpg)
I hope you all enjoy the video! Let me know - it means the world
great video, been postponing learning go for a few months but this type of content always comes in handy!
Using laravel’s author as an example, he came to the point when he already had clear understanding of what he needed, what was not enough for him. This knowledge is received through practice acquiring experience and often unavailable for learners.
1:49 - "All links will be in the description down below"
I'll pow the Like button when I see links, sir!
Just did it - thanks for the reminder!
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.
Can i have some copy? can't afford it right now
Wtf 62$ 😢
@@PITOApps I have the PDFs.
@@jigyansunanda Send it to me
@@PITOAppsit’s possible to find pdf versions of them across the web for free.
Content is hard man. You got it! Just keep going
Haha - are you saying this was a bad piece of content
@@MelkeyDev I didn't particularly like it. I think you are super knowledgeable on all things golang and I guess that is how I see you. Happy to see you grow and try out different things.
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.
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
Thank you Melkey!
Working on my go project!
Key point: “You have to have your goal”
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.
You're real in your perception man. Thanks for this honest video.
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.
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.
I bought them like 2 weeks ago, and I almost finishing the first one. Love all the explanations, the comments in the code, the reason about what to use and why, etc.
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.
Great advice Melkey. I really want to learn go in the future!
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.
enums from rust is what really missing in Golang
@@tsolanoff yep.. whilst you can switch on consts with a type/iota & achieve the same result, it's not very pragmatic.. at all.
Thanks for the shout out to LGWT
oh - yeah dude great stuff. Thanks for what you put together
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 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).
Hell yeah man, thanks for the insight. I totally agree with you, but I will say although the video-copy-style worked for you, my personal experience is that it didnt work for me. Thats why I said solve your own problem!
@@MelkeyDev Yeah yeah, love that approach, now that I realized that solve your own problem was the way I learned most of the languages I learned before, but for Go video-copy-style happened to be the effective way. Again, great video will definitely check the links you mentioned, also enjoyed style of the previous one! keep it up
@@MelkeyDev I think its a good idea if you dont have any problems you want to solve, you just find some one elses problem and solve it, having a "problem" that you come up with on your own doesnt mean you are going to be passionate about solving that specific thing, that is forcing it. sometimes its better to find something interesting that others have built and just try to build that yourself, its more important to build something interesting and fun than forcing you to figure out a problem to "solve" I tried that before I built a scheduler before and it was one of the most boring things I ever built..
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
Hell yeah
Please focus on just making projects instead of only studying
noted! thanks for the suggestion
I’ve been doing let’s go and it is amazing.
Contributing to open source projects can also be a good way to learn a language and proof of work!
i am currently using go lang to build an AI project as a beginner
Still binge watching your excellent content. Jonathan Hall recommends "Learning Go" by Jon Bodner
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.
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.
Im on this level rn, I'm a beginner and have no idea what to build, especially something I could put on github and CV, do u have any sugestions?
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?
I often can't think of problems I have that would be solved by building things with code. I get that this is good advice and you see it said often but idk
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.
Some advice here would be to find some open source go tools your already using, and learn their code base. Build the project yourself and make tiny changes and you’ll get experience with more structured code bases.
What happened the moustache?
It escaped.
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.
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?".
Shit. Build something for no reason, no real usecase is a waste of time. It teaches you nothing.
No using foul language is NEVER good advice - period.
Wait when did i use foul language
i don't get it, he never once mentioned v*code
I think he's referring to the guy who said "build shit", not that deep tho. @MelkeyDev
My problem is that I don't have problems
lol