What I've made for you
Book notes—Grokking Simplicity: Taming complex software with functional thinking by Eric Normand
This is one of the better books I've read on programming. It presents functional programming topics in a very simple way.
The downsides are the massive amount of repetition, writing things wrong (sometimes for many pages) before deriving the correct answer, and the lack of depth.
I would recommend this book to any novice programmer, but more intermediate or advanced programmers would likely find it too simplistic and repetitive.
Twitter thread—A synthesis of my notes on The Score Takes Care of Itself.
Being productive is about radical prioritization
You can only become so much more efficient.
Productivity is about that to a certain extent.
But from there, it's mostly about becoming more effective: making more out of less.
Think efficiency vs. effectiveness.
One way is to increase your leverage to become more productive.
Using tools like AI, shortcuts, or automations.
But often, it's more about choosing what not to do.
There's always an opportunity cost, so becoming a good judge at which opportunities give the highest return is crucial to becoming more productive.
It doesn't matter that you can get through 500 emails in a day if all of them are useless. Don't do it just because it is easy, because direction is often more important than speed.
Quote
Civilization advances by extending the number of important operations which we can perform without thinking about them.
— Alfred North Whitehead
|
