|
I'm pretty sure this is a generational thing as well.
Younger engineers are used to just "google it", or "watch a youtube video" and you are suddenly an expert in whatever you want. Watch a video on building a cabin in the woods, and you have it all figured out. Older generations are used to studying the field, and learning about the capabilities of the language, environment, etc. It comes down to this. A language is a tool. Learn your tools well. Become a master craftsman in the tool, and then you will be able to craft amazing things. If you just learn "enough" to get by for now, i.e. "On Demand Learning", then you won't even be aware if some particular capability of your toolset exists, because, you can't "learn it" if you don't know about it. Eventually, you will "see some code" that does something, and suddenly you will be prompted to "go learn it", but your understanding will always be limited. I still take time to read through books (Oreilly, packt, etc) or do some langauge reviews to understand what my tools can do, and do my best to get a good feel for the capabilities. As I approach a particular problem, I usually need to do some more review, more "on demand" learning to deal with the specifics of the problem. I guess, my approach is a bit of both. General coverage so I "know" my tools capabilities, and then on-demand for the details when I'm trying to use a particular capability for the first or 2nd time. |