Traditional rules of simple code design:
^This is put in order of importance. Now some have argued over the order of 2 & 3, because when you're doing one you're doing the other...these 2 rules inform each other in a rapid feedback cycle.
Notes taken from reading How To Read a Book by Mortimer Adler.
"Knowledge is not as much a prerequisite to understanding as is commonly supposed. We don't have to know everything about something in order to understand it; too many facts are often as much of an obstacle to understanding as too few. There is a sense in which we moderns are inundated with facts to the detriment of our understanding." - p.4
"Reading is a complex activity that consists of several acts, all of which must be performed to be 'good reading'."
Combined guide from reading https://pne.people.si.umich.edu/PDF/howtoread.pdf and How To Read a Book by Mortimer Adler.
why you're gonna read it and how you're gonna do it
'clear the clutter in our heads and our minds'
just asking, "what if this could be easy?" is a simple way to reset your thinking
choosing an indirect approach - for a really difficult task (as opposed to hitting it head-on)..how do you do this in practice? Consider strategy before doing aka "how should I approach this for ease?"
data intensive apps are built from building blocks:
