It’s strange. The man pages contain everything you need to know and even examples ready to use. But people would rather try and fail several times. I wonder what inner motivation makes someone have this kind of process. Is there a reward when you manage to make it work through erring? Psychologists, do you know?
I think it’s that the mental effort required to read the documentation, understanding how a tool works and producing an idea in your mind of how to achieve your purpose with the learning you just got of how that tool works is usually bigger.
Even if it takes more time, the mental effort of copying and pasting examples from Google until you find the one that works is way lower.
And that reminds me of an anecdote with one of the products our customers usually use. There was a problem which was kind of common and it had a discussion thread in the forum on the vendor’s website where somebody suggested that the solution to the problem was rm -rf /var/lib/rpm.
Needless to say, we had a customer who ran that command because they had read on the Internet that it was the solution to their problem without understanding what that command was going to do. And of course they ruined that server which needed to be fully reinstalled.
Until I notified the vendor to delete that malicious advice from their forum, that answer lasted there for years and who knows how many people ran the same malicious command without trying to understand first the disaster they were going to cause.
I bet you could describe a problem, tell them to not run that command, and then put the command there to copy and paste and people would still fuck up their systems.
not reading that essay (/s)
It’s strange. The man pages contain everything you need to know and even examples ready to use. But people would rather try and fail several times. I wonder what inner motivation makes someone have this kind of process. Is there a reward when you manage to make it work through erring? Psychologists, do you know?
I think it’s that the mental effort required to read the documentation, understanding how a tool works and producing an idea in your mind of how to achieve your purpose with the learning you just got of how that tool works is usually bigger.
Even if it takes more time, the mental effort of copying and pasting examples from Google until you find the one that works is way lower.
And that reminds me of an anecdote with one of the products our customers usually use. There was a problem which was kind of common and it had a discussion thread in the forum on the vendor’s website where somebody suggested that the solution to the problem was
rm -rf /var/lib/rpm.Needless to say, we had a customer who ran that command because they had read on the Internet that it was the solution to their problem without understanding what that command was going to do. And of course they ruined that server which needed to be fully reinstalled.
Until I notified the vendor to delete that malicious advice from their forum, that answer lasted there for years and who knows how many people ran the same malicious command without trying to understand first the disaster they were going to cause.
I bet you could describe a problem, tell them to not run that command, and then put the command there to copy and paste and people would still fuck up their systems.