Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Stack Overflow for Teams

stackoverflow.com

Post reply on HN
Print view View original

1–10 of 163 posts

Re: Stack Overflow for Teams

#3

Post by coryfklein »

I'm excited at the potential this has to organize your own internal information that normally lies stagnant on a wiki (or heaven forbid, email) with no context of whether it's still valid or useful to anyone. It seems like it would be particularly useful for organizations with a distributed work force.

On the other hand, so much of StackOverflow's value comes from the economies of scale at hand, and I'm uncertain how well the model scales down to small sized teams or even medium sized companies.

Re: Stack Overflow for Teams

#4

Post by tekkk »

My question is, is this better than your self-hosted wiki? At least that's cheaper and isn't a vendor lock-in. Sure wiki doesn't have the best possible UI and the UX might be too so-and-so. If I were in a position to buy this kind of service I'd still want something more out of it.

Maybe if it offered a way to export Slack threads into SO as questions so they wouldn't get lost. Sure you could generate those questions manually from the thread and maybe prune them a little but I've found mostly people are too lazy for extra-work like that. Anyway that's my first impression, take it as you want.

Re: Stack Overflow for Teams

#5

Post by coryfklein »

tekkk wrote: post #4

My question is, is this better than your self-hosted wiki? At least that's cheaper and isn't a vendor lock-in. Sure wiki doesn't have the best possible UI and the UX might be too so-and-so. If I were in a position to buy this kind of service I'd still want something more out of it. Maybe if it offered a way to export Slack threads into SO as questions so they wouldn't get lost. Sure you could generate those questions…

Nearly every company I've worked at is already paying for a vendor locked-in wiki. Of course, ADDING StackOverflow means they're now paying for TWO vendor locked-in wikis (at least until they can shut down the old one, if ever), but it may be still be a net improvement.

Re: Stack Overflow for Teams

#6

Post by cheath »

coryfklein wrote: post #3

I'm excited at the potential this has to organize your own internal information that normally lies stagnant on a wiki (or heaven forbid, email) with no context of whether it's still valid or useful to anyone. It seems like it would be particularly useful for organizations with a distributed work force. On the other hand, so much of StackOverflow's value comes from the economies of scale at hand, and I'm uncertain how…

yeah, that's definitely a huge product challenge for us!

some things do work differently than stackoverflow.com to help with that - we built integrations to help surface questions to the right people in your team quickly (rather than the shotgun approach on the public site). and we've also built mechanisms to help guide you towards building a successful community (since it starts as a blank slate).

Re: Stack Overflow for Teams

#7

Post by willcole »

tekkk wrote: post #4

My question is, is this better than your self-hosted wiki? At least that's cheaper and isn't a vendor lock-in. Sure wiki doesn't have the best possible UI and the UX might be too so-and-so. If I were in a position to buy this kind of service I'd still want something more out of it. Maybe if it offered a way to export Slack threads into SO as questions so they wouldn't get lost. Sure you could generate those questions…

We're looking into just that type of Slack integration here in the next couple of months.
Post reply on HN