10

I’m Jody, the Chief Product and Technology Officer at Stack Overflow. I’m here today to acknowledge and attempt to address the understandably strong reactions we’ve seen from some community members in response to our recent announcement about the upcoming site redesign and to share some of the thinking behind these changes.

Stack Overflow has been a cornerstone of the developer community for 17 years. It’s a resource many of us have or do rely on daily. The fact that so many people care so deeply about this platform is a testament to the incredible community that has been built here. That said, the platform has also faced challenges in recent years, including a significant decline in user activity. This is something we cannot ignore, and it’s a key driver behind the changes we’re making.

We know that, broadly speaking (and this is a gross oversimplification), this community is made up of two key groups: new users, who often struggle to find their footing; and experienced contributors, who feel they lack the tools to effectively curate and maintain the site. Our goal with this redesign is to minimize disruption to what works while modernizing the experience to serve both new users of the platform and the needs of long-standing, tenured members.

I understand that change is hard and, in this case, complex, especially when it involves tools and workflows that many have relied on and seen work for years. When we talk about rethinking tooling, I want to be clear: this is not about taking things away just for the sake of change. It’s about asking hard questions: what works, what doesn’t, and how can we make things better?

Many of the tools we have today were designed to address scaling challenges from over a decade ago. These challenges may no longer exist in the same way. With that in mind, our intent is to focus on tools that meet today’s needs while taking a hard, analytical look at existing tools to see if they’re still the right fit. While we may not have gotten it exactly right, I can assure you a lot of thought went into this redesign and direction.

I also need to level-set a bit: we’re not trying to do away with the concept of removing unhelpful posts. We care deeply about curation, and have dedicated substantial time and money to building tools for it; and we will continue to invest in this area. But we do have to move away from a world where closing questions is essentially the catchall and default option for curation. We believe we can create better, more precise, more surgical tools that can be used. And we intend to work with all of you to make sure that curators here can take advantage of those tools.

With that said, our attempts to communicate about the necessary change were imprecise and confused the situation. When we said “no more closing questions”, we failed to take into account that that phrase would mean something very different to you than to us. For instance, we effectively draw a line between closing questions and deleting questions. Deleting questions is definitely still in scope for us.

Regarding feedback on quality, you are right: there is still significant work to be done. We intentionally chose to launch this in an early state. We are, as Stack Overflow did in the distant past, intentionally relying on you to help us identify issues so we can more quickly address as many as necessary to reach an acceptable level of quality before moving the site to the new design. I’m here to listen and gather actionable feedback. I want to understand what’s most important to you, what you feel makes the site unusable, and how we can improve the tools you rely on. Specifically, I’d love your thoughts (as answers here) on:

  • Of the design changes that we introduced this week, which design changes are hindering the work that you are doing, and how?
  • The purpose of curation tools: Are they meeting your needs? How could they be improved? - What are we missing?
  • The necessity of all current tools: Are there tools you feel are redundant or no longer useful?
  • Reconfiguring tools: Are there ways we can adapt existing tools to better serve the needs of the community?

I know these are big questions, and I don’t expect all the answers right away. But I want to assure you that this is a conversation, not a one-way announcement. Your input will directly shape how we move forward.

I understand if you feel frustrated or skeptical. My ask is that we have this conversation with a shared goal in mind: to make Stack Overflow the best it can be for everyone who uses it.

Thank you for your time, your passion, and your commitment to this community. I’m here to listen, learn, and work with you to ensure that the future of Stack Overflow is one we can all be proud of.

Looking forward to hearing your thoughts.

New contributor
Jody BaileyStaff is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
30
  • 34
    This is a tad late to ask for after you already ripped a hole into key curation processes, isn’t it? Commented yesterday
  • 28
    I just want to say, before anything else, that I highly respect this level and kind of direct communication. It feels authentic, less sanitized than the initial announcements in a positive way, and just speaking for myself, I really, really appreciate it. Commented yesterday
  • 18
    This is a great step, if it translates to action, i.e. reverting your plans according to the clear feedback you've received. I am not holding my breath, but will keep an open mind. Commented yesterday
  • 10
    "Let me clarify: We're removing closure and replacing it with ....... something." Commented yesterday
  • 16
    I appreciate the direct communication, but I really hope that you can ensure that no unsolicited feature changes will be made, and especially not to "SO classic", before you have collected enough feedback and fully considered them and discussed them with the community (via comments to answers or chats). Most of the answers to the past announcements (the feedbacks you claim to care about) has got no direct response from the company and we just see unsolicited changes again and again. Commented yesterday
  • 26
    @zcoop98 you must be new here... If I had a dollar every time some company representative pretended to do a 180 in community management, finally listening to the community, only for nothing to change after that, I'd have... at least a few dollars. Commented yesterday
  • 29
    "...we do have to move away from a world where closing questions is..." Why do we have to? It's not clear. What purpose do bad open questions serve? I still think this is the wrong way. It will not lead to high quality content or a knowledge base. Is that not the goal anymore? Commented yesterday
  • 9
    @Andras Lol I'm under no delusion of 180s, but I also prefer to interpret earnest authenticity over pretending. I said precisely what I meant: I like the direct communication, stuff that outlines "here's what we're doing, here's what we want to know" over sanitized announcements of "vision" or whatever. That said, I don't at all mean to imply that earnestness alone fixes the abandoned projects and broken promises... The Stacks Editor, Opinion-based Questions, question types, threaded comments, Staging Ground, Discussions, and more all stand as testaments to the existing, rampant dysfunction. Commented yesterday
  • 16
    This is now the third direct post from staff since the beta announcement asking for new input with no indication that the substantial, detailed, and heartfelt ideas and critiques provided on every experiment leading up to this beta has been considered in any meaningful way by the product teams. This, combined with the barely complete rough draft that was released as a 'beta' has understandably left users more than frustrated. Have you looked at the site? Tell us, in detail how you feel it helps new users. Be specific, talk about button position and margins, show that you are actually engaged. Commented yesterday
  • 8
    @zcoop98 the post shows a fundamental lack of understanding of the topic it is discussing, uses blanket platitudes to indicate sincerity, and comes on the heels of very similar posts by more junior staff. There is nothing direct here. Commented yesterday
  • 29
    Could you please actually participate in the site and interact with the community more? I asked why you don't participate in meta or the main sites a year ago, and the response was a promise from you to do so and the CEO's claim that he reads meta and recognizes my username. I've repeatedly asked any senior management members reading my posts to comment that they are, so I have to assume this is just a lie. How can you hope to improve the site when you don't use it yourself, and have no idea how it works? How can you hope to keep the community here if you never interact with them? Commented yesterday
  • 10
    If you actually mean any of this, I'd like to invite you to join a session of CM office hours, as I suggested in the highest scoring answer to that post. I'd to invite you to spectate or participate in SOCVR, SOBotics, and Charcoal HQ. Try asking and answering, and once you get enough rep, try closure and deletion and review queues. In short, understand well how the site works now before you try to change it. Commented yesterday
  • 26
    The first problem I see is exactly that the people in charge of the site does not use the site on a daily basis: "Jody Bailey 101 reputation score" Commented yesterday
  • 8
    Don't model asses in seats. Model answerable questions answered. Users helped out. More questions is useless if no one gives them good answers. This is not a worthwhile KPI. Commented yesterday
  • 6
    "This is something we cannot ignore, and it’s a key driver behind the changes we’re making." ─ Something must be done; this is something, therefore this must be done. Commented 21 hours ago

19 Answers 19

49

Our goal with this redesign is to minimize disruption to what works while modernizing the experience to serve both new users of the platform and the needs of long-standing, tenured members.

OK, but you know, it really seems like the company only focuses on the former and largely ignores the latter. Every time this happens, the long-standing users group gets ignored until the complaints get loud (read: public) enough or your efforts bomb badly enough that you then feel forced to address them or walk them back, like how you are doing right now. What's that apocryphal quote misattributed to Einstein? "The definition of insanity is doing the same thing over and over again and expecting different results."

But we do have to move away from a world where closing questions is essentially the catchall and default option for curation.

I agree as do many curators, but minimizing or doing away with the ability to close questions will not do away with the need to close questions. This has the same bad logic as "if we stop testing for COVID-19, there will be fewer COVID-19 cases!" Sadly, a lot of recent company experiments or site changes on Stack Overflow have followed this same logic instead of actually measuring for useful outcomes.

When we said “no more closing questions,” we failed to take into account that that phrase would mean something very different to you than to us. For instance, we effectively draw a line between closing questions and deleting questions. Deleting questions is definitely still in scope for us.

You talk about doing away with question closure, but not doing away with deletion. So why didn't the announcement discuss how the new site would handle automatic removal of content in place of the lack of closure curation tools. I think we'd all love to discuss ways that the site can automatically handle curation such that we don't need to manually cast close votes, if what you're claiming is true. That would be a very ambitious and interesting technical challenge, the kind of thing programmers love! But why not mention that at all? Personally, I suspect it is because this is a sudden ex post facto justification, not something that was planned from the outset (or did you not run that beta site post by any curator or moderator who has been using Stack Overflow for more than a year or two to see how that bit would go over before posting it?).

Remember the age old adage, "build it, and they will come"? Current top-level company leadership does not seem to understand or remember what was built, or why people came in the first place: that Stack Overflow was built to be a repository for freely accessible, high quality, and eminently reference-able questions & answers about programming languages and tools.

Q: So, why is there such a big disconnect between the company's terminology and the community's terminology?

A: Because the company doesn't use its own product anymore.

Why are your employees not active users on Stack Overflow, asking and answering questions here? Sure, not every role is a programming one, but a lot of them are. Or at least, a lot of them should be, given the industry you're in. And for the non-technical ones, there is no shortage of non-technical network sites. It's important to not just acknowledge that there was a disconnect in language between the staff and the community here, it's critically important to ask why. A company whose staff regularly uses its own product will always be much better positioned to maintain and improve said product for the betterment of all. And with a better product comes happier users and better PR and thus ultimately more customers!

As it happens, we the community also draw a line between closing questions and deleting questions. There's a fair bit of overlap between the two actions, but any seasoned curator will agree that closure does not equate to (even eventual) deletion, and that deletion can/should also happen without closure at times.


Right now, you're hemorrhaging that first group of users you talked about to AI tools because of a perceived accessibility (call it friendliness or elitism or whatever else you want) problem. That makes perfect sense; AI tools always answer your question (except when they can't, or worse, give you a wrong answer and claim it's correct), never present roadblocks to asking a question in the first place (except when you've hit your free quota), and are always polite (except when they encourage or enable abuse, harassment, or death).

The user exodus hasn't been a complete, 100% drop-off because, as it turns out, AI tools are simply not as reliable or trustworthy as real people/experts, and by their nature never will be. But if you get rid of SO's curation tools, or make their usage more difficult, or obfuscate access to them in any way, the latter group you mentioned (experienced, tenured members, or SMEs) will continue to drop and you will have neither incoming new users nor experienced, tenured users.

Specifically, I’d love your thoughts (as answers here) on:

[...]

  • The purpose of curation tools: Are they meeting your needs? How could they be improved? - What are we missing?

  • The necessity of all current tools: Are there tools you feel are redundant or no longer useful?

  • Reconfiguring tools: Are there ways we can adapt existing tools to better serve the needs of the community?

