After trying various things over the last few years, I now almost entirely ignore video courses, instructor led MooCs, books spanning several hundreds of pages etc.
I mostly focus on things which are directly related to my job (which happens to be closely aligned with my interests) and try to familiarize myself with the stack as deeply as possible.
For instance, if you are a web developer, once you are productive enough your language/framework of choice you can use that as a reference point to expand familiarity with multiple facets of your technology stack - eg. the communication layer (HPBN is an excellent resource), client side performance tuning (Google developer site is an awesome resource), utilities for monitoring and benchmarking the server side aspects, deployment solutions, distributed job queues etc.
Reading official documentation, technical manuals and writing actual code is simply much more time efficient than courses and tutorials (not that they don't serve a purpose) and keeping the learning track aligned with a singular primary role (or a primary prospective job profile) ensures that you keep getting the benefits out of this at a day to day level which (atleast for me) significantly helps in staying motivated.