This goes along in the hall of fame with the "how hard can it be", Turns out, if you want to do it right, more often than not, very hard.

Lol. I think a disconnect that engineers often have with product people is that product people want it to be done now (right or not) and engineers want it to be done right, which obviously takes more time. But I think a good engineer knows how to get it 80% of the way there quickly, and knows which 20% is ok to sacrifice or take on as tech debt.

Alas I'm not one of those engineers, but I'm fortunate enough to work with some.

There is a lot of that, but there is also the fact that you can get lulled into a false sense of "it is working" in general the motto is 90% of the work in 10% of the time and 90% of the time to get the 10% more done, and the devil is always in those 10% that often hinge on decisions made during the 90% phase.

It also depends on the requirements, and what the actual thing you want done. For software, sure you can probably patch it and there are some inconveniences you can live with depending on the clients requirements, for hardware... a little bit tougher... But it still depends on what is being done and what are the constraints, as long as people are reasonable, usually, it works out... Except that people rarely seem to be reasonable...