Observation: I see that you do 26 exercises before doing anything with pointers.<p>I often wonder if one of the reasons Go is more "simple" or approachable to some is because you can, to a large extent, ignore pointers and interfaces and "just write that weird little * or & in some places" and get away with it. Whereas, I believe in other languages, this is much less possible (e.g. in Java or Rust you need to learn about less "just logic" traits of the language earlier on (class inheritance, generics or Options, borrow checking, etc.)<p>I'm not saying the above is a good thing, but I often wonder if there aren't ways to make this more of an incremental learning curve in other languages in a similar way that you can largely ignore pointers in Go for a long time and be productive without understanding them. What would a similar incremental learning curve for generics be?
This looks pretty cool. When I was learning Go a long time ago, I used a site called Gophercises and found it really helped me understand the language better.
I've compiled a few interesting quizzes about Go's slices: <a href="https://medium.com/@gotzmann/so-you-think-you-know-go-c5164b0d0511" rel="nofollow">https://medium.com/@gotzmann/so-you-think-you-know-go-c5164b...</a>
If you're interested in interactive language learning exercises, then try codewars(<a href="https://www.codewars.com" rel="nofollow">https://www.codewars.com</a>)