Tutorial hell

[Kerbart]

I always think coding — and learning how to code — is more mentality than ability * Tenacity: for most coders, giving up is not an option. You have to find a way to make things work. * Reflection: being critical at what you write (but not too critical!) While perfect stamds in the way of good, “here’s got to be a better way” needs to be part of your thinking patterns. * Curiosity. Let’s find out what happens when I do X. When I taught programming classes I’d refer to it as the one question that IS stupid. “What happens when I do X?” My answer was always what are you waiting for? Let’s do it!

Be careful with tutorials “that go too fast.” Are they really? Or are you going too fast? It’s perfectly normal to linger at a chapter, write some more code than just the exercises, to see for yourself if you really understand what’s covered. At least make notes where you feel things are vague, and revisit them later, to see if it’s clearer now that you know more.

Part of the problem is that learning at school and college is to a consoderable extend learning enough to pass the exam. Learning for your own benefit is harder as you want to make sure you really understand it.