Oh man, today is your lucky day! There are so, so many ways you could address the site's problems. Here are just some of the things often-requested by community, or widely popular with them, that you can do which don't require the Redditification of the site's UI/UX, and that I believe go much further in fixing your core perceived problem of "everything gets closed all the time and new users hate that" (in no particular order):

  • Improve the SO Search functions for the first time since, literally ever. Why does SO search still suck massively? Why are there entirely different search functions used for the main search bar vs. the duplicate closure finder?
  • Give the new Markdown editor feature parity with the old one. Feature parity should be a hard requirement for any feature overhaul/replacement the company does, FYI.
  • Abandon the 2025-era comment redesign and just implement comment threading, even if it's just one-level, under the classic comment design, with a single button to collapse each top-level comment thread. And allow people to @-mention at least two users in a single comment.
  • Overhaul site privileges to work more based on related feature usage rather than reputation. This is something Catija was exploring heavily while she was still here. This means not just replacing rep-gated access with usage-gated access, but also increasing the abilities users have with regard to moderation/curation actions based on the number of related feature uses they have which are 'helpful' or 'accepted'.
  • Fuzz the displayed score of main/traditional questions once they get below -1; just show "< -1" or something until expanded. That way users with moderation capabilities who might have a use for seeing the actual score can still do so, but the default score displayed is never so off-putting that someone has to read -6 or -15, etc., on their own question, however poor a question for Stack Overflow it might actually be. That's one of the biggest instances of friction for new users: seeing their post get 'downvoted into oblivion'; it's insane to me that this was not addressed like a decade ago when Stack Overflow first started realizing it had an image problem.
  • Add higher protection levels to questions, which automatically apply after a question gets more than a certain number of answers and require progressively higher tag scores in the question's tag(s) the more answers there are (if a question has 10+ or 20+ answers, we should not be letting any random user post a new answer anymore).
  • Follow through on improving chat with new features/functionality. We got all excited when you said you were improving chat during one of the sprints last year and so far all I can see that changed is now we have a ToS screen nobody reads and 1-rep users can access chat. Oh and they redesigned how chat replies look but rolled half of it back after a few days.
  • Update the Roomba to ignore comments on zero-score questions with no answers. After one year, just because there are 2+ comments on a question does not mean it is worth keeping around. At the very least, make it require that it have at least one comment by someone other than OP followed by at least one comment by OP, if you're gonna keep those questions around.
  • Reward duplicate closure finders with badges or something. It's only one of the most-requested and upvoted features, given how poorly the search function works.
  • Update the Roomba to ignore accepted answers.
  • Add parent language tags for SO, make them required and separate from the 5-tag count for questions, and restrict gold-tag closure powers to parent tags only.
  • Expand gold-tag closure powers to allow unilateral closure for more than just duplicate reasons. SMEs know when a question needs more details, needs more clarity, or is a subjective matter.
  • Allow mods to migrate questions older than 6 months (require 2+ mods if you need some higher threshold for whatever reason), and explicitly encourage that old, off-topic, but well-received questions to be migrated to their appropriate sites. Why should a question with a score in the triple digits with tons of answers and millions of views languish as closed or historically locked on Stack Overflow when it could be migrated and reopened on, say, Superuser or Unix & Linux or Server Fault? Just because it's from 2015 and not 3 weeks ago? What a short-sided restriction! Not all such questions would be good fits for migration, for sure, but many of them would be. It's a great way to grow those other network sites' traffic, too.
  • Notify users automatically via site notifications when a question they closed is edited.
  • Allow users casting 'Needs details/clarity'/'Needs MRE' close votes (only votes, not close flags) to leave a custom comment posted by the Community user (with mod and staff visibility on who actually authored it) explaining what details are needed, or what is missing to constitute an MRE. A lot of the feedback about SO being unfriendly or 'SO always closes your questions' comes from no direct, clear information (since askers are inherently often lacking understanding in the first place). Sure, people should read the close banners, but those are always generic. Meanwhile curators absolutely don't want to announce that they are the ones during the curating because that often leads to harassment. An anonymous, custom comment option would satisfy both sides' concerns there.
  • Add (optional) version tags to answers. Seriously, why the heck don't we have this? It should have been obvious even in 2008 that this would be needed.
  • Improve the Ask Question Wizard so it actually moves people and their questions to the appropriate site when they post a question we know is off-topic on Stack Overflow, or tell them straight-up that their question is not suitable for Stack Overflow. Alternatively... just finally do away with all the different sites and instead just have one big site where people can filter questions based on 'topic'. Otherwise those other network sites are never gonna succeed or thrive like Stack Overflow once did.
  • Improve the Staging Ground so all new users and a lot more new questions from existing users are sent through that process. This includes applying the Roomba to questions there, and allowing users to edit SG questions that have already been graduated, or overhauling the thing so that it doesn't create a separate question on Main, but rather just 'moves' the SG question itself to Main, and is no longer in the SG.
  • AI Assistant might be great for people who want to use it. But a lot of people don't want to use or even see it, and it's insulting that it's given top billing on Stack Overflow, which was founded to be a place for getting answers directly from human experts. You need to let users hide the AI Assistant/turn off all things AI without resorting to user scripts/styles.
  • Be more clear to users, especially new users, when posting answers that AI-generated content is not allowed here.
  • Make downvotes on Discussions reorder and hide Discussion posts like they do on Main/traditional questions. In other words, Make Discussion Downvotes Matter(TM).
  • Bring back Winter Bash, but make sure it has an opt-out option.
  • Bring back the original SO Jobs (Joel Test and everything, except add a scoring item: "requires or involves using AI tools" would be an X on the scoring rubric) and the SO Developer Story. The Dev Story especially surely took such little bandwidth and support effort that I can't believe you ever got rid of it, given how popular it was.
  • Bring back SO Documentation, just don't award reputation for content contributions there. Do more work to ensure quality (don't make the barrier for entry so low). This means much slower growth/build-out, but it's worth it if the goal is quality and not 'overnight golden performer'. It should have been treated more like Wikipedia and less like gamified Q&A.

If you stop work on UI overhauls that break/remove a bunch of features, and start implementing the things listed above instead, I guarantee you will see people coming back to SO and its reputation in the public start to improve again. You could even still work on native, first-class genAI features, so long as it's alongside and secondary to features like those mentioned the above list.

The list above is just off the top of my head (OK, and maybe the middle of my head, since I started this answer ~2 hours ago)... there are dozens more big ticket changes the community has actively been clamoring for that aren't "yet another site design change", which the community has not been actively clamoring for... ever.

10
  • 12
    Nice list. So who'll start on the new website that follows the above points, now that we're losing this one for good? Commented yesterday
  • 9
    @AndrasDeak--СлаваУкраїні Well Codidact has existed since 2020 and is open-source or something close to it. They're a non-profit alternative by ex-SE users. Adoption has been a struggling point, though. Commented yesterday
  • 5
    "Alternatively... just finally do away with all the different sites and instead just have one big site where people can filter questions based on 'topic'. Otherwise those other network sites are never gonna succeed or thrive like Stack Overflow once did." -- not all other sites are technical or even adjacent to SO. Speaking as a moderator on Puzzling SE, a thriving community which has been at the same size for ~5 years, and which would not like being forced to join with the titan that is SO. We have ~4QPD; we'd be drowned out. Commented yesterday
  • 9
    I strongly support merging all the tech sites. We would do away with all the quibbling about where questions belong, meaning less friction for askers and curators. It is especially anachronistic nowadays as the lines between tech roles are blurred. Also, SO sister sites don’t have a comparable amount of traffic nor a large pool of users who can answer. Commented yesterday
  • 1
    @blackgreen at the very least, provide cross-site rep / privileges sharing so a 30k user on SO can also fully contribute and curate in other tech sites. It will take literal years now to gain the needed reputation in a new site. Commented yesterday
  • 4
    That would probably kill many of the smaller or medium sized network communities. We're not succeeding or thriving cause we've constantly been hobbled, and the company would rather promote other companies or projects over stack exchange or stack overflow - just look at the blog. You'd lose me if you merged super user with SO - and we serve niches SO does not, and where many developers fear to tread. Commented yesterday
  • I once thought one can have a single database of questions of all topics with a single user account and then communities that might be overlapping as views on all the Q&As. No more migration needed. That might have its own problems though. Commented yesterday
  • 4
    @blackgreen "Also, SO sister sites don’t have a comparable amount of traffic nor a large pool of users who can answer" is exactly why they shouldn't be merged. You don't seem to have considerable rep on any other tech site. Rather than doing what the company does (make calls without considering the impact on those affected), ask said small sites first. Giving good-sounding harmful advice to a company that we know won't dig into exploring consequences is irresponsible. Commented yesterday
  • @AndrasDeak--СлаваУкраїні You. Me. Us. All of us. We, the community, need to build such a new, better, site. We can't rely on "someone else will figure it out". Commented 7 hours ago
  • Haven't you noticed how many tech resources including open source projects are being politicised by funded groups? Political promotion is the main priority. Getting access to funds is secondary. And technical excellence, rather than a poor third, seems to be an inverted priority to destroy. Have a look around the world today and see if you don't notice similar trends in other domains. Commented 3 hours ago
44

This doesn't directly answer your questions, but...

I am baffled to see the removal of key legacy curation tooling framed as a scaling issue. Aside from SO, you* have a myriad of much smaller SE sites that absolutely rely on toolings such as closure. Justifying the removal of such tools by a now smaller scale** doesn't match at all the reality on the ground.
A similar feeling crops up for a lot of things you* say about curation. There is a serious mismatch in what you* apparently think tools do and are meant to do, and what the community knows these tools actually do.

Before going for another round of – as you admit yourself – exchanging phrases that would mean something very different to you* than to us, it is absolutely essential that you* define what they actually mean to you*.
Seriously, we tried to tell you* again and again. Since you* apparently aren't listening to what we have to say, it's about time you* start talking.


*You, the company probably known as Stack Overflow (Inc?)

**Which ironically should be a scale you are trying to get away from in favour of previous scale.

1
  • 4
    The large drop in question volume is presumably accompanied by a drop in users doing curation, as it coincided with some massive trust-breaking moves by SO inc which got many people to leave. Maybe some things do just work differently with fewer people and fewer questions, but I hope they aren't assuming that amount of curation person-minutes per question can go up significantly from what it was in years past (when we were chronically behind on review queues, and many duplicates got missed, etc.) Commented yesterday
39

That said, the platform has also faced challenges in recent years, including a significant decline in user activity. This is something we cannot ignore, and it’s a key driver behind the changes we’re making.

Change is needed, but this isn't it. You are actively destroying the site further, not improving it. If I want Reddit or 4Chan, I can get there without your help. I go to Stack Overflow because I like Stack Overflow.

I'd ask you to consider, broadly, why user activity is declining. It's because users find this site less useful than they did in the past. You can blame this on LLMs, and you might not be totally wrong, but you'd be missing something important. It's not just LLMs. SO and SE were declining before LLMs arrived, and their decline accelerates based on the amount of the anger the community has at company actions. You do have a way to make this better that isn't "let's try random things". You just won't take it.

We know that, broadly speaking (and this is a gross oversimplification), this community is made up of two key groups: new users, who often struggle to find their footing, and experienced contributors, who feel they lack the tools to effectively curate and maintain the site.

There's an important third group, the people who just view the site. That is the main purpose of Stack Overflow, at least it was and should be. We aren't a help desk, we are a library of knowledge. If you've decided to change that, please let us know so I (and probably much of this community) can know to leave.

The primary cause of new user's having a hard time is not the existence of curation, and closing specifically. It's because we don't communicate our policies well, there is a lot of robo-reviewing and just-plain-wrong reviewing. These are problems you could help solve. Instead you burn it all to the ground. If people keep accidentally lighting their homes on fire, would you dismantle the fire department or improve fire safety education?

When we talk about rethinking tooling, I want to be clear: this is not about taking things away just for the sake of change. It’s about asking hard questions: what works, what doesn’t, and how can we make things better?

Then what purpose does this serve, other than "hey maybe if we try 100 random things something will increase engagement". What do you feel doesn't work about this system? How do you feel the beta makes it better? Do you honestly believe you know enough about how curation works to have an informed opinion? I certainly don't think you do.

Many of the tools we have today were designed to address scaling challenges from over a decade ago. These challenges may no longer exist in the same way.

This is fair, but also irrelevant. Closure, deletion, and flagging have been part of the site since pretty much the beginning. There is still good reason to keep them. The only real change made in them due to size is reducing the number of close and reopen votes needed from 5 to 3. I'd be open to rediscussing that, but that's not what you are doing here.

But we do have to move away from a world where closing questions is essentially the catchall and default option for curation. We believe we can create better, more precise, more surgical tools that can be used.

I'm not necessarily opposed to the idea of this, but I'd like to know what tools you intend to create? I doubt you will do a good job, but I would agree that curation could certainly be improved. The issue here is that you are not improving curation, you are removing it.

