In partnership with
Take control of your chaotic inbox
Stop drowning in spam. Proton Mail keeps your inbox clean, private, and focused—without ads or filters.
Another week in the books. I do not know what your week looked like, but mine had its moments. Some things clicked. Some things reminded me that I still have a lot of distance to cover. Both of those are useful, in their own way.
Here is what I was reading, listening to, and watching. No filler. No content for the sake of content. Just the things that actually made me stop and think this week.
Grab your drink. Let us get into it.
Book of the Week
READING
I have been reading Maxwell on and off for years, and this is the one I keep coming back to during seasons of rebuilding. The timing this week was not accidental. I have been in a stretch of going back through old failures with a different lens, trying to figure out which lessons I actually extracted and which ones I quietly skipped. This book has been on my shelf for a while. This was the week I finally pulled it down and read it the way it deserves to be read, which is slowly and with a pen in hand.
How to Get a Return on Failure is exactly what the title says. It is not a feel-good book about how failure is secretly a gift. It is a practical guide to extracting actual value from the times when things go sideways. Maxwell breaks down a process he calls the Failure Reaction Path, and he frames the whole question of failure in terms of return. What did this cost you? What did you get back? And if the gap is too big, what are you going to do about it?
What separates this book from the broader genre of failure-as-fuel content is Maxwell’s insistence on practical specificity. He does not romanticize failure. He treats it like the expensive, often painful event that it actually is, and then he asks the question that most people skip: given what this cost you, what is the minimum return you should be extracting from it? The framing of failure as an investment with an expected return is a useful reframe, especially for entrepreneurs who tend to wave off losses as “experience” without ever actually mining them for anything specific.
The chapter on the difference between people who fail backward and people who fail forward is worth the price of the whole book. Maxwell argues that failing forward is not a personality trait. It is a learnable skill, with specific habits and disciplines that any operator can build. He breaks down the mental moves required, names the emotional traps that prevent people from doing the work, and gives practical frameworks for converting setbacks into structural improvements in how you operate.
What hit me hardest was the section on the Failure Reaction Path itself. Maxwell maps out the predictable stages most people go through after a setback, and shows where the path forks. One fork leads to extraction and growth. The other leads to denial and repetition. The fork is not as obvious as you would think. Once you see it clearly, you start noticing it in real time, which is the actual work.
For anyone in a rebuilding season, this book is required reading. It will not make the failure feel better. But it will help you make sure the next one is smaller, less expensive, and further apart.
Get it here: How to Get a Return on Failure on Amazon
Three Articles Worth Your Time This Week
ARTICLES
Article 1: How the Best Operators Build Antifragile Workflows
Source: Operator’s Notebook
I have been reading a lot lately about antifragility in business operations. The concept comes from Nassim Taleb. The application to small business operations is something I am seeing more and more practitioners write about, and this piece pulled it together better than most.
The basic idea is this. Most businesses are built to withstand shocks. They are robust. They have backup plans, contingencies, redundancies. That is good, but it is not enough. An antifragile business does not just withstand shocks. It actually gets stronger from them. The shock is fuel.
What does that look like in practice? It looks like building feedback loops into every system you have, so that when something breaks, you do not just fix it. You upgrade the whole system. It looks like running small, frequent experiments instead of big infrequent ones, so that failure stays cheap and learning stays fast. It looks like designing your offers, your team, and your tech stack with optionality built in, so that when conditions change, you can pivot without rebuilding from scratch.
I have started applying this to my own consultancy. Every time a client engagement reveals a friction point in my delivery, I do not just fix the friction. I rebuild the underlying process. Six months in, the consultancy operates on a fundamentally different chassis than it did at the start of the year, and the changes came almost entirely from things that initially looked like problems.
Read it here: Operator’s Notebook
Article 2: The Quiet Power of Small Daily Decisions
Source: The Daily Operator
The second article I have been chewing on this week is about the gap between intention and action, and specifically about how small daily decisions compound into massive directional shifts over time.
The author makes the case that most people overestimate what they can do in a day and underestimate what they can do in a year, which is a Tony Robbins quote at this point but the article does something useful with it. It breaks down the actual mechanism by which small decisions compound. It is not just about consistency. It is about the way each small decision makes the next small decision easier or harder.
The example that stuck with me was the morning routine one. Not because morning routines are some magic productivity hack, but because the article points out that the value is not in the specific activities. The value is in the early signal you send to yourself about what kind of day you are going to have. If the first three decisions you make in the morning are the ones you said you would make, the next thirty are easier. If the first three are compromises, the next thirty are harder.
I have been testing this. Not in any rigid way. Just paying attention to which mornings produce focused work and which ones produce reactive scrambling. The pattern is depressingly consistent. The mornings I keep my own commitments to myself are the mornings I get the real work done. Which means the work does not actually start when I sit down at my desk. It starts when I get out of bed.
Read it here: The Daily Operator
Article 3: Why Your Revenue Ceiling Is Usually a Belief Ceiling
Source: Stacked Insights
The third article hit me in a place I was not expecting. The premise is straightforward. Most entrepreneurs hit a revenue plateau not because of market conditions, not because of competition, not because of any external constraint. They hit it because they have maxed out their belief about what they are worth, what their offer is worth, or what their next level looks like.
The author walks through several case studies of business owners who broke through their plateaus, and the pattern is consistent. The breakthrough was not a new tactic. It was not a new platform. It was not a new offer in any meaningful structural sense. It was a new identity. The owner started thinking and acting like the version of themselves who was already at the next level. The revenue followed.
I find this both inspiring and uncomfortable. Inspiring because it means the constraint is solvable. Uncomfortable because it means the constraint is me.
If you have been bumping up against a number you cannot seem to break through, this article is worth your time. The work is not easy, but the diagnosis is precise.
Read it here: Stacked Insights
Podcast of the Week
LISTENING
This podcast episode landed in my queue at exactly the right moment. The premise is one of those things you have heard a hundred times but rarely hear unpacked with this much practical detail. Leadership requires emotional regulation. Not suppression. Not avoidance. Regulation. The ability to feel what you are feeling, name it, and choose your response instead of just reacting.
The host walks through several scenarios where leaders blow up their own teams, their own deals, and their own reputations because they could not pause long enough to choose differently. He is not preachy about it. He uses real examples, including some from his own career, and he gives actionable frameworks for building the regulation skill over time.
What I took from this episode was a renewed commitment to the gap between stimulus and response. The space where leadership actually happens. Most of us think leadership is about what you do. The episode argues that leadership is mostly about what you do not do in the moment when reacting would be easier. The pause is the work.
I listened to this one twice. The second time I took notes. There is a section about a third of the way through where the host breaks down the physiological component of emotional regulation, and how breath, posture, and body awareness all factor into your ability to lead well under pressure. I have started building some of his suggestions into my own pre-meeting routine for high-stakes calls.
If you lead a team, work with clients, or have any kind of skin in the game where your emotional state directly impacts your outcomes, this one is required listening.
Track on Repeat
LISTENING
I have had this song on repeat all week. There is something about the live version that hits different. It is raw. It is honest. It is not trying to be polished. It sounds like it was recorded by someone who knows exactly what it costs to still be standing.
Zach Williams writes from a place of having been there. His whole catalog has this quality of testimony rather than performance. I Am a Survivor is about exactly what it sounds like, but it is not a triumphant chest-pounding kind of survival anthem. It is quieter than that. It is the kind of survival that comes from showing up day after day when you were not sure you could, and then realizing one morning that you have been doing it for a while now.
The live version adds a dimension you do not get on the studio cut. The crowd is part of the song. You can hear them singing along on the choruses, and there is something about hearing that many voices commit to those words at the same time that lifts the whole thing into a different category. It stops being a performance and starts being a declaration.
I have been playing this one in the morning while I make coffee. It is setting the tone for the kind of day I want to have. The Grace Over Guilt framework I keep coming back to, and the rebuild work I have been doing in my own life and business, both line up with what this song is naming. There is something honest about declaring out loud that you are still here, still building, still in the fight, especially on the mornings when that declaration is the most expensive thing you can say.
Not a focus playlist track. Not background noise. Something to actually listen to.
Listen here: Zach Williams: I Am a Survivor (Live) on Apple Music
Show of the Week
WATCHING
Project Hail Mary is one of the most fun pieces of storytelling I have consumed in months. It is based on the Andy Weir novel of the same name, and if you liked The Martian, you are going to like this. Same author, similar DNA, completely different scope. The recommendation here is for both the novel and the film adaptation, depending on which format you prefer. Both are worth your time.
The premise is hard to discuss without spoiling anything, but I will give you the broad strokes. A man wakes up alone on a spaceship with no memory of how he got there or why he is there. The story unfolds as he pieces together both his mission and his identity, with the stakes being roughly the survival of humanity. So, you know. Low pressure.
What I love about this story is the way it celebrates problem-solving as its own kind of heroism. The main character is not some chiseled action hero. He is a high school science teacher who happens to know enough chemistry, biology, and physics to keep figuring out the next problem in front of him. He fails constantly. He recovers. He tries again. He uses what he has, learns what he does not, and keeps moving forward.
There is a structural lesson in here for anyone building anything. The hero’s edge is not talent or destiny or some unique gift. It is the willingness to keep engaging with the next problem, even when the previous one nearly killed him. Especially when the previous one nearly killed him.
For anyone in a rebuilding season, or anyone bumping up against a problem that feels too big to solve, this story is a quiet kind of medicine. It does not beat you over the head with the inspiration. It just shows you what it looks like to keep working the problem, one move at a time, until something gives.
Get it here: Project Hail Mary on Amazon
Resources Section
EVERYTHING LINKED IN ONE PLACE
Tools I use and trust. If you sign up through these links I may earn a small commission at no extra cost to you. I only recommend things I actually use.
Find out why 200K+ engineers read The Code twice a week
Staying behind on tech trends can be a career killer.
But let’s face it, no one has hours to spare every week trying to stay updated.
That’s why over 200,000 engineers at companies like Google, Meta, and Apple read The Code twice a week.
Here’s why it works:
No fluff, just signal – Learn the most important tech news delivered in just two short emails.
Supercharge your skills – Get access to top research papers and resources that give you an edge in the industry.
See the future first – Discover what’s next before it hits the mainstream, so you can lead, not follow.