There's a spectrum, right?

On one end of the spectrum you've got presumably you, who brings a sketch or prototype to engineering, and has a reasonable discussion about what can or cannot be made production ready on what timeline, with what budget.

On the other end you've got people who bring a half baked prototype to a couple engineers, demand it be in production next week, and then escalate and make a big scene when there's pushback.

No engineers tend to complain about the former. The latter is stressful as hell

It requires both sides to play nice. Engineers have to be relaxed about it but the folks asking engineers for things need to accept that it's not as simple as the prototype may make it seem. If there is mutual understanding and respect things go well. If there is any hint of us vs them mentality, it goes sideways.

It's fine if everyone realizes they are rough sketches, specs, or prototypes. But programmers have hubris, developed through many years of writing shitty code they have to burn to the ground. Other professionals often don't have that hubris. The power of writing code goes straight to their head. Programmers are trying to write the least code possible to do what they need to do, because they know every single line is a liability. A company liability, and a personal liability, because they're the one that will have to fix it when things go wrong. I think people who are not programmers don't always understand that, and they are extra isolated from it because ultimately they don't maintain or fix their stuff. Some other poor soul does, so out of sight out of mind.