I Hate Screenshots of Text

2 hours ago 2

During the course of a regular working day, I receive a lot of screenshots like this from well-meaning colleagues:

A screenshot of some text

It's almost always in a chat about some issue that occurred in the code, or perhaps code that's somehow related to the code in the screenshot, or… well, how am I supposed to even know? Upon seeing this code, I might think, “How is slug defined? Is slug being used to create the baseUrl? Why is the domain name hard-coded in that URL? What happens if an exception is thrown? What module is this code even in?

I have to either very carefully type some of the code into a search box or (these days) get my coding agent to find the relevant module for me.

Why couldn't my colleague have just used copy & paste? I could have seen a bit more of the context, even if the same lines were selected, and I could copy-and-paste that text into my IDE's search function so much more easily.

In fact, why couldn't they just send me the file, or even a link to the file (since everybody and their dog use GitHub, anyway).

It gets worse. Sometimes, I'll get a screenshot of an error log. “Hey, Paul, the build is failing. Can you look at this?”

A screenshot of some build errors

What were you building? What line did it fail on? What even was the error?

Of course, if I do a full rebuild of everything on my workstation, it'll succeed.

It would have been SO easy to just copy all of the error log, or even dump the log into a file, and just send me that.

Me reading a screenshot of some build errors

Please, don't take screenshots of text unless it's to demonstrate a cosmetic issue related to the display of the text, or there is truly something relevant about the content of the screenshot that would be lost in a purely textual context.

Read Entire Article