I also need to level set a bit: we’re not trying to do away with the concept of removing unhelpful posts...When we said “no more closing questions,” we failed to take into account that that phrase would mean something very different to you than to us. For instance, we effectively draw a line between closing questions and deleting questions. Deleting questions is definitely still in scope for us.

Nope, it means the same thing to both of us. We are upset you are removing closing because we don't want you to remove closing, not because we think closure = deletion. Actually, you seem to be the one with the misconception of the differences between curation actions.

You have another glaring lack of basic understanding of site function. You seem to be unaware that users (except for moderators) can't vote-to-delete questions that are not closed. So removing closure is removing question deletion, since our 20 or so mods can't realistically get rid of every bad question alone.

The purpose of curation tools: Are they meeting your needs? How could they be improved? - What are we missing?

Curation tools aren't perfect on the non-beta version of the site, but they are worse in every respect on the beta version of the site. Preventing closure is a death sentence for question (and therefore answer) quality. Not allowing us to flag things, even for spam, is just stupid. I'm sorry if this sounds rude, but what you are really missing is a basic understanding of how the site functions. I like to encourage you actually use the curation tools we have for a while. Try asking questions or answering questions. Hang around in moderation chat rooms like Charcoal HQ, SOCVR and SOBotics. Help in the review queues and question closure, once you get enough rep. Actually get an understanding of how the status quo works before you try to change it.

I’m here to listen and gather actionable feedback

A lot of staff members have said that recently. You've already gotten a lot of feedback, you just don't listen to it. If you read meta, as the CEO claims he does, or participate more, as you promised to do a year ago, you should know what we think. It's not hard to find.

The primary reason I'm responding to this post is because it seems at least one piece of my feedback has gotten to someone with some decision-making power, you. I've asked for years to be able to communicate with senior management on meta. What it seems to have taken to get you to make one post (and then ignore the responses) is my days-long campaign of pointing out in every announcement post that the CMs know this is stupid, and have obviously been forced to write what they write by higher management. That's not how it should be.

Reconfiguring tools: Are there ways we can adapt existing tools to better serve the needs of the community?

Yes, absolutely. We've literally given you hundreds if not thousands of proposals all ready. Look at s for improvements to curation tools on MSO and MSE, and choose some well-received one's you think are doable.

But I want to assure you that this is a conversation, not a one-way announcement. Your input will directly shape how we move forward...My ask is that we have this conversation with a shared goal in mind: to make Stack Overflow the best it can be for everyone who uses it.

This is not a conversation. Our input clearly has almost no effect on the final outcome. I'll grant you that you removing Answer Assistant, but I think that was mostly because of the moderator changes on Raspberry Pi, not the community's opinion at large. This is a one announcement. You did not ask us about this, and no one asked you to this. What you think an announcement is exactly, versus a two-way discussion?

I'd encourage you to look at how Jeff Atwood used to propose/announce changes. You'll notice that the communities feedback actually mattered. Even if he decided against it, at least we had a chance to state our case, and really be heard by the people making decisions.

What you are doing here isn't that. You have decreed on order from up high, communicating through 5 levels of people, in spite of everything the community thinks. You have never used any of the systems you intend to change, and appear to lack basic understanding of them. This is not a conversation of any sort.

Perhaps you want to make Stack Overflow better, more likely you just say that. Regardless, it's clear that you aren't. Look at activity metrics. I'll grant that a lot of the decrease in activity has been AI related, but I'd ask to you to note that decrease in activity is faster whenever there is more tension between company and community. You seem to think you don't need us anymore. Maybe you're right, in which case you might as well just tell us all to leave, rather than engage in this facade. If not, then we need to work together, and that won't work if you are going to burn all quality control to the ground.

36

I also need to level set a bit: we’re not trying to do away with the concept of removing unhelpful posts.

If that's the case.. why are we allowing content like this, that one is hardly even programming related and is so obviously answered with "yes, duh?" that it should be deleted? This is just one of hundreds (thousands?) of such cases that have been posted since open ended discussions have began. What tools are you envisioning giving us that will somehow get us back to the point where we can remove unhelpful posts?

We're skeptical because time and time again you show us that you aren't providing tools that are useful to the goals of the network.


Just in case it gets deleted due to me bringing attention to it, this was the sample discussion

enter image description here

6
  • 1
    Or if not remove, then at least filter them out in the way we can currently filter them by disabling experiments. Commented yesterday
  • 7
    @dbc filtering does nothing when we can't even ensure people are posting things in the right categories. This is the advice category, that has recieved many questions that should have been standard Q&A questions. Commented yesterday
  • 1
    That's true. It would be helpful for trusted community members to have curation tools that could move posts from the "real question" category to the "fluffy chat" category, and vice versa. I suspect I'm missing real questions I could answer because the querent labeled them as chitchat. Commented yesterday
  • 3
    Another issue with posts like that is they tend to use tags that have nothing to do with their content. Commented yesterday
  • also... this sample post itself isn't asking for advice anyway, lol... Commented yesterday
  • Their misconception is worse, the issue is not the ability to remove bad posts but to block answers posts on bad question posts-- closing. When there is closing deletion is practically moot. This answer is weak to the extent that it focuses on deletion & not the misconception & closing. Commented yesterday
30

We know that, broadly speaking (and this is a gross oversimplification), this community is made up of two key groups: new users, who often struggle to find their footing, and experienced contributors, who feel they lack the tools to effectively curate and maintain the site. Our goal with this redesign is to minimize disruption to what works while modernizing the experience to serve both new users of the platform and the needs of long-standing, tenured members.

I believe you are right. Using Stack Overflow is an on-going battle between new users who see SO as a forum to get answers, and experienced users who see SO as a source of curated information where you can find answers to your problems, or ask a question if the answer does not yet exist on this site. So the question that should be asked is: what do you want Stack Overflow to be? A library of knowledge or a programming support hotline.

At the moment, I feel that Stack Overflow (the corporation) have decided that Stack Overflow (the site) should be programming support hotline, and that the site should slowly and gently guide you towards the promise land, a.k.a an answer, notwithstanding that said question is a duplicate of an existing question, or is a bad question altogether. I have nothing against this goal per se, but you do need to realize that it is supported by a premise that is fragile at best: the experienced userbase is fully onboard with taking new users by the hand after each question and spending quality time with them explaining why their question is not really good for this site, and how they can change it.

The many posts you have made to collect the experienced users' feedback show that the people doing all the curation work do this for free, and are tired of having to clean up the thousands of bad questions that are being asked, plus the frustration of the new users who expect Stack Overflow (the site) to be a support resource rather than a repository of knowledge. Because experienced users treat Stack Overflow as a library, not a hotline. And they expect the tools made available to them to be in line with working in a library of knowledge, not a hotline. And thus, making the dual goal of "everyone should be able to ask a question" and "experienced users should be able to curate this site" incompatible.

Say you are looking for information on the Pony Express. You go to the library, and then you:

  1. Go to the counter and tell the clerk to buy a book on the Pony Express because this subject is interesting to you. The clerk points you toward a bookshelf at the back of the library saying that the 10 books they already have on the subject are located on the second shelf. You then ask a random person in the library to go fetch the book for you, find the information on what horse breeds was used in February 1861, and read it out to you, only to complain that the books lists the breeds used in January to March 1861, but you are interested in February 1861 only. You tell the clerk to buy a book that lists the horse breeds used in February 1861 only, and complain to management that the random library customer did not help you at all. You leave a 1-star review on Google to complain about the abysmal customer service you received from the random customer, and how the library does not care about their users.

  2. Go to the counter, pick up a map of the library, find the section where the books on the Pony Express are more likely to be, go the the bookshelf, find a book that seems to cover the subject of which horse breeds were used to run the PE, sit at a nearby table and read it by yourself to find the information you are looking for. You realize the book does not contain the answer to your question, nor do the other 9 books they have. You go back to the clerk and ask them if they could buy a book that covers the subject of interest.

You see, option 2 makes the most sense to me. That is how I would envision new users using Stack Overflow. That is how it was conceived, and used for its whole existence. You (the corporation) seem to lean toward option 1. Again, both options are valid choices, but if option 1 is the path that Stack Overflow (the corporation) choses, then I want to know so I can check out and stop wasting my time if my expectations are to spend my free time in the context of option 2.

I cannot speak for everyone, but that is what I understand when I read the feedback you get on Meta from said experienced users.

6
  • 4
    This is a thoughtful articulation of the two primary perspectives, but it raises the question: why do people want to create a library? To admire it from afar? Or to help people learn new information? What if you want information about the Pony Express and you ask a librarian for help on finding books that might have information about the Pony Express — the thing that librarians love to do! Here in New York City, the New York Public Library has a number you can call where you can ask them factual questions, and they'll do research and call you back with an answer. How do we get to that? Commented yesterday
  • 4
    @anildash Is the person on the end of that line paid by someone for their work? Commented yesterday
  • 1
    @anildash I did not account for the fact that clerks are paid and will indeed do fetch books and answer your questions. I have adjusted my story a bit. Commented yesterday
  • 3
    @anildash It's called duplicate closure. People have asked for ages to have a mechanism to properly give details on how a duplicate applies to a new, specific question. Commented yesterday
  • 5
    @anildash so - one of the things that I consider blinkers for most users is we keep getting promoted as a place to ask questions, rather than find answers. I'm a very experienced user - so searching for existing questions with my problem and existing literature comes first. If the question doesn't exist, I create one - not just so I can find an answer, but others can - we build a resource for the commons to tap on, primarily, and acting as a help desk is secondary. If someone has a question which I know an answer for and its novel I am helping the next person with the issue too. Commented 22 hours ago
  • Our goal should be always matching people with the answers they need - and if it doesn't exist, match them with the expertise they need. The latter's likely to be more experienced users. Commented 22 hours ago
28

Thanks for approaching the community. I think that I understand where you are coming from, but I would like to hear more details. What do you want to achieve in the end and why do you think that the new design achieves that?

If we still share a common goal, why is quality of content not a focus anymore? Why is knowledge diluted in a threaded, forum-like system? Why is there no way to put questions that do not work on hold? Why can we not move wrongly categorized questions to the right category? Why do comments take up so much space now? Why change everything at once and not simply a few things at a time?

Or in short: how is all that helping newcomers and visitors alike in getting good answers? What is the purpose of a bad, open question? And finally: why are there fake downvote buttons? Who would do such a thing?

I think we might simply have such different views on how a good Q&A should be done, that the only answer to what is wrong currently is simply: all of it.

Sorry if this is not what you would like to hear.

2
  • Comment threading does at least help to group related comments together, if used correctly. If done well (and importantly, if collapsible ), it has the potential to make long comment chains under a single answer easier to follow, and provide a more natural experience than having to enter a separate discussion room, and/or allows related yet semi-off-topic comments to be grouped in one or more discussion rooms without affecting comments that directly related to the answer. It'd be nice to be able to, e.g., have distinct informational, versioning, and clarification-suggestion threads. Commented 11 hours ago
  • ...This does require threading to be both designed used correctly, though, so it may be mere wishful thinking. It feels like it would be more useful to have on meta sites than main sites, too, so perhaps that's a change they should make. Commented 11 hours ago
19

The "new users, who often struggle to find their footing" are going to turn to AI. They already have, hence the drop in traffic.

That's good! (For them.) A personal helpdesk that can walk you through your particular problem, debugging, homework question, etc. That's way better than waiting for humans to try to understand and answer your slapdash question.

So it's really unclear why the company is redesigning the classic Q/A site to be better for those kinds of questions, when AI already exists and is already really good at answering them better and faster than the human volunteers here can.

Stack Overflow Q/A (classic) provides the library of high-quality, curated questions and canonical answers. This will continue to be valuable both for humans and as the training data for AI. Keep it as is. Provide a different path / different website for the helpdesk questions... and you should probably power that with AI.

