Programmers are "hard-wired" to solve problems.
Good programmers will try to solve the "right" problems.
Just supplying what someone is asking for is [often] the wrong problem to solve.
In the days when MS Office automation was all the rage, you'd get a string of questions, usually over the course of a few weeks, asking how to do "this" in one Office product, then "that" in some other product, then something else again in another one. Each of these are quickly dealt with, but the "problem" - not yet fully stated - isn't solved. They keep coming back for the next "link" in their chain.
If you stop them and ask them "Why?" then they have to back-track and explain more broadly what they want to achieve and not just describe the problem immediately in front of them. (BTW, Programmers suffer from this just as much as (if not more than) anyone else, to which fora like these bear testament).
The user's chain of "Getting the data from the big Database into Access, then into Excel to massage it a bit, then across into Word so they can mail-merge the results and Email these out to people every week" is quickly replaced by a batch job that does all of that, with the results sitting in people's inboxes first thing on a Monday morning, with no manual User involvement at all.
Users like that.
We need to know where you're trying to get to, before we can offer you the best way to get there.
Alternatively, (to paraphrase Monty Python):
"Do you want the 5-minute answer or the full half-hour"?
There's no point the Programmer rattling off all the minutiae of a particular function when you only want to know whether it will cope if you feed it a number with three three decimal places.
Knowing your perspective can often radically re-shape the answer you get.