I'm a software developer :-) What we usually call "software engineering" often doesn't take these kinds of issues into consideration. Even when I've worked with actual engineers (including P.Engs) the amount of "engineering" I've seen in my career as been vanishingly small. For example, I've worked in real time systems and we've had a performance budget. The number of times I've asked, "What did you do to ensure this will fit in the budget" and had people reply with something like "My code is fast. I don't think anyone can make it go faster" is ridiculous. Over time I've developed a kind of doubting attitude -- unless I see some evidence that you've done the due diligence, then I assume you've not.
Of course, what's common in my industry would obviously be fatal in other industries. I often tell my wife, "I don't have an unreasonable fear of heights. I have an unreasonable fear of engineers" :-) Still, I haven't died from having a bridge collapse under me yet, so I must be doing something right!
I know exactly what you mean. I used to work with someone who would constantly ask "where's the engineering? meaning where are the calculations, the data that support the conclusion that something would work? Refreshing words to my ears!
Of course, what's common in my industry would obviously be fatal in other industries. I often tell my wife, "I don't have an unreasonable fear of heights. I have an unreasonable fear of engineers" :-) Still, I haven't died from having a bridge collapse under me yet, so I must be doing something right!