I really like this informative blog post on unix pipes, but reading the readme would have saved some time.
It contains the answer in a simple form:
`youtube-dl -o - https://youtu.be/BaW_jenozKc | castnow --quiet -`I really like this informative blog post on unix pipes, but reading the readme would have saved some time.
It contains the answer in a simple form:
`youtube-dl -o - https://youtu.be/BaW_jenozKc | castnow --quiet -`But when something arrives I don't read the manual unless a question arises, then I search for it specifically in that section. For example how exactly did that microwave/grill-combo work? What exactly did this setting in the washing machine do?
I mean, people say the same thing about me, but I think that this is because they never even consider picking up the manual when they have a problem, while for me it's normal to tell them to read the manual. Maybe I should tell them "maybe you can find the answer in the manual", instead of "read the manual".
But some don't even look the "getting started mini-manual". This drives me crazy, specially when they then struggle using the scanning functionality of the printer or stuff like that.
Is there anything I'm missing out on, and if I wouldn't read manuals cover-to-cover, what parts would you recommend reading?
Also, assuming many are like me, do you find a lot of quality issues or inconsistencies in documentation just because it's a "tick-in-the-box" exercise to provide a documentation and maybe an overlooked part of the product development?
Thank you!
Numerous times I found warnings of how to use or not a certain product, that further expanded by understanding of how certain things works. Even the most boring product can have instructions that you might don't know and could use to learn them.
Example, my local shop sells tomatoes in a box, written with bold letters, don't store in fridge. I bought from that shop for 2 years, and always store them in the fridge until I took notice of the warning and it pushed me to read why.