Two weeks ago, the heat shifted where I live, and last weekend it caught up with me on a long ride. I ran out of water about two-thirds of the way through, and the last stretch made that impact very clear. I cut the ride short by eleven miles because I hadn't managed the heat correctly, and my body made the decision for me. 

This is the version of a bad hot weather workout that most runners never get a clear explanation for. They try to drink more water, they slow down, and they blame the heat or decide they're just not built for running in it, and they never isolate the variables that keep working against them.

Last week was one of those weeks where the same idea kept showing up in different places.

I was working through my own race calendar for the rest of the year - mapping out which races between now and Ironman Cozumel in November are doing real work in my build. Having that date locked for months has made every training decision cleaner. What to prioritize, what to skip, which races to add and which ones to pass on. When you have a clear endpoint, the decisions in between stop being guesses.

There's a conversation I have at club runs more often than I'd like. Usually after we stop, when people are cooling down and relaxed enough to mention what's bothering them.

Last week it was a runner I know who is getting ready for her first marathon. She was clearly in pain, and she let me know her hip had been hurting for several weeks. Bad enough that she almost went to urgent care the week before. But there she was, pushing through the run, telling me about it like it was a minor inconvenience she just had to work around. 

At this point, I'm not surprised by these conversations, because I've been that person. For longer than I should have been.

I was on a run with one of my clubs last week when one of the regulars asked me what she should eat before a run.

She's a retired nurse with decades of experience in healthcare. She understands how the body works at a level most people don't. And she was genuinely uncertain about whether fruit was okay before a workout, whether she needed protein beforehand, and whether her muscles would break down if she got it wrong.

When I sat down to write this piece, I noticed the date this article was going out. Last day of June.

I just came off my fourth half Ironman a few weeks ago, and I've been in that strange in-between space since. Recovered enough to think clearly again about what’s next, not yet deep into the next build. It's the kind of week when you can reflect on the calendar rather than just react to it.

Half the year is gone. The other half is still sitting there, unclaimed.

Over the last few weeks, I've been asking people at the run clubs the same question: why do you come to the runs? 

The answers usually start the same way. They came for something practical - they wanted to get into fitness, they were looking for something social, they needed a reason to show up consistently. The club gave them that.

Last week, someone asked me how they should be breathing while they run.

It's a reasonable question. People ask questions like this all the time. What's the right cadence? What's the best stretch before a run? Should I be landing on my heel or my forefoot?

Underneath all of these is the same real question: how do I run faster?

There's a week somewhere in every training block where nothing feels right.

Your easy runs feel hard. Your legs are extra heavy on days they shouldn't be. You're doing everything the plan says. Sleeping enough, eating enough, showing up. And somehow the strength you felt last month seems to have packed up and left. 

Most people assume something has gone wrong.

The registration email lands in your inbox at 11:47 pm on a Tuesday.

You know how this goes. You've been here before with the cursor hovering, the small hesitation, then the click.

You've done the long runs before. You've stood at a starting line with cold legs and a stomach that won't settle. You know the wall that comes in the later miles, and you know the miles after the wall. You know exactly what you just signed up for.

He'd been struggling for months.

Every run felt like a fight he couldn't win. His pace would spike, and his heart rate would follow.

No matter what he adjusted, the effort never evened out. He was working hard, but most of his miles were being done at a walk, and it was starting to show in how he talked about his running. 

But he kept going. Consistent days, easy effort, same plan.

The late-ride fade used to be a given.

I'd be an hour and a half into a long bike session, fueling the way I'd always fueled with a gel every thirty minutes, roughly fifty grams of carbohydrate per hour, and somewhere around mile forty, the effort would start to feel really heavy. My energy would drop. Focus would narrow to just getting to the end. I'd finish the session, but I'd finish it feeling empty.

I assumed it was a fitness problem. I needed more base. More training sessions. More time in the saddle. More weeks of work before the long rides would stop feeling that hard at the end.

I got an interesting text from a client about a month before her recent race.

It had nothing to do with the race, really. She'd already done three long races, including a full marathon, in the time we'd worked together - she knew how to get to a start line. Her text was about what came after.

She was planning to climb Mt. Whitney a few months out and wanted to know if it would mess with her training, and whether she needed to think about it differently for the new challenge she was taking on.

A runner I know took three weeks off training because he was feeling exhausted, lacking motivation, and his legs felt heavy every time he went out.

He'd been training consistently for months and couldn't understand why his body wasn't responding the way it used to. The effort and miles were basically the same. But something had shifted, and he couldn't put his finger on what.

He'd read about overtraining syndrome, and the symptoms looked familiar. So he backed off.

If there’s at least one thing all runners have in common, it’s the desire to get faster.

So when a runner comes to me logging 20 to 30 miles a week with a pace that hasn't moved in months, the first thing I look at isn't their hard days. It's their easy ones.

Most of the time, every run is sitting in the same zone, above base-building intensity, below threshold. Working hard enough to be tired every day, but not hard enough to improve the foundation.

A runner told me something last week that I've heard many times before. She wanted to do a half-marathon, but she was scared she wouldn't be able to finish it.

She wasn't describing an injury or a lack of commitment. She hadn't been told by a doctor or anyone else to hold back. The thing standing between her and the registration page was the fear that she wasn't capable of a bigger challenge.

She had already finished a 10k, but somewhere along the way, she'd picked up the idea that something bigger was undoable.

I've been writing long-form articles for well over a year on different platforms. For most of that time, the response was silence. No likes or comments, no signal that any of it was landing. Just me, publishing into the void on a schedule I'd set for myself.

The insecurity that comes with that kind of silence is real. You start to wonder if the writing is actually bad and nobody has the heart to tell you. You wonder if the work is just too niche to ever find an audience.

You think about stopping more than once, but you publish anyway.

The first time I tried to run by heart rate - more specifically, low heart rate - I made it about a quarter mile before my watch told me I was working too hard. So I slowed down.

Then it told me it was still too much. I was shuffling through my neighborhood at a pace that would embarrass a casual walker, and my heart rate was still too high. Every time I looked at my watch and saw the number, I slowed down a little more and felt a little more ridiculous about it.

Lots of people passed me in those sessions. Not racing past me, just running past me, at what any reasonable person would call a normal pace. I told myself it didn't matter, but at some level it did matter.

I was at a group program event, doing shares and asks with people I'd just met.

One of the guys had been working with coaches for a few years, trying to find his direction. Around $200,000 across different programs, different frameworks, different promises. When it was his turn to share, that's what came out — still searching, still uncertain, no clearer on where he was going than when he started.

I asked him what he was feeling pulled toward.

He paused for a long time. Then he said he still had no idea.

A runner came to me recently convinced she had a cadence problem.

She had gotten an alert from her watch or maybe seen a coach post about the topic online. Either way, the message she took in was stressing her out: her natural stride wasn’t perfect, which meant she was being inefficient, and there was a fix available if she was willing to work for it.

She had been running for three years without injury. She had run a marathon. She was getting faster and felt good as an athlete. But none of that mattered once someone told her something was wrong.

The first time someone asked me to speak about my coaching on a podcast, I said yes before I could think about it.

Then I spent three days trying to talk myself out of it.

I was a newer coach. I had never done anything like this before. Everything I knew about running and endurance and helping athletes get to start lines had only ever lived inside conversations with clients, and my own experiences as an athlete. I had no idea what would be asked, no idea if what I had to say would land, and no real reason to believe anyone outside my small circle would care.