3 years later just as relevant.
A lot of the time I find users have an issue and a theory as to what is going wrong and ask for a report to confirm this. You spend days making it pretty because you have standards. The report confirms or denies their theory and they ask for some revisions. This can take several rounds of back and forth through formal service desk requests. They then ask for the report weekly to validate the changes they implement have the desired effect but never ask for the report to be cancelled. The whole process can take months of back and forth and weeks of Dev time. If you had just sat with the user and cranked code in the database tools in a pair programming session, not only would they have a greater appreciation of what you do, but you will have saved everyone a great deal of time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
3 years later just as relevant.
A lot of the time I find users have an issue and a theory as to what is going wrong and ask for a report to confirm this. You spend days making it pretty because you have standards. The report confirms or denies their theory and they ask for some revisions. This can take several rounds of back and forth through formal service desk requests. They then ask for the report weekly to validate the changes they implement have the desired effect but never ask for the report to be cancelled. The whole process can take months of back and forth and weeks of Dev time. If you had just sat with the user and cranked code in the database tools in a pair programming session, not only would they have a greater appreciation of what you do, but you will have saved everyone a great deal of time.