Not sure where you are in your programming career, but avoid the pitfall of not programming by only reading about programming, as you might trick your brain into believing that you are working on it. As with any skill, hours spent doing it matter. A lot.
I'd add to that, somewhat conversely, to not rely on StackExchange and Google, as copy/paste coding is how not to understand programming (rather, it makes people believe that they are better at it than they are).
Well, you will need to become self-correcting. Both books and experience can help with that. Making mistakes and having to rework it all will change how you do things in the future, while books might aid in giving you e.g a theoretical understanding of quality properties and common patterns. That knowledge still needs to translate to practice. Just don't skip the exercises.
Is that a saw?
+1
I found "better" ways by profiling code (analize which parts are slow, and then rewrite parts as optimal as possible to get faster speed). Then I found that there is a delicate balance between readable (for co-workers) and fast...
Yes, its power mitre saw, a type of circular saw I believe.
I don't know why but I look at your favicon and think you're an old man. When you said your parent's I though 'crap they must be old!'
