Yeah, many people don’t want to read and understand, just copy and paste.
I saw that in a lot of people I worked with on projects, they just look for something to copy and paste from the Internet without even trying to understand what it does. Just looking for some command without even paying attention to the text around it.
I remember one girl once that I gave her the link to the documentation explaining step by step what she needed to do, a link I had to find myself and pass it to her, of course, even when it was her task. Those steps included some alternatives like “if you are in this situation, run this command, but if you are in this other situation, run this other command” but she ignored all the instructions on that page and started copying and pasting every command that was found there. When I asked her what she was doing and why she was running every command there without reading the explanations around them, she said she thought she just had to run all the commands on that page.
The amount of times someone has asked me why something doesn’t work, and I’ve silently pointed to the sentence or paragraph next to the code snippet they’ve copied…
Oh, yeah. I had this situation so many times in this same project. Even pointing them to the documentation and telling them to read it because the explanation was there didn’t even work because they just wanted immediate answers. Sometimes I even had to join them on a call and tell them to stop, open the link on a screenshare and read it out loud to me to make sure they were actually reading it and not just telling me they read it.
It felt like teaching to read to first-grade schoolers.
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.
What people? If you are referring to the people I mentioned in my example who don’t read the text next to the commands explaining what they do, that seems to be also the output tealdeer produces, so I don’t know how it would help.
They’re man pages that are significantly reduced and only include the common commands. People who copy paste, do so usually because the directions or manual are too long and it intimates their feeble minds.
I’m starting to see this a lot. Some man-pages are very verbose and one might not have the time, but for the most part, opening a man page and lessing through it doesn’t take too long, and it’s usually up-to-date
You need to read them apparently? I don’t know, this is weird
Yeah, many people don’t want to read and understand, just copy and paste.
I saw that in a lot of people I worked with on projects, they just look for something to copy and paste from the Internet without even trying to understand what it does. Just looking for some command without even paying attention to the text around it.
I remember one girl once that I gave her the link to the documentation explaining step by step what she needed to do, a link I had to find myself and pass it to her, of course, even when it was her task. Those steps included some alternatives like “if you are in this situation, run this command, but if you are in this other situation, run this other command” but she ignored all the instructions on that page and started copying and pasting every command that was found there. When I asked her what she was doing and why she was running every command there without reading the explanations around them, she said she thought she just had to run all the commands on that page.
The amount of times someone has asked me why something doesn’t work, and I’ve silently pointed to the sentence or paragraph next to the code snippet they’ve copied…
Oh, yeah. I had this situation so many times in this same project. Even pointing them to the documentation and telling them to read it because the explanation was there didn’t even work because they just wanted immediate answers. Sometimes I even had to join them on a call and tell them to stop, open the link on a screenshare and read it out loud to me to make sure they were actually reading it and not just telling me they read it.
It felt like teaching to read to first-grade schoolers.
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.
And this is why I recommend those people to just use tealdeer/TLDR
What people? If you are referring to the people I mentioned in my example who don’t read the text next to the commands explaining what they do, that seems to be also the output tealdeer produces, so I don’t know how it would help.
They’re man pages that are significantly reduced and only include the common commands. People who copy paste, do so usually because the directions or manual are too long and it intimates their feeble minds.
I’m starting to see this a lot. Some man-pages are very verbose and one might not have the time, but for the most part, opening a man page and lessing through it doesn’t take too long, and it’s usually up-to-date