The perpetually want a set of requirements. And they get upset if a new requirement is added later.
I agree that this is a good, if terse, summation of the basic conflict.
Poorly named, most "Computer Scientists" are NOT scientists. There is no application of the Scientific Method to solve unknown problems.
Instead, they are Software Engineers trying to adapt known problems to solution by a versatile tool (the computer). No Science. Just Engineering.
I see software as a way to explore a space. Model it. Determine what more modeling is needed. You are constantly trying to do something that usually is beyond what is computationally possible so you have to figure out what approximation is going to work. What has to be done at full scale and what can be done at lower resolution. Mock up stuff.
This sounds like Science. Very indeterminate. And, not easily estimated. Business managers that employ Software Engineers demand estimates.
And schedules. And progress reports.
Also, users of developed software often have - shall we say - hazy views of what is really needed. This can lead to disappointment when the software does not meet expectations.
Thus, to avoid being placed in a bad position, Software Engineers demand detailed requirements, so that they can make accurate estimates and avoid end user disappointment.
You live in a different world, pal... Not necessarily better or worse, but different.