(N.B. I have a hard time imagining why many people would turn to Stack Overflow's AI agent for help, when ChatGPT or Claude or whatever are probably better for the task and have a brighter future. That sucks for the company; you probably won't have disruptive growth or earn back the $1.8 Billion purchase price. But this redesign isn't going to fight that tide either.)

1
  • Regarding the last paragraph, many companies currently try to create additional value by building something around some LLM service, mostly agentic in a way. SO is not alone. And while the question is valid to ask why users shouldn't go to the sources directly, it might give them something. In this case not much though. Commented yesterday
19

Of the design changes that we introduced this week, which design changes are hindering the work that you are doing, and how?

Obviously the lack of curation tools on Q&A content (that I'm aware simply aren't implemented yet,) but otherwise the general design feels harder to navigate. There's no comments section under questions to ask the asker clarifying questions, there's no separation between different kinds of content, and the colors seem too dark for some monitors to the point where you can hardly see a lighter dark grey because it just washes out to black. Additionally the navigation keybinds I've grown used to seem to only work a small percentage of the time. (g+h, g+q, g+n, g+m)

The purpose of curation tools: Are they meeting your needs? How could they be improved? - What are we missing?

Since the current beta doesn't have curation tools, I'll approach this based on the tools on the live site. For Q&A, I don't feel like I'm missing anything, and they do meet my needs today. However, I do recognize that they aren't in a great place for serving the needs of users who come here for help and fail to provide the "Ask Questions, Get Answers, No Distractions" tagline the tour provides. Discussions content currently has no form of curation... and that's bad.

The necessity of all current tools: Are there tools you feel are redundant or no longer useful? Reconfiguring tools: Are there ways we can adapt existing tools to better serve the needs of the community?

I feel votes on questions (both up and down) are in a bad place. Upvotes don't indicate anything useful, and downvotes don't provide any useful information to askers or answerers. I'm generally a fan of the overarching strategy of the new curation system outlined here, however I'm still sceptical you'll provide us with the tools to actually remove the unhelpful content we need to given the complete inaction we've seen surrounding discussions, both the original version and the current one now known as open ended questions.

3
  • Upvotes on a question have a use. They show that the question is popular, i.e. a lot of people have the same problem. They inform that it is important to keep the answers to the most stringent quality standards becuase there will be a lot of poeple consulting them. Hovever, I agree that votes (and upvotes in particular) have little to do with whether the question should be closed / deleted. Commented 20 hours ago
  • @PiotrSiupa views already do that, though i think a "I also had/have this problem" button would be a far more useful "upvote" Commented 15 hours ago
  • Views are flawed, though, because they only show that the user clicked on the question, not that they found what they had been looking for. I have no hard data on that but I suspect that misleading or vague title can generate a lot of undeserved views. Explicitly given upvotes are a more reliable indicator. Commented 50 secs ago
18

I'm afraid all your questions presuppose that I came here to work at all. The real problem is that StackOverflow is no longer relevant.

As of now, when a user comes to stackoverflow, they're almost certainly there because they had a problem they want to solve. With that in mind, lets look at the new page you presented:

screenshot of new site

  • There's a chatbot, which is basically ChatGPT/Claude/Gemini/whatever, but almost certainly worse, since you guys aren't AI researchers, you're a help desk company.
  • There's a feed to questions which are pretty much guaranteed not to answer my question.
  • There's a list of stuff that's probably distracting and maybe interesting but definitely not helpful.
  • And lastly, there are a couple of links to other sites that I may be interested in at some point, but let's be honest, if I really cared about them, I'd have gone to them directly.

So basically you have a chatbot replica, but worse. I'm not quite sure what target audience you're hoping to attract with this. The only thing I can imagine is people who used to use stackoverflow, but aren't aware of their own chatbots, and enjoy random stuff that used to be relevant in the old site. That seems... a diminishing crowd.

I'm not saying it's game over for SE. At a time like this, StackOverflow Corporate — or whatever you called the version of StackOverflow that you sold to individual companies — is a much better value prop, because it gives companies a solid repository for internal knowledge, which makes for stronger internal context setting. However, this makeover really feels like a "hey please keep coming here because we were once awesome" attempt instead of a deep rethinking of how SE can continue to be useful in the future.

I haven't used SE in years, and as the demo is today, I don't see that changing. The value prop simply isn't there.

3
  • These chatbots can write low quality code samples....... weird but they can do. They use one of the well known AIs, I have forgot which one. How could one predict, for what you came to the site? We are not yet there, that these things could see your brain. Although your previous activities could be used, and should be used better to predict it. To some extent, it is being done, but it should be done obviously better. Commented yesterday
  • It's also worth pointing out, that this is what a new user actually sees, the exact overlay depends on region. Commented 2 hours ago
  • "you're a help desk company." No, SO is not a help desk. It's a library generator. Don't encourage them to think like that. Commented 13 mins ago
17

TLDR; There are 2 main issues with the new sites: UI, and curation. Without addressing the functionality gap, a UI change doesn't get us anywhere. And if the community is heard there won't be such strong negative reaction to changes.

I'll likely be the one with the lowest reputation to respond tho in my own ways I have an attachment to SE. My answer won't be as in depth as others as I'm not not a mod or someone who's familiar with all the work many of the member put in to keep it going, but might provide input looking at the overall picture and not down to details of how the site flow.

There are 2 main issues with the new sites: UI, and curation. With that in mind, let's go over your statements.

We know that, broadly speaking (and this is a gross oversimplification), this community is made up of two key groups: new users, who often struggle to find their footing, and experienced contributors, who feel they lack the tools to effectively curate and maintain the site. Our goal with this redesign is to minimize disruption to what works while modernizing the experience to serve both new users of the platform and the needs of long-standing, tenured members.

Does changing the UI help with either the 2 mentioned groups?

I highly doubt the UI of posts as is, is hindering new users greatly. Sure we should've had threaded comments and rich mark up a decade ago. But does overhauling the site help?

  • Moving tags, names of poster and timestamp to the top of the post just adds noise and reduces value. This metadata on the top implies high importance, which in reality isn't the case.
  • A new user has to scroll all the way down to the bottom of the answer to see the score, and let's be honest a new user will either go by the answer with the most votes, or the accepted one; and we already made it harder for them.
  • The comments have the same visual importance as the answers. Which implies they're just as important. That's not the reality of the site.

These stand out immediately, there are more, but I'll leave them off as beta is a work in progress.

I also don't how this makes the long time user's experience any better.

To us it feels like the UI was changed without any consideration on the user experience and how the site behaves. Unless, this is the intended direction of the company to make the site look more like Reddit and other social platforms. To be blunt, if we wanted to use Reddit as a forum for programming questions, we'd do so. There's a reason the community there is much smaller and less technical. Was there a case study for the UI change? Were the users asked simply which version of the site is better to visit again, or were the selected users looking to actually engage with a question and get a real answer back?

In their post @eykanal breaks down all the issues of the home page. There's lots that can be done on that page's UI alone to improve everyone's experience without restructuring the entire site. Could you have imagined people migrating to Google in its early days if it was as busy as this main page? Sure Google and SO serve different purposes and the same home page won't work for both. But if the front page of the site goes from distraction in one format to another, you've just redefined the same problem!

Specifically, I’d love your thoughts (as answers here) on:

  1. Of the design changes that we introduced this week, which design changes are hindering the work that you are doing, and how?
  2. The purpose of curation tools: Are they meeting your needs? How could they be improved? - What are we missing?
  3. The necessity of all current tools: Are there tools you feel are redundant or no longer useful?
  4. Reconfiguring tools: Are there ways we can adapt existing tools to better serve the needs of the community?

Clearly you're thinking of tools and functionality. But the original post barely focuses on the tools and only really addresses them after heavy down vote that's made it, as of posting this, it's the 5th most dowvoted post on meta and there seems to be no change of plans. The tools and functionality felt like an afterthought to the UI change! Any response by the staff there was to minor tangential points and not the mass concern of the users. Why not address the experience users, without whom the site ceases to exist?


At the end of the day we all understand a company with real investment is hosting, maintaining, and running the site and so they're entitled to directing where the site goes. But what make the site (not just SO, all SE sites) "alive" or once "alive" was the community. The company and community need each other. The community feels ignored and not listened to, news is just dropped on us and we feel a spectrum between disappointment to betrayal.

We're all aware the golden days of the site are well behind us, but changing it to what it never was in an attempt to bring more traffic in hopes of revival is not a solution. It won't bring the community back, and goes against the mission of the site.

As the tour outlines:

Stack Overflow is a question and answer site for professional and enthusiast programmers. It's built and run by you as part of the Stack Exchange network of Q&A sites. With your help, we're working together to build a library of detailed, high-quality answers to every question about programming.

The changes take us away from "a library of detailed, high quality answers to every questions about programming" aimed to help a person with a question and closer to yet another chat forum aimed for upvotes, ad revenue, and entertainment of the reader.

15

As a CPO/CTO, what is your vision for the site? Who will use it, and why? What are they looking for? To the extent that the content here is community-written, what motivates the community to participate?

Do you believe the site is successful today? After the redesign, how will you tell if it's more successful? What metrics or other indicators will you use?

11

From the question

Of the design changes that we introduced this week, which design changes are hindering the work that you are doing, and how?

Assuming that you are referring to the Beta site, none, because we have to go back to Classic to do most of the work. In my case, I'm not going to Beta to do the one or two tasks that can be done there.

From New site design and philosophy for Stack Overflow: Starting February 24, 2026 at beta.stackoverflow.com

As we continue to make updates to the beta site, please use the classic site to access these features:

  • Viewing comments on a question, or adding a comment on a question
  • Editing posts
  • General purpose moderation tooling
  • Changing your vote on a post (except for the default Troubleshooting / Debugging type questions)
  • Viewing most post notices
  • Real time notifications without reloading the page (updates on a post, inbox notifications, etc.)
  • Changing the list of one's Communities in left navigation menu
  • Certain actions on a post like Follow, Save, Start a bounty, etc.
  • Staging Ground

Note: Beta allows posting an answer to a closed question ---ref. Duplicate questions shows the answer box and allow to post an answer . This was reported a few days ago. I would like to think that this is unintended.

11

Short and sweet: the copious screen space allocated to comments, using the same font size, huge "upvote" buttons and more is weird, as it assigns a completely new importance to "just" comments.

Even if that's intended for comments coming in in the future for whatever reason, it misappropriates importance to historic comments.

11

Perception

Sir, with all due respect, Everything you wrote and the questions you asked are fundamentally flawed, in my opinion.
It almost reads as if we all work for the same company but in different departments. You, as the CTO, stepped in to clear up some miscommunication between the devs on your engineering team and all of us in content management, and we should "work with you to ensure that the future of Stack Overflow is one we can all be proud of."
To help smooth things out, you also asked our team for feedback because, after all, our shared goal is "to make Stack Overflow the best it can be for everyone who uses it."

Translation: SO pays the bills, which should incentivize all of us to work smarter, not harder, and communicate more so both teams can focus on what really matters: the customers. Because if they aren't happy, the company loses money, which triggers budget cuts. And we all really need this job.


Reality

The reality is we do not work for Stack Overflow, nor are we your coworkers, which explains the overwhelming negative sentiment from the so-called and much-maligned "Community."
Now, a handful of us, either out of the kindness of our hearts or because it gives them a sense of purpose, choose to volunteer in our free time to maintain and safeguard this collective knowledge we have amassed. But we all have our own teams to lead, our own code to debug, our own features to ship, and our own paychecks to earn. We also have our own problems to solve, so we visit Stack Overflow to ask questions and search for answers. We are your customers.

I also want to piggyback off an observation Tyler brought up earlier today in his stellar response about how Stack Overflow employees rarely use their own product as a point of reference, much less bother to contribute anything. Why should they? The same could be said of their CTO...

jody stack overflow profile


Responses

"This (significant decline in user activity) is something we cannot ignore, and it's a key driver behind the changes we're making."

Actually, I can ignore it indefinitely; this doesn't pay my bills.

"We have to move away from a world where closing questions is essentially the catchall and default option for curation."

Actually, I can find answers elsewhere; I don't have to do anything.

"I want to understand what's most important to you, what you feel makes the site unusable, and how we can improve the tools you rely on."

The UX of the site is most important to me. I, along with many others (feedback here), feel the proposed UX is abysmal and makes the site unusable by design. It should goes without saying that any discussion about improving tools while these fundamental concerns go unaddressed is simply a waste of time.

"With that in mind, our intent is to focus on tools that meet today's needs while taking a hard, analytical look at existing tools to see if they're still the right fit. While we may not have gotten it exactly right, I can assure you a lot of thought went into this redesign and direction."

Sir, with all due respect, In my opinion, considering you have zero firsthand experience on Stack Overflow, you are both ill-equipped and unqualified to meet today's needs. After all, to analyze the worth of a tool, you must both study its functions and learn to operate it with some degree of proficiency. And lastly, I can likewise assure you a lot of thought went into the redesign and direction of Windows 8. As they say, the road to hell is paved with good intentions.


Conclusion

I am not implying you are incompetent in any way, nor do I have anything against you personally. A lack of experience is simply a disadvantage, not a trait. From what I can tell, you seem honest, intelligent, direct and well-intentioned. It is just that, to quote you once more, I feel a good bit of frustration and skepticism.

The ball is in your court now, Sir.

New contributor
killshot13 is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
5
  • 6
    "We are your customers." I am afraid we are the product instead. And the customers care more about our numbers than our peculiarities. Commented 14 hours ago
  • 6
    I'd cross that line and say that as CPO they should feel responsible for this fiasco. It is Jody's poor judgement that led to the release of broken and hated new design. It doesn't come from personal incompetence but as you said from inadequate research and understanding of the platform. Perhaps they were pressured by someone higher up, but as a CPO they have considerable power to put their foot down and not let this happen. And yet they did. Commented 14 hours ago
  • 1
    @Dharman are you saying that instead of releasing the design and intent for preliminary review they should hide it and then force after finalization? This would be much worse! Indeed the previews are the only thing new team does right. Commented 13 hours ago
  • 4
    @Basilevs They should have brainstormed the ideas with the people who will be using the new UI before putting in the work. Commented 13 hours ago
  • Everyone can have an anonymous second account. Maybe an account with 1rep and a bunch of closed questions. But seriously, the changes do not focus on the Q&A as product, they sell us instead, even though they don't own us. @Dharman even as a CPO it's possible that someone else presents numbers and get the task to change it. Pre-releasing it and presenting the backlash can be the only way to argue back by presenting different facts to support their own stand. Especially in heated times, people tend to act rather than discussing matters, because no one will listen they wanna see. Commented 3 hours ago
8

I'm going to start somewhere in the middle

With that said, our attempts to communicate about the necessary change were imprecise and confused the situation. When we said “no more closing questions,” we failed to take into account that that phrase would mean something very different to you than to us. For instance, we effectively draw a line between closing questions and deleting questions. Deleting questions is definitely still in scope for us.

Well, that's a clear example of why the company fails us. We try our best to communicate our needs. We don't have enough people who speak our language, and can translate it to what you speak. Where people have the skills to communicate with the community, they are undervalued and we've lost too many.

If you can't understand the community's needs, and understand why we need closures of questions (to give an opportunity to fix those questions) - you shouldn't be changing those things.

You've already gotten a lot of feedback. Some of it from the most gifted folks on the network. Jon Skeet weighed in - how much of it do you actually understand, and if you don't, how're you going to figure out what you're missing?

If you have no one who can communicate effectively between the community and company - you should be building on and growing those competencies. As a community member, that's lacking across the company.

Hiring for those abilities - across the company would be good, but y'all aren't seen as a good choice by many, or the people who'd give you a shot just can't get hired. And the folks we've had over the years who could communicate invariably end up downsized.

You arn't just dealing with corporate customers. You're dealing with a deeply passionate community of folks who're dealing with the trauma of the company's past actions and are mistrustful. Reactiveness isn't a sign the community is against you, its that the company's actions did and continue to hurt us and the relationship we've had.

In some cases that's personal, in other cases, its common to many of us. We don't have good reasons to think the company will listen to us, or even keep its word.

If we were clients, chances are we'd be dropping you or asking for compensation. As a community, we only really can try to reach out, fight or walk.

You're never going to succeed if you can't get people who can bridge the gap.

Many of the tools we have today were designed to address scaling challenges from over a decade ago. These challenges may no longer exist in the same way. With that in mind, our intent is to focus on tools that meet today’s needs while taking a hard, analytical look at existing tools to see if they’re still the right fit. While we may not have gotten it exactly right, I can assure you a lot of thought went into this redesign and direction.

These challenges partially don't exist because the folks who were active on the network often got alienated by decisions made by the company. This path reinforces the negative feedback loop that causes people to leave. "Not gotten it exactly right" is a very strange way of saying "We know what people on the network need better than folks who are actively doing curation and content creation every day"

In a perfect world - we'd want to scale up again and have the tools to deal with those problem.

experienced contributors, who feel they lack the tools to effectively curate and maintain the site.

Thing is on the short run, we created these tools. Review queues evolved from chatrooms used to review posts. More recently, we got better spam tools - after 2 years of ad-hoc dealing with thousands of spam posts with the help of the community. We don't need perfect, but we're more likely to be able to handle things if we know you understand our needs and are working on it.

We've been complaining about these over a decade, we've lost a LOT of contributors, and as things go, folks who can operate on the site at the level are rare.

This is also, incidentally the group the company seems to alienate the most often.

I also need to level set a bit: we’re not trying to do away with the concept of removing unhelpful posts. We care deeply about curation and have dedicated substantial time and money to building tools for it, and we will continue to invest in this area. But we do have to move away from a world where closing questions is essentially the catchall and default option for curation. We believe we can create better, more precise, more surgical tools that can be used. And we intend to work with all of you to make sure that curators here can take advantage of those tools.

If there's better options for dealing with duplicates and such, people would use them. Taking away tools without better options is a bad idea though. And If you're not listening to the people using the tools - we're less inclined to suggest better tools. I've been floating a idea on better duplicate handling for a while - but in the current environment, I don't see the point of spending the time laying out even an early draft on meta cause it'll likely to be ignored.

Regarding feedback on quality, you are right – there is still significant work to be done. We intentionally chose to launch this in an early state. We are, as Stack Overflow did in the distant past, intentionally relying on you to help us identify issues so we can more quickly address as many as necessary to reach an acceptable level of quality before moving the site to the new design. I’m here to listen and gather actionable feedback. I want to understand what’s most important to you, what you feel makes the site unusable, and how we can improve the tools you rely on. Specifically, I’d love your thoughts (as answers here) on:

An early draft that a little janky, designed to find requirements has value. Something that's clearly designed to be a completely different model is going to get pushback. Thing is there was a lot of early feedback on the redesign that's been ignored.

In many cases, with other initiatives - such as the new data dump, still have promised features (like access to a complete copy) either on hold for years, or quietly killed off.

We have no real reason to believe this isn't going to end up with the vision of folks uninvested in the stack exchange network as it has been, rather than as a evolution of the platform we know and love.

We've consistently given actionable feedback and continue to, even tried to explain where its less than obvious to someone not a network regular and its been ignored. At some point we burn out (and we've lost mods due to company actions... far too many). The mood amongst many mods is 'why bother' cause our feedback hasn't had any impact at all. So - I'd wonder if the company is willing to work towards changing that.

