The older I get, the less time passes between starting a new project and reading the readme / manpages for a library.
I find it extremely frustrating how weirdly wrong-density much documentation is. It’s extremely detailed in all the wrong places and often lacks examples for common use cases.
I learned a while ago that news articles are supposed to have increasing levels of detail from top to bottom. Each paragraph adds a bit more context, but the general picture should be contained in the first one. Hardly any documentation follows that pattern.
Learning to learn:
Also tldr: https://github.com/tldr-pages/tldr
Ah yes, they demonstrate my use case in the getting started section. I am an arrogant fool.
In the balkans we have a funny term for that - MUP, which stands for Metoda Uzaludnih Pokušaja, the ‘method of futile attempts’.
Finally reading instructions for the TARDIS?
“Ah! A configure script! I know how to run these!”
./configure && make && make install
Error: cannot find rare esoteric library not in any of your package repositories and is only found as raw source code on a defunct website on the wayback machine from 2002
