Live data from Hacker News

StackOverflow for private teams in beta

stackoverflow.com

51–60 of 64 posts

Re: StackOverflow for private teams in beta

#51

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…

I don't understand... why would you want to keep your discussions private to each experiment? Certainly people from other experiments or from other research groups could have very similar interests. Moreover, CERN is funded by the taxes of us european citizens. Does this research really need to be kept secret?

If you study all your life for something, you want it kept held close to you as possible until "the right time" to extract maximum benefit/glory/$$$/fame etc. Wouldn't you?

Re: StackOverflow for private teams in beta

#52

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…

I don't understand... why would you want to keep your discussions private to each experiment? Certainly people from other experiments or from other research groups could have very similar interests. Moreover, CERN is funded by the taxes of us european citizens. Does this research really need to be kept secret?

They have a pretty strict rule about not talking to other experiments to avoid confirmation bias, because in the end they want to verify each other.

Re: StackOverflow for private teams in beta

#53

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…

I don't understand... why would you want to keep your discussions private to each experiment? Certainly people from other experiments or from other research groups could have very similar interests. Moreover, CERN is funded by the taxes of us european citizens. Does this research really need to be kept secret?

Loose lips sink ... Nobel prizes? https://en.wikipedia.org/wiki/Photo_51

Re: StackOverflow for private teams in beta

#54

This could be really useful, however I wonder how teams will find answers to their questions without a private Google channel :) I don't know anyone who actually finds the answer via SO search.

PM on Stack Overflow Channels here. You make a valid point. :) And I can assure you, the success of Channels is predicated on a solid update to the way we do search (as well as better integration with tools you might already be using, like Slack).

Re: StackOverflow for private teams in beta

#55

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 if not, the data you create is yours and you can export it and bail!

Re: StackOverflow for private teams in beta

#56
post #52

Earlier quoted context omitted.

I don't understand... why would you want to keep your discussions private to each experiment? Certainly people from other experiments or from other research groups could have very similar interests. Moreover, CERN is funded by the taxes of us european citizens. Does this research really need to be kept secret?

They have a pretty strict rule about not talking to other experiments to avoid confirmation bias, because in the end they want to verify each other.

Ok, this makes sense then.

The part about "maximizing your glory" is a bit... tiring.

Re: StackOverflow for private teams in beta

#57

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…

I agree, it's better to make a "beta price" or "pioneer price" that you honor, when I see "Free for now" I worry about investing effort in a product that the company does not have enough confidence in to put a price on. Especially one where I may be storing what is private intellectual property and trade secrets. I would much prefer to see a price and a commitment.

Re: StackOverflow for private teams in beta

#58
post #55

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…

the price is a key part of product functionality.

Re: StackOverflow for private teams in beta

#59

This could be really useful, however I wonder how teams will find answers to their questions without a private Google channel :) I don't know anyone who actually finds the answer via SO search.

That, and one gets usually chastised when not finding a duplicate via this search box.

I always check Google results, then look at the yellow suggestions box for earlier posts and sometimes end up with a duplicate (rarely but still).

This usually ends up with a "closed as duplicate" (which is fine) but also sometimes end up with cynical, passive aggressive remarks on Meta.

I love SO (and SE in general). It helped me to understand and discover things I was not aware of.

But Meta is an abomination, full of people with ego issues and heavy complexes. I abhor this community, which is a shame as I stopped to file bugs in SO just because of the toxic environnement there.

Re: StackOverflow for private teams in beta

#60
post #6

Can this do what SharePoint and private wikis can't? My team has tried both with varying degrees of success. In my experience it's always just "easier" for people to pester those who should know the answers.

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