Do you want to be doing those things when you're 30?
25?
20?
Maybe there's a better way...?
Because, oddly enough, I have been in the industry a long time, I happen to know that's wrong.
The "all the bullshit" of the industry is not a product of the immaturity of the industry. Because it had gotten worse. In each of my five-ten year job search cycles, I have observed more companies with more of the problems you describe (60+ hour work weeks, 24/7 on call, psychological pressure for death marches, etc). Each time, consistently more insanity.
Not sure exactly what to do myself or in general but I'm pretty sure we can't chalk this up to an immature industry.
Besides you don't want to fire fighting with software, But you are OK with firefighting with life? Especially when you are 50?
I think the secret question behind a lot of this sentiment is: do you want to still be burning yourself out at 50? Do you want to still be working 60+ hour weeks? Do you want to still be on call 24/7? Do you want to still spend part of every release cycle in a pitiless death march?
And, ultimately, do you still want to put up with all of the bullshit in this industry?
But all of that bullshit is not an inherent part of working in this industry, it's just a byproduct of the immaturity of the industry.
The author here tries to draw a distinction between "Type A" (programming by intention) and "Type B" (reactionary programming verging on programming by accident) but there's really nothing wrong with "maintenance mode programming" as long as you're not perpetually in firefighting mode. Indeed, concentrating on polish, performance, and robustness are often fantastic ways to improve a system, provided that they are done well and not half-assed last-minute kludges.