3 ms·
A common problem I'm having with coding tutorials is the tendency to copy paste example code and gain only a superficial understanding. My version "works" but a
by cornholio 9y ago
A common problem I'm having with coding tutorials is the tendency to copy paste example code and gain only a superficial understanding. My version "works" but a month later I won't be able to recreate it from scratch.
Your test-driven approach lends itself to hands-on exercises where you introduce the pre-written test cases, explain the new concepts on generic examples, and the person completing the tutorial needs to write the code that gets the test case to pass (or maybe expand a partial solution from you).
Once you struggled with the compiler errors, the trial and failure, the syntax, etc. and passed the tests you will gain operational knowledge that will last a lifetime.
Also, a chapter zero could be made available for the absolute beginners, detailing how to assemble a free Go environment, for example VS Code + go plugin + golang package + Git SCM + delve debugger. That should get most people running in 10 minutes with a very rich and productive environment.
- fwip 9y agohttp://exercism.io http://exercism.io has test-driven learning tracks for a whole bunch of languages. I highly recommend it for anyone looking to gain basic proficiency in a language in a few hours.
- quii 9y agoA chapter zero is a great idea, just less exciting to write so the current one is what got priority ;) I echo your sentiments, in the README.md in the root i talk about how writing tests is how I generally try and solidify knowledge. I watched a few videos from a Coursera course called "learning how to learn" (or something like that) and it talked about how making your own analogies and examples helps you memorise stuff. To me, this style of learning works along those lines.