I'm going to quote from a moderator internal post I wrote earlier

A lot of the time, the company lacks direction and communication. There's multiple situations where the company has failed to take community feedback, or pushes through 'features' or bigger projects without taking neither their own employees feedback or the community's (see the rebrand). We've had extended periods over the years with insufficient support. While the company is very focused on changing the platform to attract people from outside, we lose people who have impact within the communities. The public platform, especially smaller sites often end up in a poor state as a result cause they don't have the critical mass to handle a problem.

We need to know our feedback has value. If the feedback is that the new design is currently unserviceable for our needs - and we're rather you iterate and improve our current model, we need you to take that feedback , and show good faith, even if It means killing off a project you've sunk a lot of man hours into .

You'd note most of the feedback has been negative. Its been actionable. We have a return of the new comment design - where we clearly pointed out comments were a 'second class' thing and they distracted from answers for example. You have everything you need already. Its just ignored from our perspective.

And while early action's nice, much like with your AI initiatives, hubris has poisoned the well. This is seen as the first step towards killing off the Q&A platform (and the rest of the redesign kills off the stack exchange network's identity). We see this as a threat to the network, and are reacting accordingly.

So very much my actionable suggestion would be - without the Q&A platform we've built over the last 16 years, this place wouldn't exist. These changes are affecting folks who are the most active the most. If you want to try something new - let it be on its own merits. Build a different model. See if people prefer it - but if you' want to replace what we have now, you're going to lose the community we have.

I sometimes feel the community SO inc wants is different from the one we have. Its also... kinda vaporware. So take the opportunity - look at what we've said, and please do right by us.

7

I've been using [so] for about 10 years now. Half the time I didn't had an account and just looked up Q&A here to solve my problems or find orientation by reading experts sharing their expertise on this platform. This is also the group of people we (the community) actively aiming for. The metrics of new users or new questions is irrelevant to us, if you wanna talk to us about a decline of SO show us that our products (Q&A) aren't clicked anymore. Because that would indicate that our products lose real value to us.

Making an account and ask a question is a last resort for SO users. We ask questions here when we don't find an answer in advanced and that is how it should continue to work.

After a SO user (visitor) made an account, they don't know nothing about this site besides what they believe to be on-topic. The only tools we have to signal it ain't on-topic to new users are downvotes and close-reasons, which are ambiguous, ask the community about common reasons they downvote and friendly phrase for it.

I welcome that you decide to resolve the ambiguous reasons to provide detailed reasons. Buttons with down-vote-reasons below the question, which result in comments by the community bot would be helpful, for author and curator. Since SO member don't like to engage with authors in general. Because we don't know what lunatic or maybe even a kid is sitting on the other end.

Even so for each close reason there are some common responses. I would suggest you to take each close reasons and ask for them here on meta. After gathering the information implement it like this:

[dublicate] [details] [focus] [opinionated] [format] [custom]

  • Belongs to a different site ...

Since the community-bot tells the user what's wrong they can act by editing or ask for further advice in the comments. If a question finally got closed place a link to What does it mean if a question is closed? and What if I disagree with a closure of a question ?

It took me years before I found out about meta and it's not the job of the community to educate the users, nor is it necessarily the new members fault for not knowing how this site works. That's the company's job and you have to do this and I refuse to accept that a new user has to hop through all the rings of immensely searching for guidance, it's like having to reading a manual to this site. Provide them automatically in the situations they are needed.


Resolve ancient issues, put them on the table again and ask for concrete solutions:

6
  • 1
    "if you wanna talk to us about a decline of SO show us that our products (Q&A) aren't clicked anymore." Anecdotal, but I have long since stopped treating SO as the first step for finding information. There are many topics for which I don’t even trust it as a sanity check for GenAI queries. The "knowledge base" now includes so much uncurated noise and so many highly-voted bad practices, it’s not a reliable source of knowledge anymore. I keep consistently finding myself having to double check what I read here instead. Commented 21 hours ago
  • @MisterMiyagi So wouldn't it be appropriated to have review queue for hot topics where we can do sanity checks? The low threshold of new question could be a blessing in this regard. Or what tool you would envision to tackle this ? Commented 20 hours ago
  • 1
    This has nothing to do with new questions (since another post also referred to this metric, it would be interesting to know why you think otherwise). The primary use as a knowledge base is to look up what has already been written. And this knowledge base itself has been in a quality decline over the past years and accumulated significant "review dept". I don’t think it makes sense for me to suggest a tooling solution when both company and moderators insist we don’t operate at that scale anymore. Commented 20 hours ago
  • 1
    What I meant with --The low threshold of new question could be a blessing in this regard.-- is that I feel less occupied by new questions and could do more curation than before. I only do so nowadays if I stumble upon a Q&A by researching and then I edit/answer/upvote/downvote. Reviewing existing content seems to be the bigger target than new questions. Ain't it ? I still wish for more people coming here and asking new good questions and I think new members would be more attracted if they knew what spectrum is already covered. Commented 20 hours ago
  • 2
    Just as new questions have declined, so has the number of people willing to ensure quality. We now have (much) less people to handle a volume that is still the same. Commented 20 hours ago
  • Well it is less exciting but I guess new people can join or old can come back. It's a variable after all that can go up as well. Commented 20 hours ago
