<p>I'm new to learning code. I chose golang because I'm planning on going to cryptocurrencies business like writing smart contracts hyperledger fabric. I'm having a hard time learning coding. I'm not getting it, it's not coming to me. How should I approach it to fully understand it. I'm dying to learn it, but it frustrates me that it's not coming to me. Can you guys help me out please I'm desperate.</p>
<hr/>**评论：**<br/><br/>shovelpost: <pre><p>It's hard to help without knowing what exactly is the problem. Have you tried the official <a href="https://tour.golang.org/welcome/1" rel="nofollow">Go tour</a> and <a href="https://golang.org/doc/effective_go.html" rel="nofollow">docs</a>? Do you find them hard? Have you tried a <a href="http://www.gopl.io/" rel="nofollow">book</a>? What exactly is that you do not get? </p>
<p>If you are really having a hard time then you should start with the basics before you go about "smart contracts hyperledger fabric".</p></pre>itsmontoya: <pre><p>The best thing is just starting to code. Give yourself small projects for fun and you will learn as you try more experiments. </p></pre>gentleman_tech: <pre><p>In my experience from teaching a few people to code, it takes a good six months of daily practice to finally feel like "OK, I got this, I can do this".</p>
<p>There's a spot about 1-2 months in where everyone feels like they're never going to understand this, and the temptation to give up is huge.</p>
<p>To be able to code vaguely competently, you need to have about a dozen "things" understood. You start by learning one, and that's OK, and then you hit another, and you cope. By the time you get to your fifth new thing to learn and cope with, you're beginning to get disheartened. By the time you hit your tenth "what? I have to know about this, too?" thing then you feel like you'll never get it. But fairly soon after that, you stop hitting new things and you get to master the ones you've already met.</p>
<p>In other words: don't despair, it does get easier. You can do this :)</p>
<p>Don't worry about learning the syntax for each command. Every programmer has to google the syntax sometimes. The standard library is really well documented because we all forget how the bloody things work all the time.</p>
<p>Understand how pointers work, it's probably the single hardest thing for newbies to get their heads around, but once you grok it you'll wonder why you ever thought it was hard. Then you can face channels with some vague confidence ;)</p>
<p>good luck :)</p></pre>Diddyshyne120: <pre><p>I read book and watched a lot of videos. Just not making sense to me yet. Maybe there's a better way to approach coding. Idk</p></pre>shovelpost: <pre><p>The best way to approach coding is to code.</p></pre>dtoebe: <pre><p>Coding is hard.. especially when you're learning your first language. A lot of things don't make sense at first. First you do "hello world" and maybe a simple server, but after that you'll feel like your banging your head against the wall. That's the fact of life learning development.</p>
<p>Just keep building things, post it on GitHub, and post that to Reddit. Then others can critique your work. When you hear go is an easy language to learn, that's coming from the perspective of existing developers.</p>
<p>When you try to build projects, create a to-do list of the different parts you want it to do. Then figure out how to do each part.</p>
<p>Finally crypto currency can be hard. Start with other projects, maybe create a file uploader returning the file meta data. Then try to create a multiple file uploader, again returning the metadata with file size. Just some ideas.</p>
<p>And know there is a reason software developers are some of the highest payed jobs... Because software development is friggin hard. Those with a passion for it will persevere through the banging your head against a wall part and learn to create great software.</p></pre>carsncode: <pre><p>And it's worth mentioning that the banging-your-head-against-the-wall part <em>never stops</em>. It's just that the better you get at development, the more you accomplish <em>in between</em> periods of cursing.</p></pre>dtoebe: <pre><p>Oh and that feeling of accomplishment, even after years old development, is amazing! Makes it all worth it.</p></pre>AngryGoNerd: <pre><p>Heres a list of golang books:
<a href="https://github.com/dariubs/GoBooks" rel="nofollow">https://github.com/dariubs/GoBooks</a></p>
<p>I really like An Introduction to Programming in Go along with other free starter books you can also get help from the Go Forum: <a href="https://forum.golangbridge.org/" rel="nofollow">https://forum.golangbridge.org/</a> and on slack</p>
<p><a href="https://invite.slack.golangbridge.org/" rel="nofollow">https://invite.slack.golangbridge.org/</a></p></pre>DigitalCthulhu: <pre><p>As shovelpost said, you should define what exactly is the problem.</p></pre>darkmagician2: <pre><p>If you want to learn to code check this out <a href="https://www.udacity.com/course/intro-to-programming-nanodegree--nd000" rel="nofollow">https://www.udacity.com/course/intro-to-programming-nanodegree--nd000</a></p></pre>SamJTWIV: <pre><p>You might have made a mistake jumping straight into Go. Its not a more difficult language but there aren't many truly beginner resources. Its much easer to learn a different language and then transfer to go. I would recommend C. CS50 on EdX is a good starting point for code and C.</p>
<p>Edit: Every resource I have seen for Go from the "Go Tour" to "An Introduction to Programming In Go" assume some prior knowledge or experience with programming.</p>
<p>Edit: I believe this is a result of the fact that Go has been mainly picked up and practiced by talented and experienced programmers. Who don't need the level of help a true beginner does and are less likely to notice small assumptions that they innately understand but that can drive a beginner crazy.</p>
<p>Edit: This is not to say you can't start with Go just that it may be more work starting out but on the bright side at the end you may be a better problem solver with a deeper understanding of the language.</p></pre>PsyWolf: <pre><p>Yeah, I have noticed that most resources for go assume some basic level of programming knowledge. A quick Google search did turn this up though. No idea how good it is, but it looks promising <a href="https://www.udemy.com/learn-how-to-code/" rel="nofollow">https://www.udemy.com/learn-how-to-code/</a></p></pre>SamJTWIV: <pre><p>That does look promising though the amount of hype in the description does raise some flags with me.</p></pre>SamJTWIV: <pre><p>I also mostly agree with what dtoebe said. Except that I think the basics of programming aren't that hard if you pick the right resources but the moment you go past the basics is like stepping off a cliff. I would also recommend trying to minimize how many different things you try to learn at once. It is very easy to get info overload and not learn something well enough because you are distracted of overwhelmed by the other stuff you are learning.</p></pre>
