No, i do not. But i suggest having environments, that teach those technicians over time the basics and shove them towards searching for engineering knowledge for solutions and incooperate best practices.

I'm violently opposed to crunching those "self-thought" to death in no-code-marathons were they are expected to realize complex behaviour with declawed software-Lego-bricks.

Software is eating their world too. Have you ever seen the eyes of a guy who copy pasted a "pallet" structure together, because he never knew about arrays?

PostScriptum:

>Nobody wants it and the few that want it don't want

>to pay for it. Control engineering really isn't a

>branch of CS, its culturally its own thing.

I have heard these lines a thousand times by now.

Its different - we have processes that require hard "Real-time"-capable hard and software..

So.. Space X and all those other projects using hard real-time in the lower decks, are not software controlled devices?

Its different -we have physical processes we control at the end of day. So a amazon package logistic center is not a physical process? A self-driving car is not a physical process?

Its different, reliability is huge if the process ever fails. So Google and AWHs DevOps do not have that pressure?

Its exactly this. Just another, run-down department of CS. Run-down to save a few cents and now running into the limitations its No-Code solutions impose. Grinding good, untrained people to dust, because it wants to save money. And thus ready for disruption.