Simplify the mental model of the code, product, etc. Discuss it with someone.
Joint pain is a whole other thing, though. Usually joint pain means that you're doing some sort of exercise incorrectly, or that you're using too much weight or intensity for your current level of physical fitness. Or you have a previous injury that can't fully heal and there are some exercises that you just shouldn't be doing, but you do them anyway.
But I think the author is talking about less pain in a different way. For example, I threw out my lower back 25 years ago in college, and it's never been the same since. But doing core exercises and strengthening the muscles around that area means much less chance of pain doing regular day-to-day activities.
Is there anything to back this up? The people I know who work out are always complaining about their muscles and joints.
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.
It would be better if these fundamentals were spread out alongside code writing.
It's not about management skills.
It's also impolite to use "nobody" in it.
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.
If you don't have a documented mid-term check, vibe-coded PR might not be what you expected.