Everyone should check out these lessons:
Journey into cryptography: https://www.khanacademy.org/computing/computer-science/crypt...
Journey into information theory: https://www.khanacademy.org/computing/computer-science/infor...
I use it for everything including X rated content from adult sites
It extracts the audio then "huff-duffs" it; i.e., puts it into an RSS feed you can consume with your podcatcher of choice. Check it out, it's great.
Here's the code if you're curious:
https://github.com/alangpierce/Audicademy
And there's a feature-incomplete web version that lets you navigate to any video and play it (requires a recent version of Chrome):
I just watched the videos of the first few sections of this math course and they're all very nice and I feel I really understand how to draw parabolas now, but the section I just watched ends with a proof.
I'm not convinced by the proof at all, it goes very fast through the basics and is very quick to point out the different relations between the ratios and the points. Now I know I've never been very quick with proofs, and I know the whole idea of Khan Academy is that you can pause and replay whenever you like, but I feel just a video isn't enough to explain even a simple geometric proof like this. Did you test this on any students? Could they reproduce the proof?
(p.s.: many events cause a bar to appear on the top of the page that pushes the entire page down, that's very not-done in web ux and causes disorientation and frustration with the user especially if the site is slow to respond (which the site is for me))
I agree that some students will not recognise the crux of the proof, but will simply see something ends up being equal to something else in some identity without understanding how that relates to what was being proved.
Euclid's Elements (an ancient Greek textbook on Geometry) is a good model in this regard. He first states what he is to prove. He then starts from the assumptions and finishes with what he was to prove. Each step in between is justified.
We also do this for the bonus step in Character Modeling (my favorite lesson!)
Our plan is to continue collecting more feedback on these different styles and find out what works best.
I've written an RSL tutorial that has been online for past 15 years (it's currently offline, I'll put it up again) and I've had people from all over the world from different studios (big and small) thank me.. it seems RSL doesn't have much resources online and considering this is tied to Pixar - do you have plans for RSL?
Pixar has ditched RSL in favor of BSDFs written in C++, so there is no real reason for learning RSL anymore. Open Shading Language (OSL) is a new shading language which is getting more and more use in the industry, but it's completely different by design.
PBRT is a great resource too. I don't know if they opted out of literate programming? I can't stand that for some reason. I've leafed through PBRT though. I've learned (back in the day, hah) from Shirley's Ray Tracing book and bibles that Andrew Glassner wrote (Principles of Digital Image Synthesis) which I still consider awesome resource.
The current edition of Physically Based Rendering still uses literate programming, but most of the maths are separated from the code, so you can skip over most of the code. Even if you can't stand I can really recommend reading it, as it's a great book. Shirley's Realistic Ray Tracing is still very useful these days, but obviously it's lacking the state of the art. If you really want to avoid any code you should read Veach's PhD thesis [2] and then some papers on BSDFs [3], shapes [4] and ray tracing acceleration [5].
[1] http://wjakob.github.io/nori/
[2] http://graphics.stanford.edu/papers/veach_thesis/
[3] http://www.cs.cornell.edu/~srm/publications/EGSR07-btdf.html
[4] http://www.graphics.cornell.edu/pubs/1997/MT97.html
[5] http://www.nvidia.com/object/nvidia_research_pub_012.html
Is there some way we could please SUBSCRIBE to notifications that wonderful speakers like these are coming to our area?
Okay, yes, I know this isn't your job, but please... you might be able to help me! :)
This is a tough area for us in general, unfortunately.
Otherwise, it's like reading the theory section of documentation without getting to use the program.
I didn't go through the whole thing initially. Excellent examples.
Thanks for your hard work. It is indeed an amazing series.