That's the key. A structural engineer ostensibly has the background necessary to work without the tool, albeit with much less efficiency. Because of that they should have a first principles understanding of what situations the tool won't apply rather than the situation breaking down to 'garbage in/garbage out'.
I'll be the first to admit that measuring this in terms of education is at best a proxy for that knowledge, and have met technicians that truly understand what they're working on better than most engineers they worked with, and engineers that promptly forgot everything as soon as the exam was over. But what is listed above is the underlying piece that's attempting to be controlled for. It's a hard concept to measure.
Right, they do. Not everything an engineer does is engineering.
> A structural engineer I know uses software to design beam strengths in buildings. He understands what the software is doing, but he didn’t write the software and he uses the outputted parameters at part of his designs.
I've worked with formula-plugger engineers, too. But they would, now and then, misuse the formulas because they didn't understand its limitations. And, if the problem didn't quite fit the formula, they were dead in the water. While they had engineering degrees, I considered them mechanics.
> A mechanical engineer I know needed to design a gear to mesh with an outer ring gear. He uses proprietary software to define the shape of the gear, entering necessary parameters and the output is generated into a CAD file.
Could he design the gear without the CAD tool? If he could, he's an engineer. If not, he's a mechanic.
P.S. I'm all for using labor-saving devices. But they are not a substitute for understanding.
P.P.S. The guy who programmed the CAD tool is an engineer.
Another "engineer" spent a couple weeks trying to eliminate the noise in a circuit, essentially trying things at random. Finally, an actual engineer was called in. In 10 minutes, he had calculated an RC circuit to fix it, and the noise went away.
Having an engineering degree doesn't guarantee competence.
Engineers do that too.
A structural engineer I know uses software to design beam strengths in buildings. He understands what the software is doing, but he didn’t write the software and he uses the outputted parameters at part of his designs.
A mechanical engineer I know needed to design a gear to mesh with an outer ring gear. He uses proprietary software to define the shape of the gear, entering necessary parameters and the output is generated into a CAD file.
Both are real engineers working as independents, but neither meets your definition.
I design a JavaScript framework that I use, the process of developing that meets my definition of engineering. I call a huge variety of functions without needing to know any of the internals. If I need to, I can go as deep as I wish to understand those internals (my background is assembler, followed by an EE degree, followed by embedded software, followed by business software). An engineer doesn’t derive everything from first principles, but they breath compromise and parry with conflicting constraints: they have the judgement to go down rabbit holes when it is necessary.