[mock-possum]

Yeah honestly I know I’m capable of asking those kinds of questions, but I’ve been realizing lately that I just don’t want to. I want other people to figure their shit out first, then come to me when it’s ready to be built.

[chiefalchemist]

Few users / clients actually know tho'. They think in wants. They think in - because of past disappointments - what they can get. They think in what they think the boss wants. They rarely think in actual biz needs.

You can give them *exactly* what they ask for and still be wrong. The user / client isn't going to admit that. Nah. They'll just play the "Damn IT" card and it'll be back to the drawing board but now with a shit load of tension.

It's best to ask - sooner rather than later.

[another2another]

But expecting anybody to know all the details about a request, as well as the consequences to other bits of functionality in a system (especially if it's still being built) is unrealistic.

Most people have a vague idea of the outcome they want, and the reason for it. They also quickly know what they don't want _once they see it_

And that's why agile and iterative development is actually great for GUI based user interactive app development.

[PH95VuimJjqBqy]

well shit, you should just roll over on your back and cry until someone puts a bottle in your mouth then.

One of the advantages of being helpless is not taking responsibility.