No; I teach about responsible Engineering. To make beautiful code is a great thing. On your own time. That's how you become an expert of course.

So no I take nothing away from the art, in the right place and time. And thanks for the personality evaluation!

It wasn't a personality evaluation, it was a critique of your teaching methodology.

Responsible engineering isn't targeting the minimum thing that works. That's short sighted thinking that involves taking on way too much technical debt up front to pay for a faster initial release. This method might work if you're writing one-off tiny projects, but it will slam you if the project needs to adapt to new requirements in the future.

That's the difference between writing software and building a bridge. Three weeks before a bridge is completed, nobody can say, "oh BTW, this needs to also carry two trains." With software major requirements can change last minute and you better have written your code to deal with that possibility.

For many, maybe most, engineers it is targeting the minimum thing that works. For every platform or structural problem, there are 1000 apps. And they get old faster than cheese in my refrigerator. Shipping sooner for less cost is a primary metric!