Earlier quoted context omitted.
I'm a software engineer that went through architecture school and I think you're glorifying architects a bit here. The only reason why architects have a more gradual path as you describe is because there is a LOT of gatekeeping and feedback on your work is a LOT slower. To become an architect you have to ideally go through schooling at a specific set of schools and then after that you have years of internships where…
Agree. I also work in the building industry (Electrical Engineering - power distribution for buildings) and I love software because of the instant feedback loop. In software, you make a typo and you get an error immediately. You fix it and go on. In architecture, you make a typo and you hear about it 6 months later, and it's a $200,000 change order (exaggerating...somewhat).
This level of thing is usually silly, ultimately-meaningless errors. (The rare exception being the metric-vs-imperial type things that literally blow up eventually.)
There are many other errors we make every day building software that lead to years or decades of tech debt. The thing we need to figure out is how to get better at making better up-front decisions on that. Being better at monitoring the long-term feedback produced by our designs, so that instead of saying "we should rewrite this in a new framework" we can say "we should restructure this doing X and Y to prevent these types of problems from coming back."