Thank you, you're totally correct.
The biggest problem with tech is that it's a mental game. The act of working is a mental activity, and we can't actually switch our minds off, so it's hard to let it go. This, with the amorphous nature of when a software project is "done" definitely doesn't help with that.
So figuring out a way to work with my own mind was crucial in my own journey. And I've also downgraded responsibilities at times too like you suggest - not by getting out of dev completely, but by taking part-time or less challenging work.
Realizing that the work is never finished is key - now you can stop worrying about it.
Re construction: I thought building is a "more exact" profession as well.. until faced having a house through planning and construction. There are always ad-hoc situations to handle, modifications to make retroactively.
Programming is problematic since it is so fun and easy to get into. Then we are not used to persisting through challenging problems. Our love of the profession helps us pick up skills and make amazing progress, but a professional gets the job done even if bored to death by it. A contradiction hard to resolve.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.