Hi guys,
Love your stuff, really. Engaging visual, audio, and tactile senses1 (typing code, writing notes) at the same time is an excellent way of picking up new skills.
If it is not too much to ask, for longer screencasts could you put a simple Table of Contents within the first few seconds of the video? Something like
1. Has-many associations - 01:59
2. Polymorphic associations - 04:03Sometimes when I’m trying to recall the exact implementation details of something I go back to your videos, and I have to skip about to find it. It would be easier to drag the slider to the time value given by a handy TOC.
I think this is probably something relatively straightforward to do (compared to the huge amounts of work you are already putting in!) and will greatly increase value for your consumers.
Thanks. You guys rock.
Best,
Tim.
UPDATE: PeepCode has some screencasts with Quicktime chapter tracks , and will be including chapter tracks with other screencasts in the future.
1 Just a thought when it comes to engaging senses and learning/coding. I think it would be hilarious to have a device that literally emits a bad smell anytime you’re writing bad code. That may be difficult to identify, but stuff like using deprecated functions, having too much logic in views, etc can all be detected programmatically. Just imagine, you could walk past someone’s desk and be like “Ugh! That’s some nasty code you’re writing today”.
