mikemajzoub

Thanks for posting those Jerry Weinberg quotes. I'd never heard of him, and just spent a few hours reading up on him. I think I've found another role model tonight :)

This thread may also end up exploring how people decide when they're dealing with an irrefutable truth (2+2=4), versus not (The world is flat, obviously.)

Humbly listen to users. Courageously question your assumptions. Iterate as fast as possible.

My current strategy is to take thorough notes whenever I pick up a new programming book.

I organize my notes by topic (i.e. "node.md", "swift.md", "git.md", "statistics.md", "cpp.md").

If it is the 3rd book I've read on JavaScript, I'll find myself speed reading my way through it, only slowing down when I encounter something unfamiliar.

In order for the above strategy to work, I need to make time for regularly reviewing all of my notes via spaced-repetition strategies so that I have a good understanding of what's in my notes and what isn't. (I use pandoc to convert my .md files into pretty html files.)

The above is definitely time consuming, so I'm eager to hear about how others tackle this problem.