I’ve got to confess, I have for years been guilty if not reading the documentation. I simply go with the flow and hope it works…
But not anymore! And why the change you may ask? We’ll, I’m reading the f…ing documentation on Rocky linux and I’m just blown away from the amount of great information!
If you’ve been guilty of not reading the documentation, let me me know what changed it for you
If you’re not reading the documentation, this is your time to confess!
I prefer to raw dog it first, break it, then tuck me dick and read the paper like the real alpha male
I’m kind of that way. I will browse documentation, get a good idea as to what has to happen, then I raw dog it. Then, after many failed attempts, I go read the documentation. I agree with twinnie@feddit.uk tho, a ton of documentation either assumes you are a certified, dyed in the wool, sysadmin veteran with a wall of certs, or it’s just too sparse for me to put together.
I have a theory: information is best remembered if it is acquired solving a problem.
Play with the new tech, hit a roadblock, read and learn. That way you are motivated, know why you are reading the stuff and also only learn the stuff that isn’t intuitive.
Depending on experience many things are just like something you already know and easy to learn/remember, others are not. Don’t waste your time learning the first.
On the other hand, put me into a room with a teacher, who tries to teache me specifics about a tech I don’t care about and I will promise you, I will learn nothing. Even worse, I will start to hate that tech.