Our experience has been extremely positive. We have seen quick adoption and everyone appreciates the answers and questions that we are currently using it for. It has turned into our primary internal knowledge base. I am also very satisfied with their outreach to active users during the development of new features.

I really like how Stack Exchange took the highly successful Q&A format of Stack Overflow and brought it to teams via Stack Overflow Teams. It works well for our company because everyone is already familiar with finding the answers to their questions on Stack Overflow and many of our employees are contributors (as answerers) as well. It has encouraged our employees to contribute high-quality questions and answers to help others with similar questions in the future. The long format also encourage answers with rich content such as images and external links.

Stack Overflow Teams is still undergoing active development. For example, Slack integration (a way to encourage internal adoption) was a little slow to arrive (but it's here now!). During this development period, you just have to be patient. Thankfully, Stack Exchange has a great team that values their users' feedback so the awaited features they ship will definitely meet your needs and if they don't, they want to hear about it.

It has been very beneficial for newer employees with limited HTML and Javascript experience

What our office has benefited most from with Stack is for our more graphic employees that don't know so much about javascript. As a graphic design firm, all of our employees are well versed in Adobe suite and digital design. However, sometimes projects call for implementing these designs with animation through Javascript - when employees don't know where to turn to we always used GITs from Stack.

The interface is definitely difficult to understand for people who have never used it before - once GIT is understood and how to push and pull repositories, it certainly becomes much easier.

Stackoverflow is our go-to issue resolving tool in regards to bugs and not knowing how to do things in code. And more often the only source of good information in regards to specific bugs. Even though quite a bit of the entries are dated.

The amount of information available in regards to programming issues is very nice. This helps a ton in development, and helps preventing having to reinvent the wheel all the time. The indepth-ness of said information is usually quite high, allowing for people to easier understand future/similar problems from that point on wards.

The elitist feel it often gives, which makes it fairly hard to get into the product. However, once you reach a point of understand why, the point of the product has also reached you.

One of the key benefits of Stack Overflow for Teams is the ability to reduce redundant or repetitive work. Instead of each team member having to research and solve problems on their own, they can easily search for existing solutions or ask questions to the rest of the team.

Transform the way your team works and collaborates with Stack Overflow for Teams.Get faster and more accurate answers to your team's technical questions with Stack Overflow for Teams.Elevate your team's productivity with Stack Overflow for Teams, the ultimate knowledge sharing platform.

Collaborate and innovate like never before with Stack Overflow for Teams, the ultimate Q&A platform for your organization.Simplify your team's workflow and improve communication with Stack Overflow for Teams, the centralized hub for all your technical questions.

Stack Overflow for team - helps in collaborate with team also and solve problems from any corner of the world with help of internet. Open source. Easy to use. Save our so much time.

Stack Overflow for team - a repository type platform where ideas and information from different country and corner comes. It provides a platform where we can write our views and we can correct someone by commenting if he/she is wrong. It is used in my team to get knowledge of different topics. It allows us to see a single problem from no of sights. It means if we post single question then no of people gives no of solution according to their way of thinking. Q&A feature is very supportive for users.

On this platform sometimes user get confused in searching exact solution. It must having filter option to get the desired result. Integration issue.

Best documentation software that helps organization to document Question and Answers.

I am very big fan of Stack overflow it started helping from my education and continuing now in my organization. Stack overflow for team is a great knowledge base , when you have some question but that was answered by other colleague long back, all is document and easily we can search about information. I can say it is wiki for organization.

Really no negatives, But there are sometimes i can see duplicate questions, i think they can improve to detecting duplicate question while posting question or creating thread.

Very informative and helpful software tool open to the community.

As a developer, i use this software daily! This is the first place i run to when i stumble into errors that i have failed to resolve! Very open for everyone to contribute and learn from each other.

The software may prove tricky for someone new who doesn't know how to put code in their questions and also how to format the questions on the platform.

i recommended this tool overall any doubt s

when ever i have doubt about coding using this articals Fully supporting and clarified

i think there is no dislikes about this tool very good aritcals and more than two answers is available

I love Stack Overflow and I love their ethic. I continue to hold out hope that if anyone can solve the thorny problem of cataloguing and documenting software development and making it actionable to stakeholders; they can.

Stack Overflow has solved many previous hard problems - Finding relevant content - Making authorship of Q & A easy and targetted

- It still feels like a bolt-on to the Q & A. - It presupposes that useful documentation takes the form of Q & A - In an enterprise; I can't add 'yet another' way to document things. We have five currently; and I can't get Q & A to be 6 (Google Site Wiki; Google Docs; Gitlab Wikis; Gitlab git repos; JIRA)

Our team has benefitted greatly from this tool. Our code is open source which helps us when we are seeking a better way to create enhancements in our application. The User community is very helpful and always provides great ideas for us to consider.

Our Developers love the Stack Overflow tool(s). Frequently, we will go to Stack Overflow to pose a development question or seek guidance on how to proceed on our code base. The user community is wonderful and very helpful.

We have nothing negative to state about this software.

I can kind of get with the idea that we're not supposed to post resources to Stack Overflow, but then I kind of also wish that there were some kind of a "curated" Stack Overflow, where it would be possible for "knowledgeable persons" (by reputation I'm sure) to accumulate "classic" questions and answers in a set of community references, especially such that you could see and easily browse related questions. I'm realizing now that this doesn't exactly address the "overall experience" I've had with SO, but I guess my point is that it can be kind of a pain to find quality related questions when I'm trying to find answers. Google results seem to be the way to go (because tags are generally far too superficial to be of much use), but then Google seems to optimize based on "famous" questions and really new questions, and I find the Google results keep regurgitating the same half-dozen or so questions (some results link the question, some results link the best answer, some results link the accepted answer, etc.). I've got more to say about this, but I feel like I'm digressing, so I'll just leave this comment as-is.

