5 ms·
In the footnote of the post they wrote they considered naming it "SO Examples", but didn't. For me at least, using "SO Docs" to name the site is actually much m
by akavel 10y ago
In the footnote of the post they wrote they considered naming it "SO Examples", but didn't. For me at least, using "SO Docs" to name the site is actually much more confusing. As a result, for the whole post I thought it is a dynamic manual, with per-function docs and examples. Only after browsing to the actual site I slowly realized it's not a manual: it's rather a "book" of examples. A list of HOWTOs, speaking in a language of yesteryear. As far as I see, it's impossible to build a MSDN in it. I couldn't add full documentation for one of Go packages here — borders cross vague, overlapping concepts, not clearly cut packages. To make it clear: I don't want to deny that it can be useful — suppose as examples for learning; but when looking for docs, I like being able to browse them systematically.
So, two possibilities: either something revolutionary I didn't fully grasp yet — or Examples, not Documentation.
For now, I much prefer the model of Go docs, MSDN, or PHP manual with user comments — if talking about docs.
- olivier1664 10y agoI agree with you, I was expecting a set of concurrent tutorials. I was hoping a coding version of http://www.mobafire.com/league-of-legends/champion/renekton-68 http://www.mobafire.com/league-of-legends/champion/renekton-... where author trying to answer their best on "How to start coding?" and user reading and voting for their favorites tuto.
- akavel 10y ago(replying to self) Ok, I see now one area where it actually seems to make much sense and looks like it can work very nicely: for stuff like git, vim/emacs, bash, etc. Generalizing, I'd say: for apps/services which happen to have abysmal, irregular UX/API, which often accrued/emerged instead of being designed. A classical reference manual just doesn't work good enough for them, because the "natural" edges/borders in the API are too random and accidental. "SO Docs" as it is now can then organize the chaos, while making it easier to categorize & improve than a typical wiki. http://stackoverflow.com/documentation/git/topics http://stackoverflow.com/documentation/git/topics http://stackoverflow.com/documentation/vim/topics http://stackoverflow.com/documentation/vim/topics