As a controls engineer who has integrated dozens of automated manufacturing cells, I have to say: none of the salespeople I interact with have buzzword densitie

As a controls engineer who has integrated dozens of automated manufacturing cells, I have to say: none of the salespeople I interact with have buzzword densities this high! As nbzso mentioned, the higher you climb the less oxygen there is... There's definitely a need for some kind of simplified programming that's understandable at different levels. Simplest is for an operator, then by a maintenance technician, by a line engineer, by a controls engineer at an integrator (like me), and by applications engineers at manufacturers and distributors. The operator needs a minimal number of adjustments - this part number might have a harder material and need to run at a reduced speed, or be highly porous and need more adhesive dispensed. That kind of hour-by-hour adjustment is typically custom-built into an HMI by the controls engineer. The tools themselves need to be debugged by maintenance techs, the robot code on a teach pendant or the ladder logic in a PLC are those languages. Hopefully, the maintenance tech doesn't have to touch the structure of the program, just some of the conditions or values for certain steps. Programs increasingly expose data at certain parts of the cycle to external databases. That's the "4IR" or "Fourth Industrial Revolution" or "Industry 4.0" component, or just a spreadsheet export, depending on your altitude. T Whether that data is analyzed in Excel, an MES dashboard, or a Python script depends on the consumer. There are DSLs at all levels, none of those people are writing assembly language. But "No code" proponents typically remove too much flexibility to the level of the implementor of the product, far removed from the end user.