The Coding Lesson Inside Venture Step E062

The Coding Lesson Dalton Found Inside Can't Hurt Me

Venture Step episode 62 began as a review of David Goggins's memoir Can't Hurt Me. The part that lasted was not an endurance feat. It was my memory of wanting to code, being told that coding was for a different kind of student, and waiting years before I tested that judgment for myself.

That distinction matters. An inherited limit is not defeated by pretending limits do not exist. It is tested by finding out whether the old claim still matches reality.

I was told I was the wrong kind of student

I was interested in coding in middle school. When I asked about it, I heard that the work was better suited to students who could focus without much attention or support. In high school, the message became more direct: this was not a program for jocks. It was for students who were serious about their studies.

This is my memory of those conversations, not a diagnosis of the people involved or a complete record of what a school offered. Still, the category stuck. I did not consciously decide that I could never code. I simply stopped gathering evidence.

That is how another person's judgment can become durable. It does not need to remain loud. It only needs to keep a person from running the next test.

flowchart LR
    A["Someone assigns a category"] --> B["The claim goes untested"]
    B --> C["Avoidance preserves the old belief"]
    C --> D["A real need creates a small test"]
    D --> E["New evidence replaces the inherited assumption"]

A college project finally made the question practical

Years later, I was working on a fitness-company idea in college. The company did not become what I hoped, but the project created a useful constraint. I needed something built, I could not afford to hire someone, and learning enough to do the work myself became the realistic option.

I took a class and started coding.

The surprise was not that I instantly became an expert. It was that the work was accessible, interesting, and close to what I had imagined years earlier. The experiment produced better evidence than the label. It also left me with an uncomfortable question: why had I waited so long to find out?

The answer was not a lack of desire. An old judgment had become an unexamined premise.

What the memoir helped me name

The author's current book page describes Can't Hurt Me as a memoir about self-discipline, mental toughness, and pushing beyond assumed limits. That is an author-controlled description, not independent scientific evidence. It does explain why the book gave me language for the coding experience.

The memoir's most useful question for me was not, "How much pain can I tolerate?" It was, "Which limit have I accepted without current evidence?"

That question can be powerful because it moves attention from identity to inquiry. "I am not the kind of person who can code" is an identity claim. "I have not tried a beginner coding lesson under conditions that fit how I learn" is a testable statement.

The second version allows for action, support, and revision. It also allows the answer to be no. A good test can show that a path is uninteresting, inaccessible under present conditions, or not worth its cost. The point is not to force a heroic answer. The point is to replace inheritance with evidence.

The episode also showed where intensity goes wrong

E062 included stories of extreme military and endurance experiences from the memoir. I also described an 18-mile Florida run during which I stopped moving normally, my vision changed, and I could not safely drive for roughly 45 minutes to an hour.

That was not evidence of admirable discipline. It was a dangerous decision.

The CDC's current heat guidance for athletes says that weakness or faintness is a reason to stop activity and move to a cool place. It advises exercising during cooler parts of the day, beginning slowly, progressing gradually, drinking water, and monitoring another person's condition. My story should be read as a warning about letting a motivational rule override obvious safety signals.

The federal Physical Activity Guidelines are the United States government's authoritative evidence-based guidance on physical activity, fitness, and health. They do not support treating a memoir's slogan as an individualized training plan.

This correction strengthens the coding lesson. Learning a beginner skill and running through altered vision are not two versions of the same experiment. One gathers information at low consequence. The other can turn uncertainty into injury or medical danger.

A better way to test an inherited limit

Start with one sentence you have carried for a long time. It may sound like "I am not technical," "I am bad at public speaking," or "People like me do not belong in that room."

Rewrite it as a question about observable behavior. "Can I finish one introductory lesson?" is better than "Can I become a developer?" "Can I ask one prepared question in a meeting?" is better than "Can I become fearless?"

Then make the test small, reversible, and relevant. Use available support. A tutorial, colleague, accommodation, office hour, template, or quiet environment does not invalidate the result. Support is part of the conditions under which people actually work.

Finally, record what happened. Separate the skill from the setting, the effort from the outcome, and the present result from your worth. If the test was poorly designed, change it. If the path is not useful, leave it. If the old limit was wrong, let the new evidence count.

Discipline should create information, not erase it

There is a version of toughness that refuses to listen. It converts pain, fear, exhaustion, disability, uncertainty, or a request for help into evidence of weakness. That version is easy to dramatize and hard to use responsibly.

The coding experience taught me something quieter. A belief can survive for years because no one asks it to produce evidence. A modest attempt can be enough to disturb it.

That is the lesson I would keep from E062. Do not make suffering the test. Choose one inherited limit, design the smallest safe action that could teach you something, and allow the result to update the story.

[[Can't Hurt Me - Ideas Usefulness and Boundaries]] examines the book's major concepts without turning memoir into science. [[How to Design a Controlled Discomfort Practice]] provides a bounded way to test an ordinary avoidance pattern.

You can hear the original April 2025 episode on Spotify or YouTube.

Editorial note

This revised page preserves Dalton Anderson's first-person account while correcting the episode's treatment of unsafe exertion. It is not medical, mental-health, athletic-training, trauma-treatment, or disability advice. The draft was developed with AI assistance from the preserved transcript and cited sources, then prepared for human editorial review. Publication has not been authorized.