Blaine reads code, especially Smalltalk.
There's such a plethora of code out there in Smalltalk land that is entertaining to see how "they did it". For instance, I was surprised to see how small the continuation class used in Seaside was.
Agreed. (Too much?) time can be (well?) spent clicking around the code browsers.
I think it's a good thing. Also trying to get it to execute to a point you don't completely understand. Put a
self halt in there and see what happens. Why didn't it get there? Poke around, oh, I think... cool! Look up the stack.
There's never a question of "Did they compile this with
-g?" and "Did they provide the source code?"