How to Read a Page and Write It Down

2min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

How would you read a page and then write that page? Or would you do. Yeah, I basically try to do two to three paragraphs so that my memory as I'm reading is forced to hold all of that content simultaneously. And say I've learned something about recurrent neural networks and the way that they represent information differently than convolutional neural networks or their variations. I will write down in as much detail as I can what I believe I read. Once you've written it, it's obvious to you what subset of the content you read that you knew and what subset you didn't know.

Read the full transcript here.

What is "The Index"? What are some benefits of externally compiling and organizing one's knowledge? When is spaced repetition useful? How can we co-opt our visual systems to boost memory? Would we all be more interested in producing an external personal knowledgebase if we could feel on a visceral level how much information is constantly being forgotten? How and when should we move up and down the ladder of abstraction? What sorts of problems can be solved by simulation? What is a generative model (as opposed to a predictive model)? How can constraints improve creativity? How useful are credentials as a guide to how much a person knows and whether or not a person is "allowed" to have an opinion on a topic? What do credentials actually signal about a person? What are "fox" and "hedgehog" thinking? What is deugenesis?

Jeremy is the founder of Consilience, an immersive information retrieval company. Previously he did machine learning research at Google Brain and studied Applied Mathematics at Harvard University. Jeremy works relentlessly towards aggregating knowledge, acquiring knowledge, and creating new knowledge. Find him on Twitter at @jvnixon or email him at jnixon2@gmail.com.

Staff