I do software development but at my work, our logs are so verbose (so many debug messages that should have been removed before submission but weren’t on a process that takes hours to complete, I’ve seen logs in the hundreds of megabytes for a single test) that I pretty much had to relearn how to find and read error messages. There were a few times I debugged “mystery behaviour” and once I had figured it out, suddenly noticed that there was an error message or warning about the exact thing I spent a while debugging. There was so much text that I just stopped really seeing it as text and saw it more as noise.
Now that you mention it, I have been doing tech support for multiple years and yeah, sometimes I just have to read them the message on the screen.
I do software development but at my work, our logs are so verbose (so many debug messages that should have been removed before submission but weren’t on a process that takes hours to complete, I’ve seen logs in the hundreds of megabytes for a single test) that I pretty much had to relearn how to find and read error messages. There were a few times I debugged “mystery behaviour” and once I had figured it out, suddenly noticed that there was an error message or warning about the exact thing I spent a while debugging. There was so much text that I just stopped really seeing it as text and saw it more as noise.
ironically your post qualifies :^)
This is why i’m VERY generous with newlines and paragraphs.