4

Are the curation tools meeting your needs? How could they be improved? - What are we missing?

You are missing a way to migrate posts between opinion-based discussions and Q/A proper. People get this wrong sometimes, and questions asking for "advice", "recommendations", or "troubleshooting" are actually focused and well-suited to receive a single correct answer, they do not belong into the grey area of "on-topic but no clear correct answer". Same for the other way round, instead of closing Q/A posts as opinion-based, some of them might be kept in the forum part of SO.

3

I don't have the patience to actually read through all that corporate speak anymore. So in that spirit, I'm going to keep this short and to the point. I wish you would do the same.

We care deeply about curation, and have dedicated substantial time and money to building tools for it; and we will continue to invest in this area.

Then why don't I see any curation tools on the new site? Heck, I don't see a way to flag abusive content!

Why did you de-emphasize the score? Even though they're not perfect, question and answer scores are the first indicator of quality. They aid in deciding what content to give our limited time/attention to first.

Also FYI, the new graphical arrangement actually makes it infinitely more difficult to tell the difference between the question, answers, and the comments. That wastes everyone's time, including the asker's. I say without exaggeration that this is one of the worst designs I've ever seen.

When we said “no more closing questions”, we failed to take into account that that phrase would mean something very different to you than to us.

What I'm hearing is that the people making decisions don't have any idea what made this site succeed in the first place. The entire model was designed from the beginning to eliminate common frustrations of the most active, longstanding participants in forums, such as dealing with endless duplicates and low effort requests. Removing closure brings those frustrations back. De-emphasizing votes makes it difficult to identify the best answers. A community can't survive if the experts don't stick around.

We're not looking for marketers to hand hold our feelings while you wreck everything that made this site worth using. We're looking for people who actually care enough to do something about our problems.

-14

Our goal with this redesign is to minimize disruption to what works while modernizing the experience to serve both new users of the platform and the needs of long-standing, tenured members.

The people that leave SO in a huff typically complain of closevotes and downvotes. What is obviously "wrong" about a post to an SME or an experienced curator isn't necessarily obvious to the poster or other readers. Users aren't leaving the platform because of the site UI or the color of the logo or the way that comments are displayed.

To limit my suggestions to a single fundamental change that will move the community toward constructive feedback: Provide a reason with downvotes. We aren't dealing with thousands of posts per hour now, we are dealing with dozens. Implementation can be in a number of different ways and I would be happy with virtually any step forward.

None of us would enjoy working where our pull request was declined with no feedback. Countless calls for reasons with downvotes have been made by the community and largely left unanswered.

Show us the evidence, you say? Sure, since we cannot use SEDE queries to find deleted comments, I've been caching (and will continue to cache) discontent with unexplained downvotes before I delete flagged comments. I have hyperlinks for all of these deleted comments, but they didn't fit in this post - now available via this permalink to the associated chatroom.

