3 ms·
In 15 years of programming I’ve never read the docs for anything front-to-back. I look at the docs when I have a specific question It’s crazy to suggest someth
by brundolf 4y ago
In 15 years of programming I’ve never read the docs for anything front-to-back. I look at the docs when I have a specific question
It’s crazy to suggest something this surprising wouldn’t be a problem just because it’s technically in the docs
- sidlls 4y agoThis is unfortunately all too common. I am often dinged by my manager about my throughput when investigating the integration of new libraries because I read the docs, front-to-back, as part of my research and that takes time.
- brundolf 4y agoI don't think it's really appropriate or feasible or even helpful for most things. At least for myself, if I read through the entirety of a language's documentation I wouldn't remember half of it, and I probably wouldn't need everything I remembered. Language and library designs should optimize for least-surprise.
- sidlls 4y agoMost libraries are quite poorly documented (to my taste, anyhow). It is certainly worth spending the time reading at the very least documentation pertinent to the components of the library intended for use.