I work with a lot of Windows admins who have to move over to Linux, and this post is extremely accurate. One additional thing I’ve noticed is that because Windows error messages are terrible the users have learned to simply ignore them as there’s no useful information. Getting them to stop and read what’s in front of them is one of the hardest things to do.
Having learned how to use computers via MS-DOS, then growing to mostly use Windows machines, and then moving to daily-drive Linux in the past handful of years, I think the problem is more about context. If I see an error message, it’s not that I don’t read them. Rather, if I lack the context to understand what it is trying to tell me—and more importantly, what I can do to resolve the problem I’m having, I’m out of luck and I’d have to ignore it.
It was when I switched to using Linux that I’ve picked up the habit of searching the error message online, and then browsing the various pages (mostly Stackoverflow, sometimes Arch Linux wiki pages) which might or might not lead me to the context behind the error message. If I get lucky, I could find a clue to resolving my problem on top of understanding what the error message is about. Other times, I end up being even more confused and give up.
And then there’s the monstrosity that is the logs. I’m pretty much illiterate when it comes to them, and reading them might as well be reading arcane records of eldritch daemons keeping my machine working (in a way, they indeed are). Copy-pasting some snippets from them into an online search is a crapshoot. I may find something that fits my context, but a lot of times, it’s for a different problem. It might not even be for my OS/distro/package/version.
I work with a lot of Windows admins who have to move over to Linux, and this post is extremely accurate. One additional thing I’ve noticed is that because Windows error messages are terrible the users have learned to simply ignore them as there’s no useful information. Getting them to stop and read what’s in front of them is one of the hardest things to do.
Having learned how to use computers via MS-DOS, then growing to mostly use Windows machines, and then moving to daily-drive Linux in the past handful of years, I think the problem is more about context. If I see an error message, it’s not that I don’t read them. Rather, if I lack the context to understand what it is trying to tell me—and more importantly, what I can do to resolve the problem I’m having, I’m out of luck and I’d have to ignore it.
It was when I switched to using Linux that I’ve picked up the habit of searching the error message online, and then browsing the various pages (mostly Stackoverflow, sometimes Arch Linux wiki pages) which might or might not lead me to the context behind the error message. If I get lucky, I could find a clue to resolving my problem on top of understanding what the error message is about. Other times, I end up being even more confused and give up.
And then there’s the monstrosity that is the logs. I’m pretty much illiterate when it comes to them, and reading them might as well be reading arcane records of eldritch daemons keeping my machine working (in a way, they indeed are). Copy-pasting some snippets from them into an online search is a crapshoot. I may find something that fits my context, but a lot of times, it’s for a different problem. It might not even be for my OS/distro/package/version.