The right thing can be architectural choices in the macro and micro architecture of software that support qualities like stability, security, extensibility, int

The right thing can be architectural choices in the macro and micro architecture of software that support qualities like stability, security, extensibility, interoperability and some other -bilities. From what I experience is that many engineers don't take or don't have the time to think details through that are hard to change, later. I find functional languages to be less forgiving to bad design choices. So that's why I assume that functional languages have a smaller audience. Of course, what's right is an abstract concept. But when you see bad software, you will know it. If a company can sell bad software, they may be "right", but they also build on risks that counter that view. Edit: Btw. I don't expect software design to be 100% perfect, as long as the output is 100% correct. But every good design decision helps to build good stuff.