Join 📚 Swapnil's Highlights
A batch of the best highlights from what Swapnil's read, .
It’s better to think of an employer as a customer for your business of developing software. Sure, you might only have a single customer, and all of your revenue may be coming from that single customer, but viewing the relationship this way moves you from a position of powerlessness and dependency to one of autonomy and self-direction.
We spend so much effort trying to improve our income, skills, and ability to forecast the future—all good stuff worthy of our attention. But on the other side there’s an almost complete ignorance of expectations, especially managing them with as much effort as we put into changing our circumstances.
Same as Ever
Morgan Housel
A prime example of this happened in the London tunnel system. The biggest increase in rider satisfaction (*aka value*) was never from faster trains to decrease wait times. Instead, it was from a simple dotted map that showed them when the next train was coming and how long they had to wait. The dotted map, which only cost a few million dollars, decreased the riders’ *perception* of time delay and sacrifice (being bored waiting) more than actually making the trains faster (which costs billions of dollars to do). Isn’t that cool? This is how we need to think about our products.
$100M Offers: How to Make Offers So Good People Feel Stupid Saying No
Alex Hormozi
...catch up on these, and many more highlights
Readwise