Built in the Dark: The Indie Hacker's Guide to Going Full Goggins

David Goggins didn’t build an app.

But if he had, it would have shipped on time—even if he was running a hundred-mile race the day before.

Can’t Hurt Me is the story of a man who transformed himself from a 300-pound exterminator into one of the most decorated endurance athletes alive, largely by refusing to accept the story he was telling himself about his own limits.

For indie hackers, it’s not a fitness book. It’s a frame for what happens when motivation runs out.

The 40% Rule

Goggins’s central insight: when your mind is telling you to stop, you’re usually at about 40% of your actual capacity.

The quit signal comes early. The brain is conservative. It’s trying to protect you from damage you’re not actually close to.

This maps directly to building. The moment you want to close the laptop—at midnight, when the bug isn’t resolved and the feature is half-built and the launch is tomorrow—you’re probably not actually done. You’re at 40%.

The question Goggins asks is: what lives on the other side of that wall?

Callousing the Mind

Physical calluses form through repeated friction. Mental ones do too.

Goggins built his deliberately. He took cold showers when he didn’t want to. He ran routes that made him uncomfortable. He did things that felt pointless precisely because they trained him to act through resistance.

For builders, the equivalent is showing up on the days when nothing is working. When the product feels broken. When you’re three weeks past your original launch date and the feature list has only grown.

You don’t ship those days because inspiration struck. You ship because you trained for the friction.

The Accountability Mirror

Early in the book, Goggins describes standing in front of a mirror and forcing himself to be honest—not about his potential, but about his current reality. The gap between who he was and who he wanted to be.

He put sticky notes on the mirror. Every goal. Every failure. Every lie he’d been telling himself.

For indie hackers, the accountability mirror looks like this: Are you actually building? Or are you researching what to build? Are you shipping? Or are you optimizing the ship process? Are you talking to users? Or are you avoiding the answer they’ll give you?

Goggins’s version is brutal. That’s the point.

What This Isn’t

This isn’t a case for burning yourself out. Goggins himself has had injuries that resulted from going too hard too long.

The lesson isn’t to suffer more. It’s to question the ceiling you’ve accepted.

Most indie hackers don’t fail because they didn’t try hard enough. They fail because they stopped when the discomfort hit, before they found out whether the idea had real merit.

Going full Goggins isn’t about sleeping four hours a night. It’s about knowing when the resistance you’re feeling is a signal worth heeding and when it’s just noise.

Usually it’s noise.

Build through the noise. The signal will be clearer on the other side.