This is a great point. I enjoy reading about various languages and paradigms even if I don't have a particular problem I need to solve, just to see what's out t

This is a great point. I enjoy reading about various languages and paradigms even if I don't have a particular problem I need to solve, just to see what's out there. But without a concrete problem I'm actually trying to solve, I never go very far into actually applying these techniques at the time I learn about them. Similarly, I've never found tutorial-style docs helpful, at least not the type where they walk you through solving some toy problem. But if I'm actually trying to solve something, I'll use the tutorial examples to crib from while implementing my actual solution. I've read about Goroutines and channels, but never implemented anything with them (my experience with go consists of writing a BF interpreyer). But it looks like I'm going to have to work with a library in C++ that uses the same principles, and having that vague background knowledge helps a great deal. Interestingly, I personally find that if there's an external motivator for solving these toy problems (for example, in a class or job interview situation), I don't have this same motivation difficulty. But if it's purely for my own amusement, I'm way too lazy.