Live data from Hacker News

Introducing Stack Overflow Documentation Beta

blog.stackoverflow.com

81–90 of 136 posts

Re: Introducing Stack Overflow Documentation Beta

#81

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…

There's one question I saw on Stack Overflow a while back that irritated me. If you copied and pasted the literal question directly into Google, the top hit was directly to the canonical documentation, where you could just scroll down to the clearly marked heading, and copy and paste the sample code and have it work straight away. When I pointed this out, I was berated for not understanding that Stack Overflow is try…

> There's one question I saw on Stack Overflow a while back that irritated me. If you copied and pasted the literal question directly into Google, the top hit was directly to the canonical documentation ...

I see this on SO a lot. Some developers just have different experience levels, and are better/worse at searching through docs.

Re: Introducing Stack Overflow Documentation Beta

#82

Earlier quoted context omitted.

To be fair, that best answer is totally editable by any user to be more informative and/or link to the canonical source of information. There are few projects whose docs have such low contribution friction, for better or worse. And unlike project-specific documentation, it comes in one basic format and set of norms. I also don't think there's a problem of spoonfeeding information to developers. If a developer at Comp…

I was just idling in the Documentation chat channel and based on what I was seeing there, it appears links to sources are discouraged on StackOverflow documentation. Presumably, they're aiming to eventually host new content that's better than what's already out there. I think it's a bit silly -- at least make a Sources section where folks can click to view links to existing docs!

I think the advice is that if you link a url you should include the meat of the link in your post to ward against link rot.

Re: Introducing Stack Overflow Documentation Beta

#83

Earlier quoted context omitted.

Honestly, this seems more like a problem with search algorithms than Stack Overflow. If the canonical documentation is more helpful to more people, it should rank higher. If Stack Overflow Documentation is more helpful, _it_ should rank higher. It doesn't hurt to try to create a resource that might end up being more useful to more people. But until it really is, it needs to be ranked as so.

My point is, why would you duplicate documentation both on the canonical source and in Stack Overflow? For example, Flask [1] has a great and complete documentation, but still someone is starting to duplicate it on SO Docs. Why are we wasting time duplicating things instead of improving what's already there? [1] http://flask.pocoo.org

Never underestimate the human desire to aggregate and have "everything in one place".

Re: Introducing Stack Overflow Documentation Beta

#84

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…

Not being able to comment at low karma is a cause of low quality answers from new users. They post answers that should be comments, and get down voted to hell. I think account age should also factor into a few of the low karma thresholds like being able to comment.

Re: Introducing Stack Overflow Documentation Beta

#85

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…

Agreed. I'm the author of Vorpal.js and already have community-maintained docs on Github's Wiki: https://github.com/dthree/vorpal/wiki

Now I have to duplicate onto another community-maintained Wiki? This is only going to ask for problems. I don't really say "have to" lightly - StackOverflow is most definitely going to yield better search results in the long run.

Re: Introducing Stack Overflow Documentation Beta

#87

Earlier quoted context omitted.

Honestly, this seems more like a problem with search algorithms than Stack Overflow. If the canonical documentation is more helpful to more people, it should rank higher. If Stack Overflow Documentation is more helpful, _it_ should rank higher. It doesn't hurt to try to create a resource that might end up being more useful to more people. But until it really is, it needs to be ranked as so.

My point is, why would you duplicate documentation both on the canonical source and in Stack Overflow? For example, Flask [1] has a great and complete documentation, but still someone is starting to duplicate it on SO Docs. Why are we wasting time duplicating things instead of improving what's already there? [1] http://flask.pocoo.org

internet points!

Re: Introducing Stack Overflow Documentation Beta

#88

Earlier quoted context omitted.

Everyone knows that cool urls don't change, but the problem with links is that not all urls are cool urls. Links rot over time.

So the answer is to not use links at all?

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

Re: Introducing Stack Overflow Documentation Beta

#89
post #72

I really don't want people to start using something like this instead of improving the official documentation. I hate the fact it probably cannot be helped. To "do the same thing for docs that we did for Q&A"? Yeah, except there just was no sane platform for Q&A before. And for docs there is, you know… the docs!

"The docs" are remarkably inconsistent between projects. "The docs" for C# really don't need any help, "the docs" (by which I mean the AFAIK unofficial cppreference.com) for C++ are fine. But even major languages like Python don't have the greatest documentation, never mind the thousands of libraries out there that have wildly disperate levels of official "docs".

Re: Introducing Stack Overflow Documentation Beta

#90
post #88

Earlier quoted context omitted.

So the answer is to not use links at all?

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?
Post reply on HN