Ultimately, I'm saying DO NOT remove downvotes, make them part of constructive feedback to spur improvement instead of doling punishment. If users are being consistently unconstructive in their activity, maybe they are abusing the tools and doing unnecessary harm to the platform/community.

  1. (After 6 downvotes) "Seriously? No comments? What has this site come to? No wonder GPT is winning and stackoverflow is dying ... anyway. I got my answer so ¯_(ツ)_/¯" – Μenelaοs yesterday
  2. "(see prev comment and pls reply) I know this isn't important but I have not downvoted this question. We get very few TS questions nowadays (I guess AI answers everyone's questions now, for better or worse) and it seems like the few we get are consistently downvoted. I see nothing wrong with this question, so I don't know why it's getting downvoted. 🤷‍♂️" – jcalz Dec 31, 2025 at 14:48
  3. "???? what's wrong with this — at least comment why it got downvoted so I can do better next time? I swear this site is worse than reddit for asking questions" – RuralAnemone Sep 23 at 16:54
  4. "@DV: care to leave a comment?" – user314159 Sep 24 at 7:27
  5. "@Downvoter, any explanation of what's wrong?" – Abdulla Nilam Jul 20 at 10:37
  6. "@Downvoter: Did I say something incorrect, or just something contrary to what you were taught?" – Mike Dunlavey Aug 30, 2013 at 16:10
  7. "@DrewReese I marked it as the solution, not sure who downvoted it or why." – Brian Holestine 13 mins ago
  8. "@PhillHealey - I up voted to counteract the phantom down voter." – Brandon CommentedMay 2, 2014 at 20:20
  9. "@ZoestandswithUkraine Off topic, but I cannot understand why this question has been downvoted so severely. This really doesn't look legitimate to me. Have you raised this with the mods?" – skomisa CommentedJun 3, 2023 at 15:32
  10. "@downvoter, please explain? I was just highlighting an unusual parser that claims better performance than most major parsers out there, what's wrong with what I've said?" – Nim Jan 12, 2011 at 22:57
  11. "@downvoter: please elaborate so that I can improve my anwswer!" – TemplateRex Jun 30, 2014 at 12:15
  12. "@downvoter: reason ?" – prashantgpt91 CommentedJun 21, 2016 at 11:16
  13. "@jonrsharpe - Could you provide some advice as to how I can improve my post ? I see it's been downgraded." – bob.mazzo 1 hour ago
  14. "@shawnt00 I don't understand how in the world this answer got 3 downvotes. That is what I don't like about SO, people do that just because they can without a need to give a solid reason to do so. If instead, it was mandatory to discuss before doing so, then SO might be much more valuable." – Cetin Basoz 18 hours ago
  15. "@skomisa It's mostly a consequence of one-off revenge from a many different users. There's nothing that really can be done about it, unfortunately" – Zoe - Save the data dump CommentedJun 3, 2023 at 19:04
  16. "Added some missing details from: https://stackoverflow.com/staging-ground/79739291. PS: Not sure why there are down-votes. The info is useful to other programmers dealing with some unusual SPS parsing result(s)." – VC.One 7 hours ago
  17. "Ah I didn't think it was you :) I've asked stupid questions plenty. I just like to know why people downvote so I know why the question is stupid, haha." – John Humphreys CommentedOct 2, 2011 at 20:24
  18. "Ah, here it comes unhelpful downvote. The classic stackoverflow moment." – Satrio 30 mins ago
  19. "AmmarCSE Over a year ago heh, I dont know why people voted you down. It worked for me on PHP < 5.5"
  20. "And why is this downvoted if someone can explain ? I have seen so many people just for the sake of downvoting have downvotted so many which we are reopening with 3 votes. If you are downvoting then at least leave the comment for what reason and understand why" – Ranadip Dutta 9 hours ago
  21. "Any comment from downvoter?" – wim 2 hours ago
  22. "Any feedback on the down vote?" – Santiago Squarzon Sep 3 at 23:10
  23. "Any reason for the downvote?" – C.Nivs 3 hours ago
  24. "Anyone who can comment on the downvote? What have I done wrong?" – Andreas Jul 15, 2017 at 13:53
  25. "Bruh why on earth was I downvoted? I researched my own problem, I tried to solve it myself, I edited according to request even beyond what I think is helpful, and then someone comes by and downvotes without a word. I'm honestly getting to the point where I think that downvotes without written justification shouldn't be allowed. /rant Sorry, but I needed that." – Fluffy the Togekiss 2 hours ago
  26. "Btw I don't understand the downvotes. The question is clear, contains the needed details and states which expectation is not met." – moonwave99 9 hours ago
  27. "Can closevoters and downvoters please explain what is wrong with this question? What sort of "debugging details" do you expect to answer what is iostream?" – Yksisarvinen yesterday
  28. "Charles Over a year ago Downvoter, what's wrong?"
  29. "Could someone please explain the downvote?" – NL628 CommentedMar 18, 2018 at 5:19
  30. "Curious to know why this was downvoted?" – Julien 4 hours ago
  31. "DV? any comment" – 0___________ Aug 16, 2018 at 10:03
  32. "Does anyone care to explain why this got downvoted?" – LightningWrist CommentedNov 17, 2012 at 0:04
  33. "Don't know why the downvote. I had the exact same issue and manually deleting the dist folder worked for me." – alex351 Mar 4 at 15:11
  34. "Don't know why this was downvoted, it's a perfectly valid answer. (And one that I'm very happy to have found, as I had the exact same problem, so thanks.)"
  35. "Downvote with no explanation. Perfectly reasonable question. Explain the downvote." – mike rodent 3 hours ago
  36. "Downvoted for ...? Did I not follow a community guideline?" – machineghost Commented4 hours ago
  37. "Downvoted why exactly?..." – ZorgoZ 2 hours ago
  38. "Downvoter should explain. This meets the requirements." – Wesley Smith Sep 10, 2016 at 21:56
  39. "Downvoter, do you mind explain why? Can something be improved?" – Tushar Jul 21, 2015 at 13:32
  40. "Downvoter, please explain why you think this does not answer the OP's question. I added a link to a dbfiddle to show it works." – Bill Karwin Jul 18 at 13:04
  41. "Downvoter: what's wrong with PATH_INFO? The question is ambiguous enough to allow for this possibility." – outis Mar 1, 2010 at 19:23
  42. "Downvotes without any sort of comments do not help the situation. If you believe there is something unworthy or bad of the answer, be part of the solution: suggest something or at least identify what component needs help. (Moderators, please don't delete this comment, too. Anonymous downvoting is a guarded right, certainly, but the rate of random downvotes has increased this year, I'm trying to suggest ways to improve the community. If the seemingly-random downvotes continue, this discourages participation.)" – r2evans CommentedAug 12 at 11:30
  43. "Downvoting means I did something wrong. Any feedback will be great. If the solution is already there provide some link." – Eypros 14 hours ago
  44. "Dudes, dudes. Do you really need to DV the question that much??? The only suggestion being made here is by the Community Bot. You could always vote to close it and explain why, but the excessive silent downvoting is quite unfriendly." – JL Peyret 2 hours ago
  45. "Explain downvotes, pls" – jei 5 hours ago
  46. "Gordon LinoffOver a year ago Do I assume from the (anonymous) downvote that this does not work?"
  47. "Hey @marc_s, warum hesch mer e Downvote gä?" – David Klempfner CommentedJun 28 at 5:42
  48. "Hey anonymous downvoter: can you please explain why you think this does not answer the question?" – Bill Karwin 2 hours ago
  49. "How did i get -2 when i had the question reviewd by the community before posting? RIP stackoverflow" – john houses 7 hours ago
  50. "How does this get downvotes? A statement from the inventor of the language concerning the question at hand should be noteworthy and on-topic" – julaine Commented2 days ago
  51. "How is the "commentary" not related to the question? And why won't you let me know why the question was voted down instead of resorting to such high-handed tactics" – hassaanq Aug 7, 2024 at 11:17
  52. "I am surprised that your answer was downvoted. It worked very well for me on local files with the latest Chrome version." – Waruyama Mar 9, 2016 at 10:15
  53. "I am unsure why the downvote. I could have kept my solution to myself but I felt it was better to share it with the community." – DaiG Aug 8 at 13:43
  54. "I did note the timeline and I recognize that this thread is older than GoDaddy's blog post on how to address it. Nevertheless someone has been downvoting the only viable solution for months. This behavior has wasted a huge amount of my time and my team's time." – Isaac Potoczny-Jones Nov 29, 2014 at 21:15
  55. "I do not understand, why my question was downvoted. It is my case and I need to decide it inside my Mapper and HttpResource. This downvote is biased." – Yuriy L. CommentedMay 28, 2019 at 14:47
  56. "I don't hope a response but.. @downvoter What is wrong? What did you not like?" – L.B Nov 14, 2016 at 20:24
  57. "I don't know why I got downvoted so fast lol." – lapartman CommentedOct 23, 2017 at 14:51
  58. "I don't know why this was down voted and closed. It seems like a perfectly reasonable question to me." – Remy Lebeau
  59. "I don't understand all the downvotes. Isn't Stack Overflow a place for you to learn? I haven't used vba in quite a while and couldn't remember how to do it. All I was looking for were a couple pointers to get me started again." – j2associates 10 hours
  60. "I don't understand the down votes on a perfectly reasonable question." – qwr Sep 2 at 4:38
  61. "I don't understand the downvotes - please provide comments how I can improve the question" – kiedysktos CommentedJan 23, 2017 at 14:17
  62. "I don't understand the downvoting for this answer, it does solve the issue for me in Chrome." – ner0 Nov 11, 2021 at 16:04
  63. "I don't understand the reason for the closure without an explanation. One of the downvotes was made in just 14 seconds (if I'm being very generous) after looking at the question. Before the third close vote, the question was edited, but unfortunately I couldn't find out whether that was sufficient." – rozsazoltan 12 hours ago
  64. "I don't understand why this question was voted down ..." – sergiofbsilva Jun 22, 2012 at 9:36
  65. "I don't understand, why i am getting negatives :(" – prashantgpt91 CommentedJun 21, 2016 at 11:31
  66. "I dont know why you got downvoted, but works on my vs 2026. Thank you" – xike 26 mins ago
  67. "I got two downvotes. May I get some hints of how to improve the answer?" – fedorqui Aug 21, 2014 at 9:33
  68. "I hate down-votes without a comment. I'm guessing someone do not like the fact that standard do not defines representation of float." – Marek R yesterday
  69. "I know it's late, but downvoters (or sympathisers) care to comment why? This seems like a reasonable statement to me. We use Doxygen, and the issue certainly came up." – T.E.D. Feb 8, 2011 at 14:07
  70. "I know you're not obliged to explain your downvotes, but I would find it very helpful. I've tried to provide enough information, but I can't give a minimal reproducible example so easily." – AncientSwordRage 6 hours ago
  71. "I never get it why an answer got downvoted. Here is the usage of watchdog: pythonhosted.org/watchdog/quickstart.html" – swdev CommentedNov 30, 2014 at 22:13
  72. "I notice this is getting downvotes. Can anyone leave comment about the reason ? I did not post on serverfault because I saw this question on SF meta(https://meta.serverfault.com/q/6328/1056735)" – glacier yesterday
  73. "I think the question is valid and I do not understand why sombody downvoted it." – alex CommentedApr 1, 2009 at 23:18
  74. "I would also be very grateful for an explanation of the two downvotes so that I can avoid whatever problem triggered them in the future." – DaiG Oct 10 at 13:29
  75. "I'd like to know the reason of the downvotes. Incomplete details? Question unclear?" – Poseidon 16 hours ago
  76. "I'd really appreciate if those who downvote [working (=accepted)](Return true if all patterns exist in a given string in any order in Python), well-explained, not "here-you-are" answers could leave a note why they think this answer is not useful/helpful/poorly argumented. The point is that an incorrect answer has more upvotes than a correct answer, and this is baffling people who need the right solution to check if all the patterns match a single string in any order." – Wiktor Stribiżew Jun 16, 2017 at 10:28
  77. "I'll clarify that last sentence: Lacking any comment or clear indication that the answer is incorrect or otherwise of low quality, downvotes do not help the situation. The goal here is to make the answers good (enough) quality for some sense of longevity and hopefully generality; downvoting an answer can be used to indicate something about it, whether wrong, anti-canonical, anti-best-practices, lazy, or one of several objective assessments, and most of those reasons are often easily remedied, but only if/when the answerer knows to address them." – r2evans yesterday
  78. "I'll look at it some more. But I don't know why our answers have been marked down - they both answer the original question perfectly." – Tom Sharpe yesterday
  79. "I'm always happy to improve upon my answers, but sadly, when the down-vote is not paired with a comment I'm not sure what the shortcoming is." – Lajos Arpad Commented25 mins ago
  80. "I'm not sure why this was downvoted, so downvoting doesn't really serve anyone's interest. If the downvoter actually took the time to explain WHY it was downvoted, I'd happily do my best to rectify the evil wrong that they perceive me to have committed. Thanks." – Phill Healey CommentedMay 2, 2014 at 19:37
  81. "I'm surprised that this is downvoted, this is exactly the solution I came up with, and was about to post, before seeing your answer already existed with this solution. Apparently at least on MacOS the -S option to the env command isn't necessary, but my understanding is that it will improve portability with different versions of env." – Patronics CommentedJul 23 at 4:24
  82. "IMHO Anonymous downvotes are killing the usefulness of StackOverflow (and other forums). I think this is a useful, relevant question. If somebody thinks otherwise, then it would be more constructive to explain it why it’s not." – Manngo 3 hours ago
  83. "If downvoters can explain what is missing, maybe I can improve the question." – NBur 6 hours ago
  84. "If people mark down the question, can you at least have the courtesy to explain yourselves?" – Timothy C. Quinn 2 hours ago
  85. "If someone is inclined to downvote, would they please explain? I have laid out my question as clearly as I know how, and I researched everything I could find before posting my question, but existing results are scarce and seem irrelevant." – Greg 1 hour ago
  86. "If the person downvoting can comment explaining why she/he thinks the question is not proper ?" – jeandut Sep 26 at 15:52
  87. "If you are down voting the question, please do but kindly also add the reason." – Keshav Saraf yesterday
  88. "If you down vote - please leave a comment as to why. I'm not a passerby here, I am actually trying to learn something here. An abstract downvote does not help me learn anything other then the fact that the downvoter did not take the time to explain why this was done. When I downvote - I explain why" – Rann Lifshitz Apr 26, 2018 at 8:14
  89. "If you guys down voting it are so smart then why don't you write a line? Negative people who knows nothing and try to act as experts" – Allen King 6 hours ago
  90. "If you insist on downvoting, at least tell me why so I can fix whatever you think the error is." – John Bode CommentedNov 18, 2013 at 12:36
  91. "If you're going to take the time to downvote my answer, a comment would sure be nice."
  92. "It was just a simple question - by an amature - so why the negatives? Moreover, things can change - retrospective workarounds can be introduced (if there is a will to do it), and anyway it doesn't have to be "//" - it could be something new - randomly "?!" for example. Narrow minds it appears?" – user3306881 Aug 1 at 16:15
  93. "It's interesting that it worked, hasn't been accepted, and got a down vote." – the Tin Man Jan 19, 2013 at 3:51
  94. "JRG Over a year ago Dear down voter, why would you down vote when the solution(get1To1Mapping) gives OP's expected output?"
  95. "Just sharing what worked for me gets downvotes? At least give a reason for the downvote." – Ash K Oct 22 at 3:17
  96. "Lajos ArpadOver a year ago @mickmackusa it is up to you, I respect your decision regardless of whether you put the downvote back or not. I really appreciate that you gave a reason and gave me the chance to reflect on it. In many cases downvotes are given without a reason and in those cases I am left with questions, trying to find out what was the problem and in many cases not understanding it. I also try to give a reason each time I downvote a question or answer."
  97. "Madhur BhaiyaOver a year ago Strange to see downvotes. Any explanation guys ? would be helpful !"
  98. "Mr47 Over a year ago To downvoter: please provide a small comment in the future to indicate what could be improved."
  99. "Mystery downvote! yummy!" – ikegami Commented7 hours ago
  100. "Not sure why my question got downvoted. I did some research before asking the question." – mdailey77 Jan 31 at 15:58
  101. "Not sure why there was a negative on this." – jkdba May 31, 2016 at 15:20
  102. "Not sure why this answer got a -1. I thought it was well-written and informative, and shows the author put a lot of effort into it. Upvoted again." – Christoph Nov 18, 2024 at 3:47
  103. "Not sure why this is downvoted. Works perfectly." – Pristo 6 hours ago
  104. "Not sure why this was adjusted to -1 ??" – FuzzyWuzzy Nov 14 at 1:00
  105. "Of all the answers this is the one that worked how I wanted. Not sure why this got downvoted, it looks correct. The file name "TEAM\ 4.pdf" is hard to read?" – josephdpurcell Apr 8, 2024 at 14:09
  106. "Oh why the downvote? If it's something that should be improved, please let me know! Why @BhargavRao?" – gsamaras Feb 5, 2016 at 19:39
  107. "One last opinion, here. I don't understand why SO members down vote this question. The poster explained it clearly, worked to develop a solution; but, feeling that there should be a way better for his needs, unsuccessfully tried another approach and sought assistance. What's wrong with it?" – Gary Aug 12 at 1:25
  108. "People downvoting, please at least explain why." – sudoExclamationExclamation Nov 27 at 3:34
  109. "Please don't downvote this if the question seems specific to WordPress, it was migrated from wordpress.stackexchange.com and now it makes much less sense in context." – Dan Gayle CommentedNov 3, 2014 at 21:20
  110. "Please explain "-1" ... the function works well here." – Rudi 10 hours ago
  111. "Please give explanation for downvote and help me improve my questions, thanks." – mike rodent 6 hours ago
  112. "Please provide comment if you downvote or close." – user1032531 Feb 3, 2015 at 2:29
  113. "Please provide comments if you down vote. Would appreciate it better. Thanks," – Saurav Rai 1 hour ago
  114. "Please would you explain the downvotes?" – Paul D 2 hours ago
  115. "Please, explain what is wrong with this answer if you downvote it." – biggujo CommentedJul 4 at 19:51
  116. "Rather than giving -1 .... one should also explain what is wrong and how to correct it." – John3245 Sep 29, 2014 at 7:30
  117. "Rewriting code by reformatting it does not deserve any upvotes." – user2665694 CommentedMay 19, 2011 at 6:08
  118. "See downvotes for my post, can somebody comment." – user1982778 Commented4 hours ago
  119. "Sharanya DuttaOver a year ago Dear downvoter, may I know what’s wrong with my answer?"
  120. "Show people a new way of doing something and get downvoted for it without even an explanation. Thanks toxic platform..." – Mentalist 20 hours ago
  121. "Since the answer correctly produces the logic requested, a downvote is a little surprising. I'm all about improving my code and/or my presence on Stack, can the downvoter please provide some advice or criticism? Lacking any comment, downvotes add nothing to the quality and community of StackExchange." – r2evans yesterday
  122. "So who are the -15 lurkers! If you want to negative mark an answer, provide a comment as to why you do so." – MrC aka Shaun Curtis Jan 19 at 13:26
  123. "So, why downvote this? If it's not on-topic enough, let's delete it. I can't delete because it was answered!" – User May 29, 2017 at 19:43
  124. "Some hit-and-run down-voter who can’t take the time to explain what they think is wrong with the question." – Manngo CommentedNov 9 at 9:14
  125. "Sorry, why downvoting? Is my advice not correct or not useful? I am trying linking in order to deduplicate several threads with the same question by pointing them to the same answers." – Alexei Khlebnikov Apr 25, 2018 at 17:50
  126. "THanks for the reply. Not sure why my question was voted down. This way, this question will appear over and over again because negative questions do not show up in searches.." – LearnByReading May 20, 2015 at 16:06
  127. "Taking the time to go over the code, and downvote - but not taking the time to write what's wrong with the answer?" – Narxx Dec 6, 2017 at 8:14
  128. "Thanks for the down-vote, I understand that whoever the down-voter may be, you detected things that need to be improved. If you could describe what you found to be subpar, then I would be happy to look into it. Thanks!" – Lajos Arpad Jul 9, 2025 at 9:46
  129. "Then that's what should have been posted instead of the three cowards who downvoted it without comment." – Mike 9 mins ago
  130. "Those who are here with nothing to do except devoting the question, please suggest improvements only. If you don’t understand what the question is about or have nothing constructive to add, please ignore it and scroll past." – Hasan Othman 15 hours ago
  131. "To anyone venturing across this post: this was downvoted during a revenge downvote-spree from another user. Don't let that discourage you from trying this. it worked for me!" – Brian Nov 20, 2019 at 20:54
  132. "To whoever downvoted: please leave a comment explaining what didn't work for you. I'd be happy to improve the answer if possible, or if not I can at least note its limitations (eg. "it doesn't work if ...")." – machineghost CommentedJul 23 at 15:44
  133. "Tomas Over a year ago Can you explain, why you downvoted my answer? Your comment is absolutely out. The algorithm I provided is better than anything what has been proposed here until now!"
  134. "Two downvoters please provide feedback, why is this third option so bad?" – r2evans CommentedJul 22 at 13:46
  135. "Two downvotes and even a close vote for a clear, reproducible question. Why???" – Dominique May 22, 2025 at 8:23
  136. "Was there a genuine problem with my code? I was down voted along with several other people, despite simply responding with an alternate solution. If there is a reason for the down vote, I'd like to see a post to go along with it as it would serve as an opportunity to improve the answer if there is a problem with it." – Mezzanine Jan 27, 2018 at 2:27
  137. "What guideline doesn't it meet?" – machineghost Commented3 hours ago
  138. "What is the reason for down-voting? How can I improve my question that describes an actual real-world work programming problem?" – Den Jun 17, 2013 at 13:23
  139. "What's up with the downvotes without a comment giving me a chance to improve the question? The question is purposely extremely simple, as I see no reason to bloat it." – Jim Aho CommentedSep 21, 2017 at 7:56
  140. "Who ever down votes, do you want to explain why, the behaviour is explained, it is not javascript it is the behaviour of the browser. I also showed how to change that behaviour. " – Luke Attard Commented yesterday
  141. "Whoa, ](What is the difference between withLocale() and localizedBy() in Java DateTimeFormatter?)nine[ Down-Votes? This Question is on-topic, well-researched, focused, and important. Why the Down-Votes??" – Basil Bourque 42 mins ago
  142. "Why -1, the question is sensitive." – Timo CommentedOct 8, 2018 at 7:04
  143. "Why am I getting done voted?" – Jeremy CommentedJan 25, 2017 at 9:57
  144. "Why an upvote for a solution with same horrible efficiency like the code by the OP? Sorry, not an appropriate solution for the problem!" – user2665694 CommentedMay 19, 2011 at 5:39
  145. "Why did everyone who responded get blasted with downvotes?" – Michael Kniskern Nov 6, 2008 at 0:10
  146. "Why did this get downvoted? This answer is correct. It may not solve your particular problem, but it is correct." – Doc Commented6 hours ago
  147. "Why down vote? This is just a question?" – Racooon Jan 16, 2012 at 21:27
  148. "Why downvote ? The problem is well explained !" – singe3 Aug 22, 2014 at 9:44
  149. "Why downvote or close? There are numerous reasons why the error message posted by OP can occur. This is one of them." – user2138149 Aug 15 at 11:46
  150. "Why downvoted ?" – calynr Feb 19, 2020 at 8:11
  151. "Why downvoting?? If you know something then it doesn't means everybody knows." – Amrinder Singh CommentedMar 24, 2017 at 5:42
  152. "Why is this downvoted? It worked perfectly for me. Is there a problem with this solution?" – Nadine Jun 8, 2015 at 8:35
  153. "Why is this so downvoted? The question asks about the real problem" – Egor Bobrov CommentedJan 23 at 0:52
  154. "Why the 6 downvotes, please? This question shows research effort, it has expected behaviour and the shortest code to reproduce the surprising behaviour. It may have been asked before, but when searching I didn’t find where, so also would not necessarily expect the OP to be able to find. It’s a good question, to which also the good answers testify." – Anonymous Commentedyesterday
  155. "Why the down-vote? This is a valid useful Question." – Basil Bourque Feb 4, 2019 at 7:25
  156. "Why the downvote? If you think this question is bad, I'd appreciate guidance in how to improve it." – Maddin 20 mins ago
  157. "Why the downvote? This is the working answer for Python3." – Larry K 2 days ago
  158. "Why the downvote?" – RokeJulianLockhart Oct 15 at 21:15
  159. "Why the downvote?" – Simd 3 hours ago
  160. "Why the downvotes on this meta question, what about the meta question is unclear or not useful? What kind of research effort was expected?" – root Commented5 hours ago
  161. "Why the downvotes? This is a basic, but perfectly clear question!" – Spontifixus CommentedSep 21, 2017 at 7:56
  162. "Why the downvotes?" – robertspierre 22 hours ago
  163. "Why this question was voted down?" – Kamarey CommentedAug 17, 2009 at 16:03
  164. "Why was this downvoted? It may not be the best answer, but it seems like a viable solution (and perhaps the easiest) for someone who is new to this! Please leave comments for answers like this, as they are essential not only for the answerer, but for the readers who visit this question later. :-|" – user677526 Jan 8, 2014 at 2:21
  165. "Why was this downvoted? This is a reasonable approach." – Philipp Ludwig Jan 2 at 8:35
  166. "Why was this question down-voted? It seems like a legitimate issue." – erikcw Dec 13, 2010 at 17:28
  167. "Why will question receive a down vote." – satish CommentedAug 21, 2020 at 10:08
  168. "Works very well, I don't see why this deserves a downvote." – Aadvik Commented3 hours ago
  169. "Would the downvoter care to explain their vote? Neither of the duplicates covers elisions, or "empty"." – RobG Dec 4, 2019 at 21:29
  170. "Yuriy L. Over a year ago It is unfairly than this answer was downvoted. Person who make it did not understand the subject matter. Can this person explain here why was downvoted?"
  171. "coldspeed95Over a year ago Downvoter, comment please?"
  172. "dkaminsOver a year ago Why is this downvoted?? Read stackoverflow.com/privileges/vote-down if you don't understand the concept of voting here."
  173. "downvoters should really offer constructive criticism" – dtech Aug 16, 2016 at 21:46
  174. "downvotes with 0 close votes feels excessive and abusive, instead use the duplicate system to help the Asker and the Community or leave a comment as to why this might be a poorly-received Question and how the Asker can make it a good Question!" – ti7 Commented3 hours ago
  175. "honestly, this is a good question. why the downvotes?" – Gewure 5 hours ago
  176. "how come i have gotten 2 thumbs down? i have already stated i have just started learning php" – Mikey Sep 11, 2016 at 11:45
  177. "i don't know why this question is getting downvoted. It seems genuine." – Mike 5 hours ago
  178. "i really don't get why there are so many downvotes, i know 2 of those on both the question and the answer are from people who don't like that i answered my own question.. The rest must be from people who read @jrswgtr mistaken comment.." – Peter Feb 4, 2022 at 7:32
  179. "if anyone is downvoting tell the reason also." – Shayan Kanwal CommentedJul 1, 2021 at 9:20
  180. "not sure why this question is so poorly received given its very similar to my last question. thanks for keeping this site's reputation so stinky julien" – user31409481 Commented10 mins ago
  181. "please give solution,why negative marked?" – user6413618 CommentedJun 4, 2016 at 4:26
  182. "sazzy4oOver a year ago What is wrong with this answer? It seemed to work for me. If there is something I need to fix, please comment"
  183. "simhumileco Over a year ago What is wrong with this answer? Why somebody gives me -1 vote? Maybe I can improve it, if I will know what is wrong with this current one? Please help me smebody, who know what could be wrong. Thank you in advance."
  184. "user314159 8 hours ago @DV: Too busy closing questions or too chicken to leave a comment?"
  185. "why downvotes it's a valid question "Could anyone please explain with an example how these two traits change the behavior of implementers?" please answer this" – ravi Feb 22 at 5:01
  186. "why is not useful? dont be a KIM of Northkorea.. explain..." – HydTechie CommentedSep 11, 2024 at 17:36
  187. "why the down vote ?" – ticktalk 2 days ago
  188. "why this -1? can you explain please?" – Codegiant Feb 14, 2013 at 10:58
  189. "why you marking me down? It's a simple, straightforward question." – Claire May 15, 2012 at 14:53
  190. "wonder why was this downvoted? makes sense for the error to be related to packet size..." – FlorinelChis CommentedMar 25, 2016 at 16:47
  191. "wondering what is missing from the question thats attracting so many downvotes?" – Isabella yesterday

