The technically incorrect issue is downstream of their rigid policies.
Yes, answers which were accepted go Python 2 may require code changes to run on Python 3. Yes, APIs
One of the big issues is that accepted answers grow stale over time, similar to bitrot of the web. But also, SO is very strict about redirecting close copies of previously answered questions to one of the oldest copies of the question. This policy means that the question asker is frustrated when their question is closed and linked to an old answer, which may or may not answer their new question.
But the underlying issue is that SO search is the lifeblood of the app, but the UX is garbage. 100% of searches show a captcha when you are logged out. The keyword matching is tolerable, but not great. Sometimes Google dorking with `site:stackoverflow.com` is better than using SO search.
Ultimately, the UX of LLM chatbots are better than SO. It’s possible that SO could use a chatbot interface to replace their search and improve usability by 10x…
Yes, answers which were accepted go Python 2 may require code changes to run on Python 3. Yes, APIs
One of the big issues is that accepted answers grow stale over time, similar to bitrot of the web. But also, SO is very strict about redirecting close copies of previously answered questions to one of the oldest copies of the question. This policy means that the question asker is frustrated when their question is closed and linked to an old answer, which may or may not answer their new question.
But the underlying issue is that SO search is the lifeblood of the app, but the UX is garbage. 100% of searches show a captcha when you are logged out. The keyword matching is tolerable, but not great. Sometimes Google dorking with `site:stackoverflow.com` is better than using SO search.
Ultimately, the UX of LLM chatbots are better than SO. It’s possible that SO could use a chatbot interface to replace their search and improve usability by 10x…