mccHard to imagine a signal that a website is a rugpull more intense than banning users for trying to delete their own posts
Like just incredible "burning the future to power the present" energy here
tuban_muzuruI have dealt with novice coders for 40 years. I've told them to steer clear of SO - ask me if you've got a question about anything.
#StuckOverflow isn't entirely bad, but there's enough rat shit stirred into that pudding I would never trust anything trained on its data.
@tuban_muzuru I like Stack Overflow, but the problem with it is that it's so old that many of the questions are from like 2008-2015 and that means that often it gives you an answer that was correct ten years ago but is wrong now. (Sometimes they exacerbate this by closing a new question because it's a duplicate of a 2010 one full of outdated answers!)
So… the new "don't forget, you're here forever" policies will probably exacerbate this problem, if fewer high-quality answers come in after 2024.
Jeremy KahnFukuyama's got nothing on _this_ End of History
That's a really good point - answers don't stay right forever.
Shane Celis@mcc @tuban_muzuru They’ve invited the query rot and nothing seems to suggest they don’t like it that way.
Kevin Boyd (he/him) 🇨🇦@mcc @tuban_muzuru I was never much of a participant, something about the participatory experience soured me right off the bat.
Glad I stayed away.
Dr. Brandon Wiley@mcc @tuban_muzuru I was pondering the world after the demise of Stack Overflow and while I have depended heavily on it's use in my career as a professional programmer, I think the real problem is that we need it at all. The modern condition of programming being mostly copy-pasting Stack Overflow answers is a symptom of a much greater problem. Programming is too complicated because we have made it too complicated, we should all work together to make it easier instead. That's my opinion, anyway!
After a while, patterns are seen, problems revisited, writing a program to spec - the problem isn't complication, often.
When you run across what you think is a needlessly complex solution - you are looking at a compromise. Comment it and ride it through the debugger - but don't rewrite it immediately ....
araly@tuban_muzuru @mcc
i'll always remember taking the time to write a full question, with what i tried and what didn't work, to receive an answer that just said "duplicate, closing", without linking to where the duplicate was.
meanwhile a friend who wasn't a programmer asked the same question at the same time but super vague and with minimal effort. he got answers instantly (that were not usable because too vague).
if you punish effort and only answer the easy questions, i don't want any part of it
i'll always remember taking the time to write a full question, with what i tried and what didn't work, to receive an answer that just said "duplicate, closing", without linking to where the duplicate was.
meanwhile a friend who wasn't a programmer asked the same question at the same time but super vague and with minimal effort. he got answers instantly (that were not usable because too vague).
if you punish effort and only answer the easy questions, i don't want any part of it