As a technician, if I see something that looks wrong in a product, I point it out and make a report. But it's the engineer that makes the decision to fix it or to Use-As-Is. If that part fails and kills someone, the responsibility is on the engineer that signed off, not me that did the work.
That's the core of being an engineer I think, taking the end responsibility for a product.
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.
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.
computer programming (e.g. writing code) is not software engineering. Any "software engineering" that took place, if any, would occur before the first instruction is even written for a production system.
a computer program consists of the the instructions to be executed by a CPU to manipulable it's state to hopefully solve some problem. This serves the same purpose as the plans that an engineer would hand to a builder, e.g. place this beam here and use these screws to secure it to that pole. After a builder has completed the construction of the building, the program has finished execution.
The CPU is the builder and the program instructions are the plans. The act of writing the program is the same as an engineering writing their plans; except instead of code they use diagrams or whatever.
the engineering parts came into play in developing those plans. that is, before the instructions were written. this is where the conversation should begin to explorer what is software engineering. we don't know how to engineer software.
Great comment. Designing a bus protocol or the C++ standard is definitely software engineering.
Programming is akin to trades like construction or production technicians. However, usually a software developer is involved in the design, implementation, production and maintenance whereas the former are only involved in last two.
That is because programming projects are subject to change in production. Waterfall is too slow for many businesses and the implementation winds up being a mess despite the linear workflow. Iteration is necessary to improve any design.
Designing and analyzing algorithms is usually considered the work of computer scientists, I would think. Software engineers are something different.
So if you design a sort function intended to be optimal for your given workload, then you are an engineer and not a computer scientist.
> An engineer writes the sort function, and can tell you its complexity and why the algorithm he chose (or invented) is the most appropriate one for the particular sorting task, and what the cases are where the sort will perform poorly, and why.
So what of the people that can do this but don't have a degree? And what of the people that have a degree in engineering but can't do this? Are both also engineers, or are neither of them engineers, or is one an engineer but not the other?
I've known engineers that were no better than mechanics. And a couple (very rare) mechanics who could do engineer work, and would be engineers in my estimation.
Consider real engineering at Boeing. There are engineers and technicians (aka draftsmen) working side by side. They are often doing the same work. The difference, as far as Boeing is concerned, is the engineers have a degree in engineering and the technicians do not.
But if they are often doing exactly the same thing, what's the real difference?
Think of it another way. Think of an auto mechanic. He can fix your car. He can take your car apart and put it back together. He can customize it. But is he an auto engineer (who often does those tasks, too)?
Nope.
A programmer, technician, mechanic plugs numbers into formulas, follows instructions and procedures and practices laid out by an engineer.
An engineer derives the formulas, writes the instructions, develops the procedures, and refines the practices.
For example, a technician builds a band pass filter by using a circuit he's already used before and knows works. Maybe he'll tweak the RC values. An engineer will drive the RC values needed by understanding the calculation. The technician may use calculation (though they rarely do), but they don't understand where the formula comes from. An engineer does.
In software, a programmer calls a sort function from the supplied library. An engineer writes the sort function, and can tell you its complexity and why the algorithm he chose (or invented) is the most appropriate one for the particular sorting task, and what the cases are where the sort will perform poorly, and why.