Join 📚 Rasul's Highlights
A batch of the best highlights from what Rasul's read, .
To paraphrase Tim Ferris, probably all of the developer heroes you look up to are walking flaws who’ve maximized one or two strengths. Here’s Dan Abramov’s list of Things He Doesn’t Know - that he knows he doesn’t know.
The Coding Career Handbook
Shawn Wang
Many engineers continue as individual contributors on the technical track because they incorrectly assume that they won’t be managing people. While it’s true that staff engineers don’t have direct reports, there is a fair amount of people management involved. They still need to work with other engineers to build consensus and buy-in for the ideas, concepts, and initiatives they believe the company should pursue.
Career Advice for the Ambitious Programmer
Holloway
The feedback you’re looking for is users saying *”You know, this skateboard gets me from A to B, but it hurts my legs and there’s nowhere to put my latte”*.
Now you know how people commute! This helps you make a better system. What if your skateboard had a cup holder and a tiny motor? Oh wait that’s a scooter.
Get working software in the hands of users and they’ll tell you how it feels. If you respond, that progress builds trust.
Users feel heard and listened to. You’re shipping tools they can *use right now* and the tools keep getting better.
Scaling Fast
Swizec Teller
...catch up on these, and many more highlights
Readwise