As a couple of others have noted, there is no reason to posit a false dichotomy - that one must use either Kahn Academy (or similar) or a "live" teacher. Short lessons like Kahn does are useful to review concepts/unit operations where a student is rusty. My wife teaches physics, statistics, and calculus at a small high school and is an adjunct at a local community college, teaching the CC classes in the high school. The best bang for the buck for college credits around. Anyway, her biggest complaint is that too many of her students have been coddled in lower level classes and have either never mastered the pre-requisites or simply not retained them. Kahn's videos are one of many helpful resources for such students. The goal is to transform students into self-directed, life-long learners. This is really the only path to success, because the half-life to obsolescence of any technical course of study is so short.
Prof. Jean-Claude Bradly at Drexel discovered that students actually preferred pod/vodcasts of lectures (they could pause and watch on their schedule) and it freed up class time to work problems and answer questions. I see Kahn Academy videos in this same light. Are they perfect? No. can they be improved? Yes. Will polite, constructive criticism be better received than snarky comments? Absolutely! In this regard, the cliche "everything i needed to know, i learned in kindergarten" has some merit - things are a lot better when everybody is polite and plays nice in the sandbox.
I detest the modern versions of Office. Word 5 was a productive tool - versions after that were increasingly bloatware; Office 2010 was the last straw. I spent the last year transitioning to LaTeX. I have templates for technical reports, presentations, and reports of analysis (I specialize in microscopy and image analysis.) The combination of R, Sweave, and LaTeX, and shell scripts or batch files makes many projects very fast to reproduce when new data is added. This tool chain works quite well with git for version control - much better than the Microsoft "track changes." Microsoft keep breaking VBA to the point I will not use it for anything new.
The best part that I have found as a scientist is that I can create a directory hierarchy for a project, keep the source code and report under version control with git and have all the needed data in the appropriate place in the path. When the project is done, i do one final build of the analysis/report as a quality check and then use tar/gzip to make a compendium for archiving. When I need to reproduce an analysis, months later - everything is there. This has improved the quality of my work significantly compared to when there was a lot of point/click/copy/paste involved. it is also especially helpful in the middle of a project when I want to try a "what if" scenario or if a client wants to fine tune the sample set - or tosses in "just one more" before a tight deadline. Really reduced the number of "Mylanta moments" for me.
The world is coming to an end--save your buffers!