Re:Precision in Technical Discussions
by AnimalMuppet on Friday February 04, 2022 @12:11PM
(#30209524)
One of the nice things about where I work is that QA is a very short distance down the hall. When they tell me "It's doing X", I can walk over and say "Show me". And then I see that they didn't mention that it was in mode Y when they made it happen, and they did step Z on the way to get there. They may not have thought that those pieces mattered, but to the developer, sometimes they do.
[ Parent
| on HN ]
Re:Precision in Technical Discussions
by justin_oaks on Friday February 04, 2022 @03:03PM
(#30212212)
Because of this, screen-sharing capabilities are critical to resolving computer-related problems that people report.
I once got a report from a coworker that he couldn't import a text-based configuration file into an application. I was unable to reproduce the problem. It wasn't until I had a screen-sharing session with him that I saw the problem. The configuration file extension wasn't correct. It looked right at first, but then I realized that it had an extra .txt at the end of it that was being hidden by Windows. The application saw the .txt at the end of the filename and rejected the file.
Nothing wastes time like emailing/texting/chatting back and forth when a voice call and screen share are available.
Re:Precision in Technical Discussions
by spaetzleesser on Friday February 04, 2022 @12:17PM
(#30209616)
“And then I see that they didn't mention that it was in mode Y when they made it happen, and they did step Z on the way to get there. They may not have thought that those pieces mattered, but to the developer, sometimes they do.”
Exactly. You take things for granted and suddenly all your analysis work is based on incomplete or wrong assumptions .