People outside of engineering can't give engineers immediate credit for long-term decisions. They don't have the competency to know what to reward.

I'd go further and say that even within engineering, people outside of a team can't give immediate rewards for work whose long-term value is internal to the team, for the same reason: they don't know if the work you're doing is actually valuable or is just superficially similar to the kind of work that often does have long-term value.

If you're confident enough in your long-term decisions, and how you spend slack time, then you should be fine with being rewarded for delivery, since you expect your long-term work to pay off in future delivery and future rewards.

It's a conflict as old as time. What do you do when an argument leads to an unexpected conclusion? I think there are two good responses: "There's something going on here, so let's dig into it," or, "There's something going on here, but I'm not going to make time to dig into it." Both equally valid.

In real life, the conversation too often ends up being, "This has to be wrong, and you're an obnoxious nerd for bothering me with it," versus, "You don't understand my argument, so I am smarter, and my conclusions are brilliantly subversive."

Maybe do it more consistently! Heat acclimation takes a week with daily exposure or 2-3 weeks if you get exposure every other day[0]. If you work out in the heat once a week, you might be living that miserable first hot day of the year over and over again all summer.

[0] I don't know how well nailed down this is, but I didn't find any wildly differing opinions in my internet research: you achieve roughly 80+% of the heat adaptation you're capable of in this time period, assuming 90 minute sessions with physical activity.

Your reaction to heat is highly dependent on acclimation. I live in Texas and have to re-acclimate every year. Exercising on the first 85º+ day of the year is miserable, but a month later 85º feels quite tolerable, and 95º is doable, though performance suffers.

I grew up playing baseball and tennis in 95-100º weather with high humidity routinely. It wasn't pleasant, but nobody was getting heatstroke, nobody was cancelling games or practices. But on a visit to Montana a few summers ago, I saw that kids' baseball games had been cancelled because the temperatures had reach a dangerous level: 90º (in dry mountain air.) Same human beings, different levels of acclimation, very different safety thresholds.

I've never been in the temperatures described in this article, though, and I don't know what the physical limits of acclimation are.

That's what I've observed empirically over my last half-dozen jobs. Many developers treat decomposition and contract design between services seriously, and work until they get it right. I've seen very few developers who put the same effort into decomposing the modules of a monolith and designing the interfaces between them, and never enough in the same team to stop a monolith from turning into a highly coupled amorphous blob.

My grug brain conclusion: Grug see good microservice in many valley. Grug see grug tribe carry good microservice home and roast on spit. Grug taste good microservice, many time. Shaman tell of good monolith in vision. Grug also dream of good monolith. Maybe grug taste good monolith after die. Grug go hunt good microservice now.