3 ms·
Once you've got an "in" into knowledge work (particularly finance or engineering), you can use large portions of your day job for learning things. Basically 10
by nostrademons 8y ago
Once you've got an "in" into knowledge work (particularly finance or engineering), you can use large portions of your day job for learning things. Basically 100% of my job (startup founder) consists of learning new things, as did about 80% of my previous job (Google search engineer), as did nearly 100% of the job before that (startup founder). I did have to do some grunt work at my first couple of junior software engineering positions, but still managed to save 40-50% of my time on the job for learning new stuff.
I learned ElasticSearch for my current startup, for example, but I didn't deliberately set out to learn ElasticSearch. Rather, I set out to index all the forum sites on the Internet, and it was the best tool available for that, so I just learned enough of it to go build my index. How much time did it take? Probably a lot more than 30 hours, and I still wouldn't say I really "know" ElasticSearch, but I know enough that I can run load a big corpus in, run search queries, and get useful data back out. That's pretty much all you can expect given that ElasticSearch is a moving target - hell, 5.0 had barely come out when I started learning it and it's on 6.5 now.
There are 2000 hours in a typical work-year, and 8760 in a calendar year. That's a lot of time. 30 hours is a drop in the bucket for it - 10 hours over 3 weeks will get you there. I'd just give up on learning everything (you will never succeed in that, new knowledge is being generated faster than you can learn it) and focus on continually learning within domains that you care about.