StackOverflow for private teams in beta • Hacker News Board

Re: StackOverflow for private teams in beta

#61

Post by napa3uT » Wed, Jul 19, 2017, 8:03 PM UTC

captainmuon wrote: post #16

This would be great for CERN. We do a lot of software development, but most of it is very bespoke, and you are often not going to get an answer on stackoverflow. Also there are confidentially requirements (it would be great if you could tag a post e.g. ATLAS-internal, CMS-internal, and then only people from your experiment could see that post). We probably have tens of thousands of members, so I think we have the cri…

hallelujah brotha, I've seen ROOT questions on so and only CERN people has responded yet it wasn't the best answers one can get

Re: StackOverflow for private teams in beta

#62

Post by sofaofthedamned » Wed, Jul 19, 2017, 8:49 PM UTC

cheath wrote: post #55

CameronBanga wrote: post #36

Really not a fan of the "free for now, we'll give you an idea of pricing in the future". I understand that the team at StackOverflow probably doesn't have an idea on pricing, but it makes it extremely difficult to jump on and try the product. I guess in that situation, our team should just wait until it's out and public. But a lot of these "free betas" go on for months or even years. I know this isn't always the case…

PM on Channels here. I see what you're saying. The honest answer is that we just really need to focus on making sure the product works well before anything else. I really can't speak with confidence about pricing, because we still need to do discovery on what will work best. But what I do know is that it'll likely continue to be free for many people with some premium features that people can pay for if they want. And…

Thank you. But when you say 'export it and bail', what do you mean? Is it exportable in a way I can fire it into something else? Is there a definition of 'exportable'?

Re: StackOverflow for private teams in beta

#63

Post by brianwawok » Thu, Jul 20, 2017, 1:01 PM UTC

pishpash wrote: post #60

brianwawok wrote: post #9

Earlier quoted context omitted.

Of course. You need to teach this with culture. Come over and ask me something I know is in the wikki? Let's sit down and search the wikki together. No match? Then let's type up a result together and enter it for future use. You can't fix a bad process with a magic app, but a magic app can help a process work much better.

How many people are that conscientious?

The people that would want a wiki program to work?

It only takes a few to start a culture.

Re: StackOverflow for private teams in beta

#64

Post by jfriend » Fri, Jul 21, 2017, 5:44 PM UTC

laythea wrote: post #50

Stack overflow may offer lots of fancy features, but, in my opinion, the essence of what they do should be easily achievable by any competent group of engineers. Genuine question - I don't get it, what does this bring to the table? A voting system?

Microsoft built several of these Q&A systems that are "easily achievable by any competent group of engineers". They never really took off until they got Stack Overflow Enterprise. So, I guess it isn't really that easy.

Note: I'm a former Microsoft PM and currently a Stack Overflow PM. My POV comes with bias.