Around 9 minutes, maybe: parity between design and developers
10:30 do you really need to do this?
somewhere in here (maybes in Haskell)
From 17:45 - 22:45
(it's emotional... he doesn't want stress)
Haskel removes most of the mistakes you could have made in Ruby.
Java's type system in fairly shallow.
At 21:15
You always have a ton of unknowns as a developer
That's probably an instance of a user class * could also be nil * also sometimes an array * or a hash * or a decorated class * or a subclass, etc
Oh, what does this function do? By the time you're done reading the type, you usually know what it does.