3 ms·
The thing is, non technical users usually don't actually know what they want. To me this is half of the skill as developer is trying to get what they need, not
by collyw 12y ago
The thing is, non technical users usually don't actually know what they want. To me this is half of the skill as developer is trying to get what they need, not what they think they need.
For example, my users ask for "another excel to upload this to the database". I know that excel is a terrible error prone solution, so refused, and gave them a web interface, with immediate feedback about errors. They are pleased with the result, because the information is taken from the database, not cut and pasted out of the database into excel, then parsed again. Speaking to the user is important.
The other problem is time estimation, which as most developers will tell you, is not easy.