Join 📚 Rasul's Highlights
A batch of the best highlights from what Rasul's read, .
Prioritize your bugs (and even ignore some of them)
Just because you discover a bug in your product, doesn’t mean it’s time to panic. All software has bugs — it’s just a fact of life.
You don’t have to fix each bug instantly. Most bugs are annoying, not destroying. Annoyances can be tabled for a bit. Bugs that result in “it doesn’t look right” errors or other misdemeanor miscues can safely be set aside for a while. If a bug destroys your database, though, you obviously need to fix it immediately.
Getting Real - The Smarter, Faster, Easier Way to Build a Successful Web Application
37Signals
Every single human is an explosion of complexity; needs, wants, quirks, foibles, beliefs, habits, worldviews. Humans are the hardest part of any business. The closer they are to you, the harder it is. Customers are pretty much at an arm’s length… but your team is right up inside your strike zone, next to your soft underbelly. (And you are, to theirs.) Hiring looks easy but in reality it’s fraught with danger and difficulty. Even most contractors still have to be managed or at least overseen.
Being a boss is *far* more demanding and difficult than acquiring and serving customers.
5 Things I Wish Somebody Told Me Before I Founded My SaaS
Amy Hoy
Focus on the big problem first. Before jumping head-first into a new problem, find a piece of A3 paper and map out the bigger picture to see where you fit in. If a company loses $10 million on fraud but only $100,000 on faulty chargebacks, it’s 100x more impactful to figure out how to solve the former. It’s obvious in hindsight, but too often, too much time is spent without the bigger picture in mind.
Data Will Not Tell You What to Do
Mikkel Dengsøe
...catch up on these, and many more highlights
Readwise