|
|
|
|
|
by zemvpferreira
959 days ago
|
|
I might be misreading but I think you're missing the forest for the trees. It's not about the upfront planning, meetings or whatnot, those are consequences of prior criteria. This is what engineering is: 1-A practical problem is being solved in a scientific way. 2-Safety, repeatability, understanding of the how and why of the solution are non-negotiable. 3-The person solving the problem has been credentialed as an engineer in both ethics and scientific rigour. 4-Because he is credentialed, there is non-waivable liability for the engineer signing off on the solution if it fails. No whining or superiority intended, but if any of the four criteria is missing, you're not practicing engineering. In my experience most software development is missing all four. That's not necessarily a bad thing, it's just that most software development isn't engineering. Again, nothing intended by it. There's no superiority to engineering over development. |
|
It's like how the word "literally" has come to be used as an intensifier, not strictly in the (ahem) literal sense of the word - and "objectively" is well on it's way down the same path. You can be angry about that, but it's not going to stop the continuing evolution in how the world uses those terms - and "engineering" as a term is exactly the same.