I wouldn't say reading a typical book is a waste of time, but as a rule of thumb that might be worth saying. Action (e.g. practice, doing, etc..) is the gold st

I wouldn't say reading a typical book is a waste of time, but as a rule of thumb that might be worth saying. Action (e.g. practice, doing, etc..) is the gold standard. When you do actions, you read scattered tutorials, explanations of exception stacks, and multiple API documentation. If your non actions exceed 50% of your actions, then you are probably reading into one ear straight out the other. A good computer science book reading can be a real asset to someone who's looking to improve their work.