Re:You've only added two lines – why did that take two days?
by addicted44 on Tuesday July 14, 2020 @04:22PM
(#23837315)
Assuming the reporter is internal, you don't need them to go ahead and type out everything. A quick call with a screen share is all that's needed.
Not even reaching out (again, assuming they are internal...if they are external then there are many other considerations) is just not smart IMO.
When working as a support agent I have spent a lot of my time acting as a filter to stop making the end-users go mad with all the requests from the devs and preventing the devs from being flooded with crap reports (of course, some always slip through). That means a lot of time spent on reproducing and testing (and sometimes pointing out where the bug is in the code, even suggesting patches). But very few organisations pay for that knowledge and very few allow agents to muck around for a day with a tricky issue to make sure the devs can fix it without a major hassle.
It is very easy to ask for more information as a dev, and very often it is needed, but a lot of the time it is just pushing the cost to the end-user when a minimal amount of detective work (or even a single quick test) would do the same and save everyone a lot of hassle. I would argue that in a lot of time when we, as devs, ask for more information we do it to push the issue into the future and to save ourself a minuscule of work now, not to have a quicker resolution.