4 ms·
“A picture is worth a thousand words” is an adage many would agree with. People intuitively can ‘show’ you what’s wrong but most non-developers will have a har
by tppiotrowski 5y ago
“A picture is worth a thousand words” is an adage many would agree with.
People intuitively can ‘show’ you what’s wrong but most non-developers will have a hard time phrasing it.
“I press the button and nothing happens” is representative of written bug reports I’ve seen. What button? What’s supposed to happen? What page are you on? How can I reproduce this?
Almost all issues I’ve seen with a video I can reproduce. But I agree that they should be succinct.
- WarOnPrivacy 5y ago> Almost all issues I’ve seen with a video I can reproduce. But I agree that they should be succinct. As long as we retain those opening, over-amplified metal riffs. Jump scares are why I watch tech vids.
- gweinberg 5y agoThat can depend on what it's a picture of. A picture of a block of text is usually not as good as the text as text.
- dahart 5y ago> Almost all issues I’ve seen with a video I can reproduce. Oh yeah, totally, my experience has been that video bug reports are literally a thousand times better than text bug reports. I've worked in console game dev where we even required reproducer videos because they're so much better at showing the context of what happened. Often the text description was wrong and/or wildly incomplete and/or full of assumptions the user made about how things work or what's going on, and the video would demonstrate the issue and allow me to not have to engage in a lengthy back-and-forth conversation trying to understand the situation. > “A picture is worth a thousand words” is an adage many would agree with. I do too, but until now, I had never read that the other way around, that a picture might cost a thousand words. ;)