Interesting post, Steve. For the most part, I agree with you, but I will challenge you on some of it. For example, I'm interpreting what you were saying when you wrote, "I would say that far too many software engineers think that their solution will scale without actually testing it" paragraph. Around that section of your article, I interpret what you've said to be software engineers need to be willing to write something, then if it doesn't work, re-write it as something else. If I've gotten that wrong, please let me know.
Assuming, for the moment, that I've interpreted what you've said correctly, then I'd like to point out that everywhere I've worked in my career, both in the public and private sectors, as we plan to write some new software solution it really turns into considering what approach we should take, knowing that we cannot re-write it as we don't have the time. Of course, there's always a chance to make small changes along the way, based upon what we've learned or user feedback. But it is always a small change. I've taken agile and DevOps to support the idea of small changes, making minor adjustments. I've never worked anywhere that first decides we'll write a web app, then halfway through decide it would be better to make it a Windows or mobile app. It has always been the idea that once a direction is decided upon, then that's it. Stay on the course and finish the project decided upon. Your article suggests, to me, that at any point during the journey it's OK to radically change direction. I've never worked for any organization that was agile or truly practiced DevOps, so maybe my point of view is stilted. But I know that none of the managers I worked for, over the years I've worked, would consider a radical change in direction. They would first get rid of me, or whoever suggested such a daring thought, then risk delaying a project much further than it always has gone.
Kindest Regards, Rod Connect with me on LinkedIn.