How many times as a programmer do you receive an screenshot and it gives you limited information? Usually taken too far out, or so zoomed up that you can't make sense of what the person is trying to convey.
I present to you the Art of taking a screenshot. It should be taught in school just like English. It is very similar:
Who: Are you logged in a someone in particular, please if you can include that in the screenshot.
What: Yes, what are you wanting to show -- if you just snap the entire screen or zoom so far in, it is going to be hard to tell. Take a picture and then mark it up in an Editor to highlight what or where the issue is.
When: Can you include the date/time of when this happened?
Where: What url were you using - you know sometimes we have a dev site, a stage site, a prod site. This all matters because the code is not always the same everywhere!
Why: Again, mark it up in an editor, maybe take multiple screenshots.
Hope that helps someone out there!
No comments:
Post a Comment