If you drive a car, have you read the entire owner’s manual for every car you’ve owned? If you’re a homeowner, how about your hvac system? What about your system shell? Your compiler(s)?
At some point you need your tools to be intuitive enough that you don’t need to read an entire manual in order to do your work.
I suspect this attitude of “read the fucken manuel” comes from when tooling was simpler and you could actually read all the manuals (or buy a book) to learn every small bit of it. Today, I’d be surprised if someone actually read all the Windows, .Net, and Powershell docs before attempting to write a small script.
Heck, even simpler things like Python have massive docs beneath every layer of them. You don’t learn everything from the ground up anymore, only the relevant parts to your use case.
If you drive a car, have you read the entire owner’s manual for every car you’ve owned? If you’re a homeowner, how about your hvac system? What about your system shell? Your compiler(s)?
At some point you need your tools to be intuitive enough that you don’t need to read an entire manual in order to do your work.
I suspect this attitude of “read the fucken manuel” comes from when tooling was simpler and you could actually read all the manuals (or buy a book) to learn every small bit of it. Today, I’d be surprised if someone actually read all the Windows, .Net, and Powershell docs before attempting to write a small script.
Heck, even simpler things like Python have massive docs beneath every layer of them. You don’t learn everything from the ground up anymore, only the relevant parts to your use case.
I miss the days when every package came with a man page.
Every respectable package; don’t come at me, pendants.
Did you do that on purpoise? :3
No, not on porpoise.