Live data from Hacker News

Introducing Stack Overflow Documentation Beta

blog.stackoverflow.com

101–110 of 136 posts

Re: Introducing Stack Overflow Documentation Beta

#101
post #88

Earlier quoted context omitted.

Put the content AND the link, instead of just the link. This way, if the link changes the info will stay in SO.

Wouldn't that be a copyright violation?

Like in any other writing, a short quote is fine. If it's long, then you may have to summarize the content in your own words.

Re: Introducing Stack Overflow Documentation Beta

#102
I'm actually very conflicted about Stack Overflow in general and of course the new documentation section as well.

For whatever reason I answer many (most?) of the WebGL questions. At some point I felt I needed to make longer form answers with better working examples so I made http://webglfundamentals.org

But, now there's this huge conflict. I spent a couple hundred hours on making webfundamentals.org but when someone asks a question on stack overflow I'm not supposed to just link to whatever I wrote. I instead I'm supposed to effectively transfer all my content to SO. Something about that just feels wrong. SO is making money from the content I created which feels a little weird (yes I know I get other people's content back). Also, while I get that SO's gamification is part of what has made it so successful it's also feels like it turns many things into a competition. I try to tell myself don't worry about those points I'd be lying if I said they didn't affect me at all in various ways.

Taking all that and adding to documentation, as an example, when I contribute to MDN I feel like I'm doing something purely positive. But if/when I contribute to SO Docs I already know I'm not going to feel the same. One reason is because SO Docs will be making money from my work. The only thing I get in exchange is some "score" on my name I can maybe use to get a job. Maybe that's a fair trade since I don't get a score on MDN?

I'm not sure how to make my point. I love that I find answers on SO but something just doesn't feel right and I don't know how to express it.

Re: Introducing Stack Overflow Documentation Beta

#103
post #95

What I'm most worried about is the duplication between the canonical documentation of a project and the StackOverflow one. As the author of an open-source project, I try my best to write a great documentation, and I would be a bit annoyed if people started to add examples to StackOverflow just to gain reputation there instead of contributing to the "official" one. Also, SO is ranked way higher than the smaller-projec…

First of all a personal heartfelt "thank you" to you for contributing towards open-source project. It's because of people like you, who rise above the personal benefits to a significant extent and contribute to the open/free source movement, the people like me from the third-world can hope to learn anything significant without fearing about the costs involved. So I do appreciate your concern about SO grabbing all the…

The documentation of a lot of projects is really bad, I know, and something is needed to improve it.

I think though the efforts spent on duplicating documentation on SO is just wasted: why don't you contribute back to the canonical one? Usually maintainers are just happy to merge new documentation chapters or examples.

Re: Introducing Stack Overflow Documentation Beta

#105
post #95

Earlier quoted context omitted.

First of all a personal heartfelt "thank you" to you for contributing towards open-source project. It's because of people like you, who rise above the personal benefits to a significant extent and contribute to the open/free source movement, the people like me from the third-world can hope to learn anything significant without fearing about the costs involved. So I do appreciate your concern about SO grabbing all the…

The documentation of a lot of projects is really bad, I know, and something is needed to improve it. I think though the efforts spent on duplicating documentation on SO is just wasted: why don't you contribute back to the canonical one? Usually maintainers are just happy to merge new documentation chapters or examples.

Just editing something on Stack Overflow is much quicker than git cloning something, figuring out the documentation build that they have, editing, issuing a pull request, watching that pull request linger for ages, get a nit-picking comment, fix it, watch it linger for ages, and then finally merged, but not released, and then waiting for ages for the release. Obviously, sometimes the experience is better than that, and sometimes it's worse, but SO Q&A is much more consistent and immediate, and I imagine SO Docs will be as well.

Re: Introducing Stack Overflow Documentation Beta

#106

I'm actually very conflicted about Stack Overflow in general and of course the new documentation section as well. For whatever reason I answer many (most?) of the WebGL questions. At some point I felt I needed to make longer form answers with better working examples so I made http://webglfundamentals.org But, now there's this huge conflict. I spent a couple hundred hours on making webfundamentals.org but when someone…

Links to what you wrote are welcome on SO and always have been, but link-only answers are not. Just summarise what you link to, and then recommend the link for the full answer.

Re: Introducing Stack Overflow Documentation Beta

#107

Stack Overflow's point system is really annoying. I've been programming for around 10 years, but because I don't participate much I can't even comment on an answer. A month or so ago I was stuck on a problem and thought I'd go through a tag for something I'm familiar with, and submit some answers to try and get enough points to be able to fully use the site. One answer had a new programmer following a tutorial and us…

I remember that phase as well. It was frustrating, but it was worth it. Don't waste your time on the front page, just post questions and answers that are personally useful in your work, and eventually, you'll get the 5 upvotes needed to be able to comment everywhere.

Re: Introducing Stack Overflow Documentation Beta

#108
post #47

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…

I 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-... where author trying to answer their best on "How to start coding?" and user reading and voting for their favorites tuto.

Re: Introducing Stack Overflow Documentation Beta

#109
post #47

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…

(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/vim/topics

Re: Introducing Stack Overflow Documentation Beta

#110

Really curious to see if this succeeds, fails like discourse or gets overrun by what I consider to be a major destructive faction of nitpicks and deletionists on SO.

Has Discourse failed?

Tell me about how it compares in usage to any of the solutions it set out to replace :-)

Or tell me about where people are using it to discuss every question that is not fit for SOs questions/answer format.

Post reply on HN