stahnma
I don't think it's wrong in most (nearly all) cases. The cost of running software, keeping it updated, changing the HW it runs on, keeping it compliant, etc over time costs much more than the dev time to build it.
Unless your service is completely replaced every couple years, I'd venture operations cost more than development. (even if dev handles the ops).
The point of the statement is designing for operability helps with ownership and combats the "leave it in the corner and hope for the best" mentality.
Code doesn't become legacy if it didn't fulfill some purpose. If it didn't work, it wouldn't be legacy, it'd be source code in somebody's home directory that was never deployed.
All working software is not legacy software. All legacy software (still running) works, for some definitions of works.
That's not to say your points aren't also really correct. Software is built with current requirements and knowledge in mind. Best decisions with info we have..etc.