Reading List
20 books that shaped how I build, think, and lead. With notes on each one.
Also on
Goodreads
.
1 of 20
Man's Search for Meaning by Viktor E. Frankl
My rating: 5 of 5 stars
Frankl survived Auschwitz by holding onto a reason to live, not just willpower. He imagined his wife to keep going. The key idea: "He who has a why to live for can bear almost any how." The idea that meaning, not pleasure or comfort, is the deepest human drive. Even in the worst situation, you always keep the freedom to choose your attitude.
Freedom, in Frankl's view, is not freedom from circumstances but the freedom to choose how you respond to them. For a software developer, conditions are often out of your control: shifting requirements, production outages, impossible deadlines. The developer who finds meaning in building products that genuinely help people can stay grounded when the sprint falls apart. The "why" keeps you writing better code even when the "how" is painful.
View all my reviews
Man's Search for Meaning by Viktor E. FranklMy rating: 5 of 5 stars
Frankl survived Auschwitz by holding onto a reason to live, not just willpower. He imagined his wife to keep going. The key idea: "He who has a why to live for can bear almost any how." The idea that meaning, not pleasure or comfort, is the deepest human drive. Even in the worst situation, you always keep the freedom to choose your attitude.
Freedom, in Frankl's view, is not freedom from circumstances but the freedom to choose how you respond to them. For a software developer, conditions are often out of your control: shifting requirements, production outages, impossible deadlines. The developer who finds meaning in building products that genuinely help people can stay grounded when the sprint falls apart. The "why" keeps you writing better code even when the "how" is painful.
View all my reviews
2 of 20
Atomic Habits by James Clear
My rating: 5 of 5 stars
Habit stacking (linking new habits to existing ones) and environment design are the two most practical tools in the book. Make good habits the easiest choice by changing your space, not relying on willpower. The deeper idea is identity: instead of "I want to run," think "I am a runner." Every small action is a vote for the person you want to become, and 1% better every day compounds into a completely different life.
Turning vague wishes into measurable daily systems. Breaking a big goal into a simple daily writing habit. For a software developer, this maps directly to skill growth: blocking specific hours for deep work, setting up your dev environment so the right tool is the easiest choice, and improving slightly every day at system design, code review, or communication. A developer who applies 1% daily improvement to their craft will be dramatically better in a year than one who waits for a course or a conference to level up.
View all my reviews
Atomic Habits by James ClearMy rating: 5 of 5 stars
Habit stacking (linking new habits to existing ones) and environment design are the two most practical tools in the book. Make good habits the easiest choice by changing your space, not relying on willpower. The deeper idea is identity: instead of "I want to run," think "I am a runner." Every small action is a vote for the person you want to become, and 1% better every day compounds into a completely different life.
Turning vague wishes into measurable daily systems. Breaking a big goal into a simple daily writing habit. For a software developer, this maps directly to skill growth: blocking specific hours for deep work, setting up your dev environment so the right tool is the easiest choice, and improving slightly every day at system design, code review, or communication. A developer who applies 1% daily improvement to their craft will be dramatically better in a year than one who waits for a course or a conference to level up.
View all my reviews
3 of 20
The Millionaire Fastlane by M.J. DeMarco
My rating: 5 of 5 stars
The slowlane trap is trading time for money and hoping to retire rich at 65. The fastlane is building a business that works without you and can reach many people. DeMarco's CENTS test for a good business: you have Control (not dependent on a boss or platform), high Entry barriers (hard to copy), it solves a real Need, doesn't require your Time to run, and has Scale. Investing comes after the business generates wealth, not before.
The "computer system" (software that earns without your time) is literally what a software developer builds. With skills leverage already exists. The question is whether those skills are being used to build someone else's fastlane or your own. A SaaS product, an API, or a tool that serves thousands of users at once is the exact model the book describes, and a developer is better positioned than almost anyone else to build it.
View all my reviews
The Millionaire Fastlane by M.J. DeMarcoMy rating: 5 of 5 stars
The slowlane trap is trading time for money and hoping to retire rich at 65. The fastlane is building a business that works without you and can reach many people. DeMarco's CENTS test for a good business: you have Control (not dependent on a boss or platform), high Entry barriers (hard to copy), it solves a real Need, doesn't require your Time to run, and has Scale. Investing comes after the business generates wealth, not before.
The "computer system" (software that earns without your time) is literally what a software developer builds. With skills leverage already exists. The question is whether those skills are being used to build someone else's fastlane or your own. A SaaS product, an API, or a tool that serves thousands of users at once is the exact model the book describes, and a developer is better positioned than almost anyone else to build it.
View all my reviews
4 of 20
The Psychology of Money by Morgan Housel
My rating: 5 of 5 stars
Financial decisions feel like math but are really driven by personal history, fear, and ego. Two people can look at the same investment and both be rational based on their own experience. The "enough" concept is one of the most important in the book: knowing when to stop and not risk what you have and need for what you don't. Wealth is invisible, it's the money you didn't spend. Compounding over a long time beats any clever shortcut.
The one that stands out most for a developer is "reasonable beats rational." As someone technical, the temptation is to optimize everything: find the best investment algorithm, build the most efficient financial system, make the most data-driven decision. But Housel's point is that the best strategy is one you can actually stick to when things get uncomfortable. The same truth applies to engineering: the most sophisticated architecture you won't maintain is worse than the simple one you will. Choosing boring, sustainable solutions over clever ones is a skill, not a weakness.
View all my reviews
The Psychology of Money by Morgan HouselMy rating: 5 of 5 stars
Financial decisions feel like math but are really driven by personal history, fear, and ego. Two people can look at the same investment and both be rational based on their own experience. The "enough" concept is one of the most important in the book: knowing when to stop and not risk what you have and need for what you don't. Wealth is invisible, it's the money you didn't spend. Compounding over a long time beats any clever shortcut.
The one that stands out most for a developer is "reasonable beats rational." As someone technical, the temptation is to optimize everything: find the best investment algorithm, build the most efficient financial system, make the most data-driven decision. But Housel's point is that the best strategy is one you can actually stick to when things get uncomfortable. The same truth applies to engineering: the most sophisticated architecture you won't maintain is worse than the simple one you will. Choosing boring, sustainable solutions over clever ones is a skill, not a weakness.
View all my reviews
5 of 20
Mastery by Robert Greene
My rating: 5 of 5 stars
The 10,000 hours idea is real but incomplete. What matters is deliberate practice: focused, uncomfortable repetition with feedback, not just clocking time. Greene also says you need an apprenticeship phase where you observe and absorb before trying to be original. And the passion is not optional, it's what sustains you through the years of slow progress when no one is watching.
Mastery represents a moral evolution in Greene's writing: the focus here is on great contribution to society, not on self-advancement. For a developer with experience, the apprenticeship phase is already done. Greene would say the next phase is the creative-active: using that technical depth to build something genuinely original. The book's repetition is intentional, embedding ideas through multiple angles. In software, that is how real learning works too: reading the same concept in different codebases, different contexts, until it becomes instinct and not just knowledge.
View all my reviews
Mastery by Robert GreeneMy rating: 5 of 5 stars
The 10,000 hours idea is real but incomplete. What matters is deliberate practice: focused, uncomfortable repetition with feedback, not just clocking time. Greene also says you need an apprenticeship phase where you observe and absorb before trying to be original. And the passion is not optional, it's what sustains you through the years of slow progress when no one is watching.
Mastery represents a moral evolution in Greene's writing: the focus here is on great contribution to society, not on self-advancement. For a developer with experience, the apprenticeship phase is already done. Greene would say the next phase is the creative-active: using that technical depth to build something genuinely original. The book's repetition is intentional, embedding ideas through multiple angles. In software, that is how real learning works too: reading the same concept in different codebases, different contexts, until it becomes instinct and not just knowledge.
View all my reviews
6 of 20
How To Win Friends and Influence People by Dale Carnegie
My rating: 5 of 5 stars
The deepest lesson is that people want to feel important and understood, not impressed. Using someone's name, genuinely listening, and talking about what matters to them works because it signals they matter to you. Carnegie's point is not to fake it: become genuinely curious about people, and the rest follows naturally. Most conflicts come from making the other person feel attacked or wrong, even when you're right.
Teaching alignment of mutual interests rather than manipulation. For a software developer, this is the skill that separates good engineers from great ones. People don't adopt your architecture because it's technically correct; they adopt it because you made them feel heard first. In code reviews, technical debates, and client calls, the developer who frames things in terms of what the other person cares about consistently wins. You can be right and still lose if you make the other person feel wrong.
View all my reviews
How To Win Friends and Influence People by Dale CarnegieMy rating: 5 of 5 stars
The deepest lesson is that people want to feel important and understood, not impressed. Using someone's name, genuinely listening, and talking about what matters to them works because it signals they matter to you. Carnegie's point is not to fake it: become genuinely curious about people, and the rest follows naturally. Most conflicts come from making the other person feel attacked or wrong, even when you're right.
Teaching alignment of mutual interests rather than manipulation. For a software developer, this is the skill that separates good engineers from great ones. People don't adopt your architecture because it's technically correct; they adopt it because you made them feel heard first. In code reviews, technical debates, and client calls, the developer who frames things in terms of what the other person cares about consistently wins. You can be right and still lose if you make the other person feel wrong.
View all my reviews
7 of 20
The Hard Thing About Hard Things by Ben Horowitz
My rating: 5 of 5 stars
No book or business school prepares you for "the struggle": the moments when you don't know the answer, have no formula, and still have to decide. Horowitz is honest that being a CEO is lonely and hard in ways that are hard to explain. The practical lessons are about communication: tell people the truth even when it's painful, whether laying off employees or delivering bad news to investors. Avoiding hard conversations always makes things worse.
Two insights that apply directly to software leadership: hire for strength rather than lack of weakness, and one-on-ones should be driven by the employee, not the manager. For someone who has run a software company, these are the exact lessons that matter. Horowitz also argues that managing your emotional state is as important as any strategic decision, and in engineering, that is literally true: the developer who stays calm during a production outage makes better decisions than the one who panics. The struggle is not a sign of failure; it is the job description.
View all my reviews
The Hard Thing About Hard Things by Ben HorowitzMy rating: 5 of 5 stars
No book or business school prepares you for "the struggle": the moments when you don't know the answer, have no formula, and still have to decide. Horowitz is honest that being a CEO is lonely and hard in ways that are hard to explain. The practical lessons are about communication: tell people the truth even when it's painful, whether laying off employees or delivering bad news to investors. Avoiding hard conversations always makes things worse.
Two insights that apply directly to software leadership: hire for strength rather than lack of weakness, and one-on-ones should be driven by the employee, not the manager. For someone who has run a software company, these are the exact lessons that matter. Horowitz also argues that managing your emotional state is as important as any strategic decision, and in engineering, that is literally true: the developer who stays calm during a production outage makes better decisions than the one who panics. The struggle is not a sign of failure; it is the job description.
View all my reviews
8 of 20
Outliers: The Story of Success by Malcolm Gladwell
My rating: 5 of 5 stars
Gladwell argues that extraordinary success is never just talent or effort: it also requires the right opportunity at the right time. Bill Gates was born in 1955, which put him at exactly the right age when personal computers arrived. He also had access to a computer terminal in 1968, which almost no teenager in the world had. The 10,000 hours still matter, but without the opportunity to put them in, they never happen.
"life-altering" for shifting how you think about achievement and fairness. The timing insight is crucial for anyone in tech right now. Being a software developer and AI engineer in the 2020s is like being born early in the calendar year: the tools, the cloud infrastructure, the open-source ecosystem, and AI have multiplied what one developer can build to an unprecedented degree. Recognizing that luck and timing are part of the story should make you less arrogant about your own success and more motivated to create similar opportunities, for the teams you build and the products you launch.
View all my reviews
Outliers: The Story of Success by Malcolm GladwellMy rating: 5 of 5 stars
Gladwell argues that extraordinary success is never just talent or effort: it also requires the right opportunity at the right time. Bill Gates was born in 1955, which put him at exactly the right age when personal computers arrived. He also had access to a computer terminal in 1968, which almost no teenager in the world had. The 10,000 hours still matter, but without the opportunity to put them in, they never happen.
"life-altering" for shifting how you think about achievement and fairness. The timing insight is crucial for anyone in tech right now. Being a software developer and AI engineer in the 2020s is like being born early in the calendar year: the tools, the cloud infrastructure, the open-source ecosystem, and AI have multiplied what one developer can build to an unprecedented degree. Recognizing that luck and timing are part of the story should make you less arrogant about your own success and more motivated to create similar opportunities, for the teams you build and the products you launch.
View all my reviews
9 of 20
Think and Grow Rich by Napoleon Hill
My rating: 5 of 5 stars
The starting point is a burning desire, not a casual wish, combined with a concrete plan and obsessive focus. That level of focus makes you notice and attract opportunities that others miss. The mastermind idea is also key: surrounding yourself with people smarter than you and working toward a shared goal multiplies what any one person can do alone.
"60% brilliant, 30% obvious, 10% crazy," and that is exactly the right way to read it as a developer: extract the useful parts and skip the mystical claims. The brilliant 60% is about burning desire, concrete goals, and persistence. The mastermind concept is the most actionable: a developer who surrounds themselves with other technical founders, product thinkers, and business people will make better decisions than one who codes in isolation. The burning desire idea also explains why some projects get finished and others die: the ones that survive are the ones you actually care deeply about solving.
View all my reviews
Think and Grow Rich by Napoleon HillMy rating: 5 of 5 stars
The starting point is a burning desire, not a casual wish, combined with a concrete plan and obsessive focus. That level of focus makes you notice and attract opportunities that others miss. The mastermind idea is also key: surrounding yourself with people smarter than you and working toward a shared goal multiplies what any one person can do alone.
"60% brilliant, 30% obvious, 10% crazy," and that is exactly the right way to read it as a developer: extract the useful parts and skip the mystical claims. The brilliant 60% is about burning desire, concrete goals, and persistence. The mastermind concept is the most actionable: a developer who surrounds themselves with other technical founders, product thinkers, and business people will make better decisions than one who codes in isolation. The burning desire idea also explains why some projects get finished and others die: the ones that survive are the ones you actually care deeply about solving.
View all my reviews
10 of 20
The 7 Habits of Highly Effective People by Stephen R. Covey
My rating: 5 of 5 stars
The most practical tool is the urgency vs importance matrix: most people spend all their time on urgent but unimportant things, interdependence is critical for small teams and ignore what's important but not urgent, like health, relationships, and long-term goals. That's where most of life happens.
Production vs production capability. In software, production is shipping features; production capability is refactoring, learning new tools, and improving how your team works. Most developers and teams overweight production at the expense of capability, until the codebase becomes unmaintainable or the team burns out. A developer who wins every technical argument but damages trust is actually losing. The private habits build the character that makes the public habits possible.
View all my reviews
The 7 Habits of Highly Effective People by Stephen R. CoveyMy rating: 5 of 5 stars
The most practical tool is the urgency vs importance matrix: most people spend all their time on urgent but unimportant things, interdependence is critical for small teams and ignore what's important but not urgent, like health, relationships, and long-term goals. That's where most of life happens.
Production vs production capability. In software, production is shipping features; production capability is refactoring, learning new tools, and improving how your team works. Most developers and teams overweight production at the expense of capability, until the codebase becomes unmaintainable or the team burns out. A developer who wins every technical argument but damages trust is actually losing. The private habits build the character that makes the public habits possible.
View all my reviews
11 of 20
Awaken the Giant Within by Tony Robbins
My rating: 5 of 5 stars
Robbins argues that your decisions, not your conditions, shape your life. The six human needs (certainty, variety, significance, connection, growth, contribution) drive every behavior, and understanding which ones you prioritize explains a lot of your patterns. The book teaches how to change your emotional state fast through body, language, and focus, and how to link pain to old habits and pleasure to new ones so change sticks.
CANI principle: Constant And Never-ending Improvement. For a developer, CANI is not abstract. Changing limiting beliefs as the core personal work. Developers who stop learning because they believe they are "not a mobile person" or "not a business person" are not describing fixed facts; they are describing beliefs they haven't challenged yet.
View all my reviews
Awaken the Giant Within by Tony RobbinsMy rating: 5 of 5 stars
Robbins argues that your decisions, not your conditions, shape your life. The six human needs (certainty, variety, significance, connection, growth, contribution) drive every behavior, and understanding which ones you prioritize explains a lot of your patterns. The book teaches how to change your emotional state fast through body, language, and focus, and how to link pain to old habits and pleasure to new ones so change sticks.
CANI principle: Constant And Never-ending Improvement. For a developer, CANI is not abstract. Changing limiting beliefs as the core personal work. Developers who stop learning because they believe they are "not a mobile person" or "not a business person" are not describing fixed facts; they are describing beliefs they haven't challenged yet.
View all my reviews
12 of 20
High Performance Habits by Brendon Burchard
My rating: 5 of 5 stars
Burchard studied high achievers and found six habits: seek clarity (know exactly who you want to be), generate energy (protect your body and mind), raise necessity (make it feel critical, not optional), increase productivity (prioritize outputs, not activity), develop influence (lift others up), and demonstrate courage (act even when afraid). The "raise necessity" one is the most underrated: the people who perform best feel they must, not just that they should.
All six habits share one thing: they require deliberate, conscious effort. There are no shortcuts. Burchard's observation that "superiority draws us off track a quarter inch at a time," which is a precise description of how good software slowly becomes unmaintainable. A developer who stops questioning their architecture because it feels solid is exactly when the system starts quietly degrading. For a software engineer, high performance is not about learning one more framework; it is about practicing clarity, energy, and influence as deliberately as any technical skill.
View all my reviews
High Performance Habits by Brendon BurchardMy rating: 5 of 5 stars
Burchard studied high achievers and found six habits: seek clarity (know exactly who you want to be), generate energy (protect your body and mind), raise necessity (make it feel critical, not optional), increase productivity (prioritize outputs, not activity), develop influence (lift others up), and demonstrate courage (act even when afraid). The "raise necessity" one is the most underrated: the people who perform best feel they must, not just that they should.
All six habits share one thing: they require deliberate, conscious effort. There are no shortcuts. Burchard's observation that "superiority draws us off track a quarter inch at a time," which is a precise description of how good software slowly becomes unmaintainable. A developer who stops questioning their architecture because it feels solid is exactly when the system starts quietly degrading. For a software engineer, high performance is not about learning one more framework; it is about practicing clarity, energy, and influence as deliberately as any technical skill.
View all my reviews
13 of 20
The ONE Thing by Gary Keller
My rating: 5 of 5 stars
The Focusing Question ties it all together: "What's the one thing I can do such that by doing it, everything else becomes easier or unnecessary?" Success is sequential, one domino knocking the next. The book says multitasking is a myth and willpower is limited, so protect your best hours for the one priority and let everything else wait. Saying no to distractions is saying yes to what actually matters.
The Steve Jobs example: he reduced Apple's product line to almost nothing, and that focus is what saved the company. A developer who can build anything faces the same trap: spreading across too many technologies, clients, or side projects simultaneously. Protecting four uninterrupted hours of deep work daily. For software engineering, that protected time is where the real architecture decisions get made, the hard bugs get solved, and the code that actually matters gets written.
View all my reviews
The ONE Thing by Gary KellerMy rating: 5 of 5 stars
The Focusing Question ties it all together: "What's the one thing I can do such that by doing it, everything else becomes easier or unnecessary?" Success is sequential, one domino knocking the next. The book says multitasking is a myth and willpower is limited, so protect your best hours for the one priority and let everything else wait. Saying no to distractions is saying yes to what actually matters.
The Steve Jobs example: he reduced Apple's product line to almost nothing, and that focus is what saved the company. A developer who can build anything faces the same trap: spreading across too many technologies, clients, or side projects simultaneously. Protecting four uninterrupted hours of deep work daily. For software engineering, that protected time is where the real architecture decisions get made, the hard bugs get solved, and the code that actually matters gets written.
View all my reviews
14 of 20
Good to Great by Jim Collins
My rating: 5 of 5 stars
Collins studied companies that made a dramatic leap from average to exceptional and stayed there. The Hedgehog Concept is the center of it: find the intersection of what you can be the best in the world at, what drives your economics, and what you're passionate about. Level 5 Leaders are also key: they are quietly confident and ambitious for the company, not themselves. They credit others when things go well and take responsibility when things go wrong.
Useful context. As a developer, the right approach is to treat the Hedgehog Concept as a thinking tool, not a proven law: periodically ask what you can be genuinely world-class at, what the market actually rewards, and what you care about enough to sustain for years. Use it to frame decisions, not as a guarantee of outcomes.
View all my reviews
Good to Great by Jim CollinsMy rating: 5 of 5 stars
Collins studied companies that made a dramatic leap from average to exceptional and stayed there. The Hedgehog Concept is the center of it: find the intersection of what you can be the best in the world at, what drives your economics, and what you're passionate about. Level 5 Leaders are also key: they are quietly confident and ambitious for the company, not themselves. They credit others when things go well and take responsibility when things go wrong.
Useful context. As a developer, the right approach is to treat the Hedgehog Concept as a thinking tool, not a proven law: periodically ask what you can be genuinely world-class at, what the market actually rewards, and what you care about enough to sustain for years. Use it to frame decisions, not as a guarantee of outcomes.
View all my reviews
15 of 20
The Lean Startup by Eric Ries
My rating: 5 of 5 stars
The Build-Measure-Learn loop is the core: ship the smallest version of your idea, measure what real users do, learn from it, and then decide to pivot or keep going. The goal is not to build faster, it's to learn faster and avoid spending months building something nobody wants. In the AI era this is even more true: the cost to build and test ideas has dropped dramatically, so there is no excuse not to validate first.
For a developer, the Build-Measure-Learn loop is probably already intuitive. The real reminder is that validated learning means talking to real users, not just analyzing dashboards. Shipping an MVP in a week and getting ten real users to give honest feedback is worth more than six months of internal assumptions, no matter how technically elegant the build is.
View all my reviews
The Lean Startup by Eric RiesMy rating: 5 of 5 stars
The Build-Measure-Learn loop is the core: ship the smallest version of your idea, measure what real users do, learn from it, and then decide to pivot or keep going. The goal is not to build faster, it's to learn faster and avoid spending months building something nobody wants. In the AI era this is even more true: the cost to build and test ideas has dropped dramatically, so there is no excuse not to validate first.
For a developer, the Build-Measure-Learn loop is probably already intuitive. The real reminder is that validated learning means talking to real users, not just analyzing dashboards. Shipping an MVP in a week and getting ten real users to give honest feedback is worth more than six months of internal assumptions, no matter how technically elegant the build is.
View all my reviews
16 of 20
Start with Why by Simon Sinek
My rating: 5 of 5 stars
Most companies communicate from outside in: here's what we make, here's how we make it. Great leaders do the opposite, they start with why. Apple doesn't say "we make great computers." They say "we believe in challenging the status quo," and computers are just how they express that. People don't buy what you do, they buy why you do it. The same logic applies to careers and leadership: people follow purpose, not job descriptions.
Sinek's argument is largely circular: successful companies started with why because starting with why is what successful companies do. Southwest Airlines succeeded by copying a competitor, not by innovation. This is useful context. The concept still has real value for a developer even if the proof is thin: when you write documentation, pitch a project to a client, or convince a team to adopt a new technology, leading with why it matters is almost always more persuasive than leading with what it does. Clients hire a full-stack engineer not just for the skill list, but because they trust the developer understands what they are trying to build and why it matters.
View all my reviews
Start with Why by Simon SinekMy rating: 5 of 5 stars
Most companies communicate from outside in: here's what we make, here's how we make it. Great leaders do the opposite, they start with why. Apple doesn't say "we make great computers." They say "we believe in challenging the status quo," and computers are just how they express that. People don't buy what you do, they buy why you do it. The same logic applies to careers and leadership: people follow purpose, not job descriptions.
Sinek's argument is largely circular: successful companies started with why because starting with why is what successful companies do. Southwest Airlines succeeded by copying a competitor, not by innovation. This is useful context. The concept still has real value for a developer even if the proof is thin: when you write documentation, pitch a project to a client, or convince a team to adopt a new technology, leading with why it matters is almost always more persuasive than leading with what it does. Clients hire a full-stack engineer not just for the skill list, but because they trust the developer understands what they are trying to build and why it matters.
View all my reviews
17 of 20
Rich Dad Poor Dad by Robert T. Kiyosaki
My rating: 5 of 5 stars
The core lesson is the definition of an asset: something that puts money in your pocket. A liability takes money out. Most people buy liabilities (cars, lifestyle upgrades, sometimes their home) and call them assets. The rat race is the cycle of earning more and spending more, always needing the next paycheck. The way out is to buy assets that generate income, so money eventually works for you instead of the other way around.
The mental model still stands, and for a developer, the most relevant version is this: your skills are productive assets, but only if deployed strategically. Writing code that runs for thousands of users without your involvement is the developer's version of a rental property. Translate the asset vs liability framework into your own context and build accordingly.
View all my reviews
Rich Dad Poor Dad by Robert T. KiyosakiMy rating: 5 of 5 stars
The core lesson is the definition of an asset: something that puts money in your pocket. A liability takes money out. Most people buy liabilities (cars, lifestyle upgrades, sometimes their home) and call them assets. The rat race is the cycle of earning more and spending more, always needing the next paycheck. The way out is to buy assets that generate income, so money eventually works for you instead of the other way around.
The mental model still stands, and for a developer, the most relevant version is this: your skills are productive assets, but only if deployed strategically. Writing code that runs for thousands of users without your involvement is the developer's version of a rental property. Translate the asset vs liability framework into your own context and build accordingly.
View all my reviews
18 of 20
The E-Myth Revisited by Michael E. Gerber
My rating: 5 of 5 stars
Being good at a skill means you can run a business doing that skill. A great developer who starts a software company still needs to be a manager, a salesperson, and a visionary, not just a coder. Gerber says to build your business like a franchise: document the systems so anyone could run them, and your job becomes working on the business, not just in it.
Teaching how to operate a business independently from the owner. The core insight, working "on" the business rather than "in" it, is the most urgent lesson for any developer who starts a software company. The natural instinct is to keep coding because that is the comfort zone. But the business only grows when you build the systems, processes, and team structures that can deliver without you writing every line. Document what you do, build the playbook, and make your knowledge transferable.
View all my reviews
The E-Myth Revisited by Michael E. GerberMy rating: 5 of 5 stars
Being good at a skill means you can run a business doing that skill. A great developer who starts a software company still needs to be a manager, a salesperson, and a visionary, not just a coder. Gerber says to build your business like a franchise: document the systems so anyone could run them, and your job becomes working on the business, not just in it.
Teaching how to operate a business independently from the owner. The core insight, working "on" the business rather than "in" it, is the most urgent lesson for any developer who starts a software company. The natural instinct is to keep coding because that is the comfort zone. But the business only grows when you build the systems, processes, and team structures that can deliver without you writing every line. Document what you do, build the playbook, and make your knowledge transferable.
View all my reviews
19 of 20
Delivering Happiness by Tony Hsieh
My rating: 5 of 5 stars
Zappos almost outsourced their warehouse to save money. They didn't, because fast and reliable delivery was the core of what made customers trust them. The lesson: never outsource what your brand promise depends on. Hsieh also believed that culture is not an HR initiative but the actual product. If you get the culture right, great service and growth follow naturally.
Four-part happiness framework: perceived control, perceived progress, connectedness, and vision or higher purpose. For a developer who works with small dev teams, this is also a description of what makes a great engineering team. Perceived progress matters especially in software: teams that see their work shipping and improving are more motivated than teams grinding through invisible internal improvements. Zappos used core values as actual hiring guidelines, not wall decorations. Applying that to a technical team means hiring for cultural alignment, not just skill level.
View all my reviews
Delivering Happiness by Tony HsiehMy rating: 5 of 5 stars
Zappos almost outsourced their warehouse to save money. They didn't, because fast and reliable delivery was the core of what made customers trust them. The lesson: never outsource what your brand promise depends on. Hsieh also believed that culture is not an HR initiative but the actual product. If you get the culture right, great service and growth follow naturally.
Four-part happiness framework: perceived control, perceived progress, connectedness, and vision or higher purpose. For a developer who works with small dev teams, this is also a description of what makes a great engineering team. Perceived progress matters especially in software: teams that see their work shipping and improving are more motivated than teams grinding through invisible internal improvements. Zappos used core values as actual hiring guidelines, not wall decorations. Applying that to a technical team means hiring for cultural alignment, not just skill level.
View all my reviews
20 of 20
The 5 Second Rule by Mel Robbins
My rating: 5 of 5 stars
The moment you hesitate, your brain starts building reasons not to act. Counting 5-4-3-2-1 and moving interrupts that pattern before doubt takes over. Robbins came up with it when she couldn't get out of bed in the morning and started using the countdown to force herself up. It works because it bypasses feelings entirely, you don't wait to feel ready, you just count and go.
The core insight that lands hardest is that motivation does not precede action: action precedes motivation. For a developer, this is the most counterintuitive and useful idea in the book. You do not wait until you feel like refactoring the messy codebase, writing the documentation, or sending the uncomfortable client update. You count down and start. The PR you have been avoiding, the conversation about scope, the new technology you keep pushing off: those are exactly the moments to use the rule. Start the count, then go.
View all my reviews
The 5 Second Rule by Mel RobbinsMy rating: 5 of 5 stars
The moment you hesitate, your brain starts building reasons not to act. Counting 5-4-3-2-1 and moving interrupts that pattern before doubt takes over. Robbins came up with it when she couldn't get out of bed in the morning and started using the countdown to force herself up. It works because it bypasses feelings entirely, you don't wait to feel ready, you just count and go.
The core insight that lands hardest is that motivation does not precede action: action precedes motivation. For a developer, this is the most counterintuitive and useful idea in the book. You do not wait until you feel like refactoring the messy codebase, writing the documentation, or sending the uncomfortable client update. You count down and start. The PR you have been avoiding, the conversation about scope, the new technology you keep pushing off: those are exactly the moments to use the rule. Start the count, then go.
View all my reviews