"Move fast and break things".

It's funny how words have a habit of coming 'round to their original meanings. It might be time we stick tech companies in those helmets and leashes they used to put on hyperactive kids.

Great words! I would add that the developer block specifically appears when you delve too deeply. You may get stuck in limbo.

Simplify the mental model of the code, product, etc. Discuss it with someone.

Soreness isn't ideal. It won't make you stronger. Actually, it might make your recovery slower.

First time I've ever heard that soreness = something wrong. Isn't soreness basically guaranteed to some degree if you've done enough work to actually build strength?

> Isn't soreness basically guaranteed to some degree if you've done enough work to actually build strength?

Not really. If you're eating/sleeping well and training consistently it's completely normal to not feel soreness (that is, excluding the immediate discomfort that rapidly subsides). I can't speak for all forms of exercise, but certainly it's normal when lifting weights, even to failure.

That said, if you're just starting out you will notice a lot of soreness. Many people look back on the early DOMS and wish they could feel that sort of "positive feedback" again.

I noticed that two things make my DOMS disappear like magic:

- eating an shocking amount of spinach (works much better than a magnesium pill)

- some sort of light cardio of the affected muscles after lifting

It depends. But as GP also said, it can be because one is not exercising (that part of the body) regularly. Anecdotally, I have seen that soreness is not really observed when exercising regularly. Some aches and a little fatigue? Probably. But not really muscle soreness.

True

I suggest reading or listening to Dr. Andy Galpin on this topic.

Physical activity triggers the production of endorphins, specifically beta-endorphins, which are natural painkillers.

Physical activity increases lifespan primarily by lowering the likelihood of falling and breaking your hip. If you break your hip, your life expectancy is dramatically reduced. If that's your goal, just train your legs!

That said, I think the most important part of exercising is the mental boost it provides. It's like a healthy drug. There are no negative side effects, and it's highly praised by society.

That's certainly not the only (and I'd also not put it as primary) reason for extending the lifespan.

Still, breaking one's hip in advanced age is often a death sentence as many people never get out of bed again.

When an old person breaks their hip around here, people say something along the lines of "we'd better hurry up for visiting them one last time".

There's also a lot of reverse causation here. Healthy people don't fall very often and when they do they generally don't break their hips. Falling frequently and suffering broken hips when falling are both general signs of poor systemic health and overall fragility which portend a short remaining lifespan regardless.

It's probably just me but I've had the opposite effect. When exercising I typically can focus less and I'm less productive.

My most productive days are when I just start working on my computer after tea/coffee in the morning and can keep building momentum over the day. Any distractions like exercise break my momentum.

> If that's your goal, just train your legs!

This should be easily confirmed by analyzing life expectancy of people with squat toilets vs a traditional western camode.

Look at the abysmal life span of russian men. They squat all the time.

You aren’t wrong. Train your legs and walk. Don’t sit in the recliner when you retire. 7000-10000 steps a day helps

True, however I know a lot of people over 60 who think that walking alone is sufficient. You need to strength train too. Train your abs and at least do body squat variations. Walking is great to lose weight and keep your heart healthy, but not sufficient in itself.

I agree with you. My comment wasn’t as detailed as yours but I meant the same. Great advice!

Interestingly for many people the break precedes the fall.

Yes. Programming isn't just writing code.

It would be better if these fundamentals were spread out alongside code writing.

Sometimes I think it would be good to have separate terms.

Programming is just writing code. It might or might not be complicated say you fine tune some assembly algorithm.

Developing would be next step up. As you need bigger view.

Software engineering is when you start to consider what would be good engineering and making decisions before just writing code.

Software architecturing is interdisciplinary with engineering and happens is larger systems.

I really think we have done lot of disservice, by grouping all of the things also under coding or programming.

That's the way it was decades ago. In the mid-1980s, a headhunter cold-called me at work and asked what I did. I answered, "I'm a computer programmer." Sounding severely disappointed, he said, "Oh ... Is there anyone in your office who designs programs?" I responded, "Yes, we all do." I was aware of this mindset from books I'd read in the late 1970s when I first got interested in computers.

In the 1990s, I worked as a contractor at a very large engineering corporation and I was surprised to discover they still had developers who only designed programs down to the pseudocode level and then handed them off to "programmers" for coding. I thought this was stupid as all get out as there was no feedback mechanism in place, so the "designers" never learned of and from their mistakes. (And a feedback mechanism wouldn't be enough in my opinion, as the designers really needed to be mired in the mud of producing a working system.) This was especially serious as some of the programs ran on embedded real-time computers and the designers had no hands-on experience with the real-time OS and would not gain that experience simply through designing.

Experienced programmers do bits at all 4 of the levels without consciously thinking, "I'm doing engineering here, developing there, ..."

Reading comments. It seems like there are a lot of bad managers.

The title is misleading.

It's not about management skills.

It's also impolite to use "nobody" in it.

Agreed. Cliff's Notes version: "Apologize when you make mistakes."

This can be used in any process where the result is only judged at the end.

The solution here may be to add a midterm check. I think this is what you mean by a "design review."

In my experience, there are some rules that need to be followed for it to work.

- Keep the number of stakeholders involved in all decisions, including PR, as small as possible.

- Everyone involved should take part in this check. That way, no one will be surprised by the results.

- This check should have been documented, like in the ticket.

This can be used in any process where the result is only judged at the end. The solution here may be to add a midterm check. I think this is what you mean by a "design review." In my experience, there are some rules that need to be followed for it to work. We should keep the number of stakeholders involved in all decisions, including PR, as small as possible. Everyone involved should take part in this mid-term check. That way, no one will be surprised by the results. This check should have been documented, like in the ticket.

When and how to do this check and how to handle disagreements depend on the task, culture, and personalities.

We should do something similar with AI-coding.

If you don't have a documented mid-term check, vibe-coded PR might not be what you expected.

After reading this, it's clear that: 1) It's more important to hit the target (what users need) than to throw quickly or with force. 2) We often don't realize how scalable things are.