llm/7c7e49f1-870c-4915-9398-3b2e1f116c0c/topic-8-3222a1bb-8725-4eea-8f11-e9ac1ec97929-input.json
You are a comment summarizer. Given a topic and a list of comments tagged with that topic, write a single paragraph summarizing the key points and perspectives expressed in the comments. TOPIC: Expert knowledge preservation COMMENTS: 1. > This is why all the moderation pushes toward deleting duplicates of questions, and having a single accepted answer. My personal single biggest source of frustration with SO has been outdated answers that are locking out more modern and correct answers. There are so many things for which there is no permanently right answer over time. It feels like SO started solidifying and failed to do the moderation cleaning and maintenance needed to keep it current and thriving. The over-moderation you described helps people for a short time but then doesn’t help the person who googles much later. I’ve also constantly wished that bad answers would get hidden or cleaned out, and that accepted answers that weren’t very good would get more actively changed to better ones that showed up, it’s pretty common to see newer+better answers than the accepted one. 2. > it looks to me like I could figure it out pretty easily from what's written there Really? Wanna give it a try then, without looking up any other documentation? I've used ffmpeg plenty of times, but it doesn't seem obvious to me how I'd mute one audio channel. From your other comments it sounds like you believe SO should have less content. Why? How would SO be improved by forcing people to figure something like this out from the existing answer? I just don't understand the benefit to having that question marked as a duplicate and deleted. I've long wondered the same thing about wikipedia. Why does wikipedia delete well written pages about obscure topics? Is their hard disk full? Does every page cost them money? Does google search struggle at scale? I don't understand the benefit to deleting good content. 3. LLMs also search Google for answers. Hence the knowledge may be not lost even for those who only supervises machines that write code. 4. Labs are spending billions on data set curation and RL from human experts to fill in the areas where they're currently weak. It's higher quality data than SO, the only issue is that it's not public. 5. Can you explain what you're saying in greater depth? Are you saying that the reason there is no human expertise on the internet anymore is that everyone with knowledge is now under contract to train AIs? 6. No, I think the reason human expertise on the internet is dying out is because we have a cacophany of voices trying to be heard on the internet, and experts aren't interested in screaming into the void unless they directly need to do it to pay their bills. 7. Instead of having chat-interfaces target single developers, moving towards multiplayer interfaces may bring back some of what has been lost--looping in experts or third-party knowledge when a problem is too though to tackle via agentic means. Now all our interactions are neatly kept in personalised ledgers, bounded and isolated from one another. Whether by design or by technical infeasability, the issue remains that knowledge becomes increasingly bounded too instead of collaborative. 8. We'll get to the point where we can mass moderate core knowledge eventually. We may need to hand out extra weight for verified experts and some kind of most-votes-win type logic (perhaps even comments?), but live training data updates will be a massive evolution for language models. 9. What I always appreciate about SO is the dialogue between commenters. LLMs give one answer, or bullet points around a theme, or just dump a load of code in your IDE. SO gives a debate, in which the finer points of an issue are thrashed out, with the best answers (by and large) floating to the top. SO, at its best, is numerous highly-experienced and intelligent humans trying to demonstrate how clever they are. A bit like HN, you learn from watching the back and forth. I don't think this is something that LLMs can ever replicate. They don't have the egos and they certainly don't have the experience. Whatever people's gripes about the site, I learned a hell of a lot from it. I still find solutions there, and think a world without it would be worse. 10. The other major benefit of SO being a public forum is that once a question was wrestled with and eventually answered, other engineers could stumble upon and benefit from it. With SO being replaced by LLMs, engineers are asking LLMs the same questions over and over, likely getting a wide range of different answers (some correct and others not) while also being an incredible waste of resources. 11. What I'm appreciating here is the quality of the _best_ human responses on SO. There are always a number of ways to solve a problem. A good SO response gives both a path forward, and an explanation why, in the context of other possible options, this is the way to do things. LLMs do not automatically think of performance, maintainability, edge cases etc when providing a response, in no small part because they do not think. An LLM will write you a regex HTML parser.[0] The stats look bleak for SO. Perhaps there's a better "experience" with LLMs, but my point is that this is to our detriment as a community. [^0]: He comes, https://stackoverflow.com/questions/1732348/regex-match-open... 12. This comment and the parent one make me realize that people who answer probably value the exchange between experts more than the answer. Perhaps the antidote involves a drop of the poison. Let an LLM answer first, then let humans collaborate to improve the answer. Bonus: if you can safeguard it, the improved answer can be used to train a proprietary model. 13. > This comment and the parent one make me realize that people who answer probably value the exchange between experts more than the answer. I'm more amused that ExpertsExchange.com figured out the core of the issue, 30 years ago, down to their site's name. 14. There are so many "great" answers on StackOverflow. Giving the why and not just the answer. 15. >> Eventually I tried with something else, and found a question on stackoverflow, luckily with an answer. That was the game changer and eventually I was able to find the right doc Read carefully and paraphrase to the generous side. The metaphor that follows that is obviously trying to give an example of what might be somehow lost. 16. > People in this thread are missing another key component in the decline of StackOverflow - the more experienced you become, the less useful it is. This is literally not true. The rate you learn and encounter new things depends on many things: you, your mood, your energy etc. But not on the amount of your experience. > The harder the problem, the less engagement it gets. People who spend hours working on your issue are rewarded with a single upvote. This is true, but not relevant, I don't think many people care. Some might, but not many. 17. I don't know what your experience has been, but I do feel that at some point you will find yourself on or beyond SO's "knowledge frontier". The questions you land on will be unanswered or have equally confused replies; or you might be the one who's asking a question instead. I've "paid back" by leaving a high quality response on unanswered SO questions that I've had to figure out myself, but it felt quite thankless since even the original poster would disappear, and anyone who found my answer from Google wouldn't be able to give me an upvote either. 18. No, you don't. Not only there are many examples of detailed stackoverflow articles written by absolute experts, you also need answer often for something trivial(which is like half of my chatgpt), e.g. how to export in pgadmin, or a nondescriptive error in linux. 19. I think it is true, but not because you have nothing more to learn when you're experienced, but that there are fewer and fewer people on SO to answer the questions that you encounter when you get more and more experienced. I've answered about 200 questions. I've asked two, and both remain unanswered to this day. One of them had comments from someone who clearly was out of their league but wanted to be helpful. The people who could've answered those questions are not (or were not at that time) on SO. 20. The idea of one “accepted answer” there always bugged me. The correct/best answer of many things changes radically over time. For instance The only sane way to do a lot of things in “JavaScript” in 2009 was to install jquery and use it. Most of those same things can (and should) be done just as succinctly with native code today, but the accepted answers in practice were rarely updated or changed. I don’t even know if you could retroactively years later re-award it to a newer answer. Since the gamification angle was so prominent, that might rob the decade-old author of their points for their then-correctness, so idk if they even allowed it. 21. This has been my experience. My initial (most popular) questions (and I asked almost twice as many questions, as I gave answers) were pretty basic, but they started getting a lot more difficult, as time went on, and they became unanswered, almost always (I often ended up answering my own question, after I figured it out on my own). I was pretty pissed at this, because the things I encountered, were the types of things that people who ship, encounter; not academic exercises. Tells me that, for all the bluster, a lot of folks on there, don't ship. LLMs may sometimes give pretty sloppy answers, but they are almost always ship-relevant. 22. Maybe there's a key idea for something to replace StackOverflow as a human tech Q&A forum: Having a system which somehow incentivizes asking and answering these sorts of challenging and novel questions. These are the questions which will not easily be answered using LLMs, as they require more thought and research. 23. And you can't delete your post when you realize how awful it was years later! That anti-information sticks around for ages. Even worse when there are bad answers attached to it, too. 24. If you're talking about deleting questions, that's because deleting the question would delete everyone's answers that they potentially worked very hard on and which others might find useful. If you think the answers are bad you can always post your own competing answer. 25. StackOverflow answers are outdated. Every time I end up on that site these days, I find myself reading answers from 12 years ago that are no longer relevant. 26. I see plenty of old answers that are still very relevant. Suppose it depends on what language/tech tags you follow. 27. There have been many times I have seen someone complain on the meta site about answers being old and outdated, and then they give specific examples, and I go check them out and they're actually still perfectly valid. 28. Many people are pointing out the toxicity, but the biggest thing that drove me away, especially for specific quantitative questions, was that SO was flat out wrong (and confidently so) on many issues. It was bad enough that I got back in the habit of buying and building a library of serious reference books because they were the only reliable way to answer detailed technical questions. 29. Actual analysts here that have looked at this graph like... a lot, so let me contextualize certain themes that tend to crop up from these: - The reduction of questions over time is asymptomatic of SO. When you have a library of every question asked, at some point, you asked most of the easy questions. Have a novel question becomes hard. - This graph is using the Posts table, not PostsWithDeleted. So, it only tells you of the questions that survived at this point in time, this [0] is the actual graph which while describes a curve that shows the same behavior, it's more "accurate" of the actual post creation. - This is actually a Good Thing™. For years most of the questions went unanswered, non-voted, non-commented, just because there was too many questions happening all the time. So the general trend is not something that the SO community needs to do anything about. Almost 20% of every question asked is marked as duplicate. If people searched... better™ they wouldn't ask as many questions, and so everyone else had more bandwidth to deal with the rest. - There has been a shift in help desk style of request, where people starting to prefer discord and such to get answers. This is actually a bad thing because that means that the knowledge isn't public nor indexed by the world. So, information becomes harder to find, and you need to break it free from silos. - The site, or more accurately, the library will never die. All the information is published in complete archives that anyone can replicate and restart if the company goes under or goes evil. So, yeah, such concerns, while appreciated, are easily addressed. At worst, you would be losing a month or two of data. [0]: https://data.stackexchange.com/stackoverflow/query/edit/1926... 30. At my place of work we use an indexing service for discord that creates an index of searchable static pages for all discord interactions. So while I agree the help desk style system isn’t really better it also doesn’t necessarily mean that it is lost forever in a silo. Before you ask, we use https://www.linen.dev/ but I’m sure there are other similar solutions by now 31. I once published a method for finding the closest distance between an ellipse and a point on SO: https://stackoverflow.com/questions/22959698/distance-from-g... I consider it the most beautiful piece of code I've ever written and perhaps my one minor contribution to human knowledge. It uses a method I invented, is just a few lines, and converges in very few iterations. People used to reach out to me all the time with uses they had found for it, it was cited in a PhD and apparently lives in some collision plugin for unity. Haven't heard from anyone in a long time. It's also my test question for LLMs, and I've yet to see my solution regurgitated. Instead they generate some variant of Newtons method, ChatGPT 5.2 gave me an LM implementation and acknowledged that Newtons method is unstable (it is, which is why I went down the rabbit hole in the first place.) Today I don't know where I would publish such a gem. It's not something I'd bother writing up in a paper, and SO was the obvious place were people who wanted an answer to this question would look. Now there is no central repository, instead everyone individually summons the ghosts of those passed in loneliness. 32. The various admonitions to publish to a personal blog, while encouraging, don't really get at the 0xfaded's request which I'd summarize as follows: With no one asking questions these technical questions publicly, where, how and on what public platform will technical people find the problems that need solving so they can exercise their creativity for the benefit of all? 33. Clearly we need something in between the fauxpen-access of journals and the wilde west of the blogosphere, probably. Why wouldn't the faded ox publish in a paper? Idk, but I guess we need things similar to those circulars that British royal society members used to send to each other...except not reserved for a club. The web should be a natural at this. But it's either centralized -> monetized -> corrupted, or decentralized -> unindexed/niche -> forgotten fringe. What can come between? 34. I wonder if there could be something like a Wikipedia for programming. A bit like what the book Design Patterns did in 1994, collecting everyone's useful solutions, but on a much larger scale. Everyone shares the best strategies and algorithms for everything, and updates them when new ones come about, and we finally stop reinventing the wheel for every new project. To some extent that was Stack Overflow, and it's also GitHub, and now it's also LLMs, but not quite. May I suggest "PASTE": Patterns, Algorithms, Solutions, Techniques, and Examples. "Just copy PASTE", they'll say. 35. Ward Cunningham once, of all places in an Github issue [0], explained how the original C2 Wiki was seeded. > Perhaps I should explain why wiki worked. > I wrote a program in a weekend and then spent two hours a day for the next five years curating the content it held. For another five years a collection of people did the same work with love for what was there. But that was the end. A third cohort of curators did not appear. Content suffered. A heroic amount effort of a single person, and later the collective effort of a small group, worked in the mid-90es. I'm skeptical that it will be repeatable 30 years later. Despite this, it would be the type of place, that I'd like to visit on the web. :( [0] https://github.com/WardCunningham/remodeling/issues/51#issue... 36. Great idea! https://paste.voklen.com/wiki/Main_Page If people start using it I'll get a proper domain name for it. 37. An algolwiki is a great idea, but I just wanted to say I got a good chuckle from this, thanks :) > May I suggest "PASTE": Patterns, Algorithms, Solutions, Techniques, and Examples. "Just copy PASTE", they'll say. 38. There is https://grokipedia.com which encourages you to suggest an article and you may submit improvements to an existing article. 39. This is _not_ at all the same thing. Grok just ripped off Wikipedia as its base and then applied a biased spin to it. Check out the entry on Grok owner Elon Musk; it praises his accomplishments and completely omits or downplays most of his better-known controversies. 40. There is https://www.wikifunctions.org/ 41. > Clearly we need something in between the fauxpen-access of journals and the wilde west of the blogosphere, probably. I think GP's min-distance solution would work well as an arxiv paper that is never submitted for publication. A curated list of never-published papers, with comments by users, makes sense in this context. Not sure that arxiv itself is a good place, but something close to it in design, with user comments and response-papers could be workable. Something like RFC, but with rich content (not plain-text) and focused on things like GP published (code techniques, tricks, etc). Could even call it "circulars on computer programming" or "circulars on software engineering", etc. PS. I ran an experiment some time back, putting something on arxiv instead of github, and had to field a few comments about "this is not novel enough to be a paper" and my responses were "this is not a publishable paper, and I don't intend to submit it anywhere". IOW, this is not a new or unique problem. (See the thread here - https://news.ycombinator.com/item?id=44290315 ) 42. There is the Journal of Open Source Software perhaps: https://joss.theoj.org/ 43. And discord is a terrible tool for knowledge collection imo. Their search is ok, but then I find myself digging through long and disjointed message threads, if replies/threading are even used at all by the participants. 44. This is a perfect example of an element of Q&A forums that is being lost. Another thing that I don't think we'll see as much of anymore is interaction from developers that have extensive internal knowledge on products. An example I can think of was when Eric Lippert, a developer on the C# compiler at the time, responded to a question about a "gotcha" in the language: https://stackoverflow.com/a/8899347/10470363 Developer interaction like that is going to be completely lost. 45. A lot of valuable information lived/lives in email threads that might or might not be publicly archived. 46. The second answer cites Lippert's pre-existing blog post on the subject: https://ericlippert.com/2009/11/12/closing-over-the-loop-var... I agree that there will be some degradation here, but I also think that the developers inclined to do this kind of outreach will still find ways to do it. 47. I had a similar beautiful experience where an experienced programmer answered one of my elementary JavaScript typing questions when I was just starting to learn programming. He didn't need to, but he gave the most comprehensive answer possible attacking the question from various angles. He taught me the value of deeply understanding theoretical and historical aspects of computing to understand why some parts of programming exist the way they are. I'm still thankful. If this was repeated today, an LLM would have given a surface level answer, or worse yet would've done the thinking for me obliviating the question in the first place. I wrote a blog post about my experience at https://nmn.gl/blog/ai-and-learning 48. Had a similar experience. Asked a question about a new language feature in java 8 (parallell streams), and one of the language designers (Goetz) answered my question about the intention of how to use it. An LLM couldn't have done the same. Someone would have to ask the question and someone answer it for indexing by the LLM. If we all just ask questions in closed chats, lots of new questions will go unanswered as those with the knowledge have simply not been asked to write the answers down anywhere. 49. You can write a paper, submit the arxiv, and you can also make a blog post. At any rate, I agree - SO was (is?) a wonderful place for this kind of thing. I once had a professor mention that they knew me from SO because I posted a few underhanded tricks to prevent an EKF from "going singular" in production. That kind of community is going to be hard to replace, but SO isnt going anywhere, you can still ask a question and answer your own question for permanent, searchable archive. 50. You should write it up and submit it to some journal officially. Doesn't matter if it mostly duplicates your own (technically unpublished) work. 51. I have a similar story about an interesting little advance in computing that I haven't formally published anywhere, but it's at https://cs.stackexchange.com/a/171695/50292 The question boils down to: can you simulate the bulk outcome of a sequence of priority queue operations (insert and delete-minimum) in linear time, or is O(n log n) necessary. Surprisingly, linear time is possible. 52. Then let me quickly say: thank you! I used that algorithm three times in different projects during my academic "career" :-) 53. > Today I don't know where I would publish such a gem. In the same blog you published it originally, then mentioning it on whatever social media site you use? So same? 54. Sounds like this should live in Wikipedia somewhere on https://en.wikipedia.org/wiki/Ellipse...or maybe a related but more CS focused related page. 55. If you ask me your blog post is basically a paper, I’d publish to arxiv. 56. Yes, LLMs are great at answering questions, but providing reasonable answers is another matter. Can you really not think of anything that hasn't already been asked and isn't in any documentation anywhere? I can only assume you haven't been doing this very long. Fairly recently I was confronted with a Postgres problem, LLMs had no idea, it wasn't in the manual, it needed someone with years of experience. I took them IRC and someone actually helped me figure it out. Until "AI" gets to the point it has run software for years and gained experience, or it can figure out everything just by reading the source code of something like Postgres, it won't be useful for stuff that hasn't been asked before. 57. I think you overestimate 2 by a longshot most problems only appear novel because they couched in a special field, framework or terminology, otherwise it would be years of incremental work. Some are, they are more appropriately put in a recreational journal or BB. The reason the "experts" hung around SO was to smooth over the little things. This create a somewhat virtuous cycle, but required too much moderation and as other have pointed out, ultimately unsustainable even before the release of LLMs. 58. I do use Claude a lot, but I still regularly ask questions on https://bioinformatics.stackexchange.com/ . It's often just too niche, LLMs hallucinate stuff like an entire non-existent benchmarking feature in Snakemake, or can't explain how I should get transcriptome aligners to give me correct quantifications for a transcript. I guess it's too niche. And as a lonely Bioinformatician it can be nice to get confirmation from other bioinformaticians. Looking back at my Stack Exchange/Stack Overflow (never really got the difference) history, my earlier, more general programming questions from when I just started are all no-brainers for any LLM. 59. I joined Stackoverflow early on since it had a prevalence towards .NET and I’ve been working with Microsoft web technologies since the mid 90’s. My SO account is coming up to 17 years old and I have nearly 15,000 points, 15 gold badges, including 11 famous questions and similar famous answer badges, also 100 silver and 150 bronze. I spent far much time on that site in the early days, but through it, I also thoroughly enjoyed helping others. I also started to publish articles on CodeProject and it kicked off my long tech blogging “career”, and I still enjoy writing and sharing knowledge with others. I have visited the site maybe once a year since 2017. It got to the point that trying to post questions was intolerable, since they always got closed. At this point I have given up on it as a resource, even though it helped me tremendously to both learn (to answer questions) and solve challenging problems, and get help for edge cases, especially on niche topics. For me it is a part of my legacy as a developer for over 30 years. I find it deeply saddening to see what it has become. However I think Joel and his team can be proud of what they built and what they gave to the developer community for so many years. As a side note it used to state that was in the top 2% of users on SO, but this metric seems to have been removed. Maybe it’s just because I’m on mobile that I can’t see it any more. LLM’s can easily solve those easy problems that have high commonality across many codebases, but I am dubious that they will be able to solve the niche challenging problems that have not been solved before nor written about. I do wonder how those problems get solved in the future. 60. Are we in the age of all CS problems being solved and everything being invented? Even if so, do LLM incorporate all that knowledge? A lot of my knowledge in CS come from books and lectures, LLMs can shine in that area by scraping all those sources. However SO was less about academic knowledge but more about experience sharing. You won't find recipes for complex problems in books, e.g. how to catch what part of my program corrupts memory for variable 'a' in gdb. LLMs know correct answer to this question because someone shared their experience, including SO. Are we Ok with stopping this process of sharing from one human to another? 61. I was tasked to add OpenOffice's hyphenation lib to our software at work back in 2010 when I was a junior dev. I had to read the paper and the C code/documentation to understand how it works but got stuck in one particular function. It was such an obscure thing (compare to web dev stuffs) that I couldn't find anything on Google. Had no choice but to ask on Stackoverflow and expected no answers. To my surprise, I got a legit answer from someone knowledgable, and it absolutely solve my problem at the time. (The function has to do with the German language, which was why I didn't understand the documentation) It was a fond memory of the site for me. 62. One thing you won’t get with in an LLM is genuine research. I once answered a 550 point question by researching the source code of vim to see how the poster’s question could be resolved. [0] [0] https://stackoverflow.com/questions/619423/backup-restore-th... 63. It's unfortunate that SO hasn't found a way to leverage LLMs. Lots of questions benefit from some initial search, which is hard enough that moderators likely felt frustrated with actual duplicates, or close enough duplicates, and LLMs seem able to assist. However I hope we don't lose the rare gem answers that SO also had, those expert responses that share not just a programming solution but deeper insight. 64. I am surprised at the amount of hate for Stack Overflow here. As a developer I can't think of a single website that has helped me as much over the last ten years. It has had a huge benefit for the development community, and I for one will mourn its loss. I do wonder where answers will come from in the future. As others have noted in this thread, documentation is often missing, or incorrect. SO collected the experiences of actual users solving real problems. Will AI share experiences in a similar way? In principle it could, and in practice I think it will need to. The shared knowledge of SO made all developers more productive. In an AI coded future there will need to be a way for new knowledge to be shared. 65. Someone needs to archive the entirety of StackOverflow and make it available over torrent so that it can be preserved when the site shuts down. Urgently. 66. https://archive.org/details/stackexchange Found it 67. https://archive.org/details/stackexchange_20250930 > As of (and including) the 2025-06-30 data dump, Stack Exchange has started including watermarking/data poisoning in the data. At the time of writing, this does not appear to apply to the 2025-09-30 data dump. The format(s), the dates for affected data dumps, and by extension how the garbage data can be filtered out, are described in this community-compiled list: https://github.com/LunarWatcher/se-data-dump-transformer/blo... . If the 2025-09-30 data dump turns out to be poisoned as well, that's where an update will be added. For obvious reasons, the torrent cannot be updated once created. 68. Now that StackOverflow has been killed (in part) by LLMs, how will we train future models? Will public GitHub repos be enough? Precise troubleshooting data is getting rare, GitHub issues are the last place where it lives nowadays. 69. The brilliance of StackOverflow was in being the place to find out how to do tricky workarounds for functionality that either wasn't documented or was buggy such that workarounds were needed to make it actually work. Software quality is now generally a bit better than it was in 2010, but that need is ultimately still there. 70. Was already dying a decade ago, but AI pretty much guarantees we'll never see a public forum that useful ever again. AI may be fine for people asking the basic stuff or who don't care about maintenance, but for a time SO was the place to find extraordinary and creative solutions that only a human can come up with. When you were in a jam and found a gem on there it not only solved your problem, but brought clarity and deep knowledge to your entire situation in ways that I've never seen an LLM do. It inspired you to refactor the code that got you into that mess to begin with and you grew as a developer. This timeline shows the death of a lot more than just the site itself. 71. This entire thread is fantastic. I felt nostalgic, angry and then concerned all at once. I love LLMs. But I miss SO. I miss being able to have that community. How do we bring it back? If anyone from the Stack Overflow team is reading this (I assume you are): what’s the plan? My take: stop optimizing for raw question volume and start optimizing for producing and maintaining “known good” public knowledge. The thing SO still has that Discord and LLMs don’t is durable, linkable, reviewable answers with accountable humans behind them. But the workflow needs to match how devs work now. A concrete idea: make “asking” a guided flow that’s more like opening a good GitHub issue. Let me paste my error output, environment, minimal repro, what I tried, and what I think is happening. Then use tooling (including an LLM if you want) to pre check duplicates, suggest missing details, and auto format. Crucially: don’t punish me for being imperfect. Route borderline questions into a sandbox or draft mode where they can be improved instead of just slammed shut. Second idea: invest hard in keeping answers current. A ton of SO is correct but stale. Add obvious “this is old” signaling and make it rewarding to post updates, not just brand new answers. Last thing that I don’t see an easy answer to: LLMs are feasting on old SO content today. But LLMs still need fresh, high quality, real world edge cases tomorrow. They need the complexity and problem solving that humans provide. A lot of the answers I get are recycled. No net new thinking. If fewer people ask publicly, where does that new ground truth come from? What’s the mechanism that keeps the commons replenished? So… TLDR…my question to this group of incredibly intelligent people: how does SO save itself? Write a concise, engaging paragraph (3-5 sentences) that captures the main ideas, notable perspectives, and overall sentiment of these comments regarding the topic. Focus on the most interesting and representative viewpoints. Do not use bullet points or lists - write flowing prose.
Expert knowledge preservation
71