And a surprising admission about an unintended downvote: "@Booboo hey i think it's mee hehe, i just made this stack overflow acc and i dont really know what im pressing im sorry dudeee – Rugal" then "at first i thought it was a scroll button for other comments – Rugal"

28
  • 6
    But it has to be anonymous, or revenge. Commented yesterday
  • 2
    "If users are being consistently unconstructive in their activity, maybe they are abusing the tools and doing unnecessary harm to the platform/community." This goes both ways then, yes? People being unconstructive about the feedback they received is meant by this as well, yes? Commented yesterday
  • 5
    Over what period of time is this data? I see a few timestamps from 201X and you say you keep collecting still. ~200 such comments, some for even just one downvote, over more than a decade… that is incredibly much less than I would have estimated. Not sure what you are trying to say with this, it doesn’t seem to help your point at all. Commented yesterday
  • 2
    @MisterMiyagi Over what period of time? I think I started caching last year when there was an entire camp of MSO users who absolutely hated the notion of providing reasons with downvotes. I collect these comments as I encounter them as a curating moderator (mostly from NLN-flagged comments). Don't worry, there will be thousands more of these that only staff can query for. Commented yesterday
  • 2
    Thank you for feeling the pain of people who ask questions in good faith and receive unhelpful negative feedback in the form of mystery downvotes. These users are very under-represented in Meta. And their questions are more helpful and in-line with SO's goals than the Meta community would make you believe. Commented yesterday
  • 8
    I don't think this list of comments taken out of context is useful useful without the context of the question/answer they were posted on as well as the context/tone of the comment section they came out of. Commented 23 hours ago
  • 4
    or we could have more staging ground- a dedicated time and space for giving feedback on how to improve a post, before voting can happen. Commented 22 hours ago
  • 3
    I don't think a company who is trying to recover lost members (or those who care about the community) can reasonably ignore ~200 such complaints (with or without context) especially knowing that this is just the tip of the iceberg. The staging ground does nothing to combat no-comment downvotes on answers. Commented 22 hours ago
  • 12
    Attaching reasons to only downvotes is unproductive. I see at least as much content being upvoted, when it shouldn't be. Think harmful answers, answers which don't answer the question, unsalvagable questions which get upvoted, not because the question is good, but just to get in the way of curation... This whole "Downvotes are hostile" bandwagon is tiring. Unless you can come up with a solution to most of the problems in that meta question? Commented 22 hours ago
  • 2
    That shield that gets lifted up every time someone dares to remind MSO just how much discontent there is around unexplained downvotes is very outdated and should be edited. I have, in the past, had sound arguments for each item, but the same entrenched voices on MSO will simply never have it so it is not worth posting on MSO. I am not asking MSO to fix the problem, I'm asking the company. I knew I would hear from all the same voices just like the last times I pointed out the obvious - people who are downvoted want to understand why so that they can learn and improve. Commented 21 hours ago
  • 3
    How nice to see mod powers were used here to clean up the feedback so it looks neat. Guess what, that’s not how it works for us plebs. I have given tons of feedback during my active time on SO/SE, and see this in dire need of improvement; but the way this agenda is pushed is something that needs to stop because it is undermining the very thing it claims to advocate for. Commented 21 hours ago
  • 4
    As problematic as it may or may not be, I've never once heard anyone say that they quit using Stack Overflow because of no-comment upvotes. I have seen comments which say [why does this incorrect answer have a positive score or a green tick], heck I've typed some...but no one is quitting Stack Overflow for unexplained upvotes ... no one. Therefore, it makes sense to tackle primary drivers for membership loss before targeting other valuable refinements. Commented 21 hours ago
  • 3
    @IvanPetrov I'm not completely against attaching a reason to downvotes. I'm saying upvotes can be just as harmful. Commented 16 hours ago
  • 2
    folks, I recognize that extra feedback with downvotes is a contentious topic. remember to treat one another with dignity and respect. I'll provide the same encouragements I wrote here: listen to one another with open minds, seek others' viewpoints of issues and consider their merit, speak in a way that exemplifies and facilitates respectful discourse, offer and receive feedback with grace towards one another, and respond to criticism and disagreement with a cool head. Commented 10 hours ago
  • 4
    I haven't downvoted (yet), but you can't seriously expect everyone reading your answer to read through a list of 190 comments. Commented 7 hours ago

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.