0:14 - Elements of Clojure 3:16 - I. Two Kinds of Abstractions 9:05 - II. A Model for Abstractions 20:10 - III. Consequences of our Model 31:44 - IV. Systems of Abstraction 46:26 - Questions
i am a noob but i was starting to read kripke's naming and necessity and then i found this book on the internet. i was glad to find it referenced kripke's book in the beginning of this book, almost as a motivation. for me, the motivation to try to read naming and necessity was actually reading wittgenstein's private language argument, which is a sort of distilled question/problem of knowledge/language.
Phew, intense. One to watch multiple times to make it sink in.
I wish he would bring code examples in addition to the real world examples. Amusingly, his ideas stayed a bit abstract :p
0:14 - Elements of Clojure
3:16 - I. Two Kinds of Abstractions
9:05 - II. A Model for Abstractions
20:10 - III. Consequences of our Model
31:44 - IV. Systems of Abstraction
46:26 - Questions
if you are open in exactly the right way, and in exactly the right mood, this talk slaps with the force of a million suns
Hahaha yes I'm starting to feel the power of that slap while watching for 3rd or 4th time.
And none of this helps any of you to write better software. ;-)
I was looking for this talk since forever!
22:10 if we are building an AI then we do want to represent the entire world in out programming of the world model
Thanks for sharing. Really useful.
Top tier presentation and thought provoking. Especially for the abstract (no pun) subject, lot of concrete ideas and takeaways. Great presentation!
The Knuth quote actually says neither that optimization is bad always, nor 97% of the time.
See ua-cam.com/video/kHG_zw75SjE/v-deo.html
I think that's part of the joke, he’s poking fun at folk wisdom: "...depending on how much of the quote we bothered to read.”
here is where you can access the book: leanpub.com/elementsofclojure
i am a noob but i was starting to read kripke's naming and necessity and then i found this book on the internet. i was glad to find it referenced kripke's book in the beginning of this book, almost as a motivation.
for me, the motivation to try to read naming and necessity was actually reading wittgenstein's private language argument, which is a sort of distilled question/problem of knowledge/language.
Could have said "sort of" one more time to get the point across better.
lol i started noticing that after reading this comment.
Hah, I only noticed the times he mentioned "right?".