Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
So here are the benefits of inheritance:
• Unlike composition, you can pass the subclass into functions expecting the parent class.
• Unlike interfaces, you can reuse code from the parent class in the child class.
So, here’s when you want to use inheritance: **when you need to instantiate both the parent and child classes and pass them to the same functions.** That’s it. That’s the use case.
When to Prefer Inheritance to Composition
Hillel Wayne
A surprising amount of executive time is spent cleaning up messes. Some of these messes are externally motivated, like a competitor launching a new product, but a surprising number are self-inflicted. At least half the self-inflicted messes that I’ve seen executives create are caused by unsympathetic or confusing communication, which you can easily prevent by testing your communication before widely broadcasting.
Internal Comms for Executives.
Irrational Exuberance
The value of a product is the number of problems it can solve divided by the amount of complexity the user needs to keep in their head to use it. Consider an iPhone vs a standard TV remove: an iPhone touchscreen can be used for countless different functions, but there's very little to remember about how it works (tap, drag, swipe, pinch). With a TV remote you have to remember what every button does; the more things you can use the remote for, the more buttons it has. We want to create iPhones, not TV remotes.
My Heroku Values · GitHub
gist.github.com
...catch up on these, and many more highlights
Readwise