First, let me be clear that it's not clear to me if this is about Stack Overflow or about Stack Overflow for Teams, the latter of which is what brought me to this survey. The survey here in particular says to write a review for "Stack Overflow" (not for Teams), so I'll say this: Somewhere on Stack Overflow is nearly every part of every program I've ever written. It's an absolutely indispensable resource for every programmer.

I'm a Stack Overflow user and a Stack Exchange moderator. The most frustrating aspect of the site(s) is that the original asker is the only one that gets to pick the correct answer. OP's choice of answers gets pushed to the top regardless of community votes, and the question will be continuously bumped to the front page if the OP never picks an answer. I wish there were something like a "community accepted" answer, or a "de facto best answer" in the events where a question has been open for X days and has an answer with a score of Y but no accepted answers, or in the event where the top scored answer exceeds the score of the accepted answer by some magic ratio.

My team maintains an open-source project that revolves around Stack Overflow and the Stack Exchange network. We use Teams primarily as a knowledge base and support hub, which has allowed us to move away from using GitHub issues and wikis for these purposes to a much more appropriate format. Teams also has the benefit for us of being directly integrated into Stack Overflow, where we're all already working, so all our content is right there when it's needed.

Teams follows the same Q&A pattern used on Stack Overflow itself, which many developers will already be familiar with. The Q&A pattern also makes it an excellent tool for knowledge bases, which is how my team uses it - instead of writing The One True Help Article for each KB topic, asking a question for it allows the whole team to collaborate in sharing the nuances they've picked up but wouldn't otherwise have an easy way to share.

Teams doesn't come with the same moderation tools that Stack Overflow itself does. While that's probably not a problem for companies (rule infractions or misconduct can be handled through HR's disciplinary procedures), it may make it not as suited to less formal teams such as those maintaining open-source projects. These projects often require more moderation than a company's use-case would do, which Teams lacks proper support for.

Especially in development teams, there's a lot of information silos - this software helps to break down these barriers and have a single place for all of the documentation relating to your product.

If you're part of the tech world, you've almost certainly come across Stack Overflow. I use the site on a regular basis and was thrilled to find that they were creating a version that I could use for my own purposes. The UI is intuitive and easy to use and when coupled with the quality/voting system, this becomes a powerful tool for storing all of your key business information in a single place. Questions which are asked over and over again will be a thing of the past. It also features some useful moderation tools to ensure that your Team stays on track. Various different notification options also let you tailor what you hear about and how whilst integrating seamlessly into Stack Overflow.

It is missing a few of the useful features for managing content quality that Stack Overflow has. The flagging controls and reviewing are missed.

Can't imagine how things would be without a forum like StackOverflow. There should be more and more developers contributing to make it a forum where it has answer to everything.

The whole idea was just awesome when I came to know about it. Needless to say it's the goto place for any solutions to an extent that StackOverflow answers are more easily comprehendible than going through official documentation. I can't imagine how would people get help and share solutions across without something like StackOverflow. The score system also motivates people to contribute more.

Cannot create tags until some points are gained but that is okay I feel since otherwise tons on random tags would be created.

The same day i started programming the very same day i was aware with Stack Overflow. It is best for me. It helped me many times. And i am thankful for the team.

Stack overflow is good when you somewhere, Some of experts write the solution and best solution will be marked as green. You can also write your solutions and earned points. The best way for programmers to get out of the solution if somewhere stuck. It is good way to explore yourself plus to resolve someone else problem.

It is a gift for all the developers looking for the solution. So everything is good except the solutions which are less reliable and people give them negative marking.