Hacker News Reader

Comment by keithnz | Hacker News Reader

I quite like the idea, we have confluence at the moment, this would take a whole section of what we do in confluence away and make it better, but it kind of becomes a bit of mish mash of systems and the pricing would double

View on HN

I'd guess it sorta depends on whether people spend more time on Confluence or Stack Overflow. If questions are already getting answered and used, Stack Overflow for Teams isn't likely to do better at this stage in its development. On the other hand, if questions aren't getting answered or if people forget they exist, it might be worth trying out the Stack Overflow product since developers are likely to end up there regularly.

(Disclaimer: I have 0 experience with Confluence and I'm a Stack Overflow employee.)

We also use confluence, but its irritating as hell having no easy way to see how recent subsections of each page are.

Is this info good or bad? The page was updated yesterday, but this part was written two years ago.

Worse, its down to arbitrary decisions by individuals what goes where, and search for answers and you get... surprise! Old pages no one wants to delete 'just in case'.

I think the real value here is that old answers are still important, but maybe they're not the right answer any more.

Confluence (and the wiki format in general) just fails time and time again at offering relevant timely information.

I get it, its like source control; just delete that stuff and update the page, its still in the history... but people just dont.

How is Stackoverflow for Teams going to be any better?

One of the biggest problems SO sites have is the prevalence of outdated info no one will ever update or remove.

We use a static website. That way you can do a git blame to see what line was last updated when. And it allows for separating the change from the approver.

Reply on news.ycombinator.com