One of the biggest problems I see in the test automation space is an abundance of information on how to manipulate a browser, but a distinct lack of guidance or training that can guide an engineer toward writing valuable, maintainable tests. I would guess that one of the reasons for this is that it's just too difficult to convey all of the nuances of what makes a test suite sustainable - not to mention how to build it in such a way - in a collection of videos.
I train in a manner that produces engineers I would hire, that I would trust to tackle small-but-valuable projects as early as possible. The only way to achieve this level of competence in a relatively short amount of time is to ask questions as they arise, to engage with the information critically. There is a lot of philosophy at the heart of good automation, and I don't say that to put on airs - as engineers we need to constantly re-assess our approach and re-orient against our short and long-term objectives.
Remote courses allow the freedom for students to get the answers and context they need to make their own connections and grow quickly into their potential as invaluable architects of today's (and tomorrow's) technology. I am excited to kick off the new year with several remote courses, the names of which I will release this week. They will cover building healthy browser automation at a professional level, and how to write backend tests that are fast and maintainable.
In the meantime, please check out the video tutorials I've already posted, and let me know if there is something specific you would like to see out of the academy! If it is something I can speak on authoritatively I will add it, and if not, I may find someone who can. Enjoy the holidays!