4 ms·
> They seem dense and dry. I consider that a feature. I loathe wasting my time by having to dig through layers of prose to get some fact. But they are probabl
by jlg23 9y ago
> They seem dense and dry.
I consider that a feature. I loathe wasting my time by having to dig through layers of prose to get some fact.
But they are probably not suitable as a tutorial, they only make sense when you already know relational database basics and need info on pg-specifics.
- paulie_a 9y agoIt's a personal preference I guess. I'd rather hit up stack overflow and find a common English answer to a similar problem that usually includes an example. Django suffers from the same thing... excellent docs, that just seem unapproachable day to day. Basically when I Google something, I'm skipping the first 2-3 official links that in fact contains the info I need, but instead clicking the one that summarized it more plainly
- mgkimsal 9y agoIf it doesn't actually resonate with you, and you don't come away with the understanding you need, it's most certainly not a 'feature' but a 'bug'. I think some projects see dense/thicks docs that keep a high barrier to entry as a feature itself as well. If they're not approachable, they're not 'excellent'.
- paulie_a 9y agoI've been a django developer for a decade and keep hearing from others how great their docs are. I barely ever use them. My biggest complaint is they give examples without any context. I can't look up a feature without knowing 12 other things before