[chthonicdaemon]

Most people really cannot tell you what they want in any reasonable way. So expecting good specs for software without a very laborious interview and review process is pure wishful thinking. People "know what they like when they see it", so spend time rapid prototyping.

Smaller and more recent: iTerm has deep tmux support. Just do `tmux -CC` to start your session or `tmux -CC a` to attach to it and you don't have to memorise all the tmux commands.

[pydry]

Also half of those people will "tell" you what you need to build and you need to work backwards from there to figure out what their actual problem is before working forward again to figure out what you actually need to build.

[scruple]

Dealing with this at work right now. A newly promoted lead is struggling to delegate and all of the work coming out of his team right now is instructions on how to do what they believe they want. Very frustrating!

[sumtechguy]

> Most people really cannot tell you what they want in any reasonable way.

But build them something and suddenly they know exactly what they want and what you built isnt it.

[snowwrestler]

This is the origin story of agile software development.

You can’t avoid building what they don’t want, so might as well do so as fast and cheap as you can.

[sumtechguy]

Then the flip side is 'oh i love what you built'

uhh wait a min that was an utter rubish version. 'no no no its great'. now you are kind of stuck with it.