Re:The Fall of Stack Overflow
by j45 on Monday July 31, 2023 @05:22PM
(#36949037)
When technology can solve a problem equivalently well in so many ways discussion and debate is the way to learn from the experiences of others to help navigate your own course.
When it comes to adult learning, some people with some topics prefer to only know the answer of what they’re after or other times want a bigger picture.
Last but not least learning to read the code and system design decisions of others are both required for competent software development.
The part that stack avoided is maximum value comes from is understanding that decision making is the key in a lot of the underlying intent of users coming there … not just a snippet of code in system design.
Not know what you should be looking for or if there’s other ways to do things is a big lose in the development of software engineers.
How do I know this beyond my subjective interpretation and preference?
I was an early user of stack overflow.
It was a heavy time of software development, and I could easily spent 4-6 hours a day on it. So I decided to write. I learned so much, and shared anything I could. It really was a great early community.
I really disliked Experts Exchange and it was one of the major inspirations for SO to happen.
Little by little, I noticed some of my posts of hard earned lessons attached to a solution, started getting locked down.
People deciding how things should be interpreted one way. Correcting answers they don’t understand.
Answers started getting rejected. Context had no value. That’s not a great recipe for success.
The strange thing is I still sit in the top X percent of stack users for not having answered anything in a while, and still get upvotes and comments.
How to schedule multiple parties to ensure eveyrone has dace tkme?
Sorry, explaining steps in English is not code or acceptable. It apparently can’t be translated to different programming languages.
Software is for people in the real world, not strictly a technical pursuit.
SO started their network of other sites but the bar to entry was too high. There’s lots of extremely valuable but esoteric design knowledge that remotely being aware of or having access to can be tremendously helpful.
Stack overflow didn’t understand or care it was helping system design to be better.
Architecture goes bad in hand with code and I don’t know how you can talk about either effectively on the whole with the ability to refer to the other. With out it the trees don’t always become a forest.
When it comes to adult learning, some people with some topics prefer to only know the answer of what they’re after or other times want a bigger picture.
Last but not least learning to read the code and system design decisions of others are both required for competent software development.
The part that stack avoided is maximum value comes from is understanding that decision making is the key in a lot of the underlying intent of users coming there … not just a snippet of code in system design.
Not know what you should be looking for or if there’s other ways to do things is a big lose in the development of software engineers.
How do I know this beyond my subjective interpretation and preference?
I was an early user of stack overflow.
It was a heavy time of software development, and I could easily spent 4-6 hours a day on it. So I decided to write. I learned so much, and shared anything I could. It really was a great early community.
I really disliked Experts Exchange and it was one of the major inspirations for SO to happen.
Little by little, I noticed some of my posts of hard earned lessons attached to a solution, started getting locked down.
People deciding how things should be interpreted one way. Correcting answers they don’t understand.
Answers started getting rejected. Context had no value. That’s not a great recipe for success.
The strange thing is I still sit in the top X percent of stack users for not having answered anything in a while, and still get upvotes and comments.
How to schedule multiple parties to ensure eveyrone has dace tkme?
Sorry, explaining steps in English is not code or acceptable. It apparently can’t be translated to different programming languages.
Software is for people in the real world, not strictly a technical pursuit.
SO started their network of other sites but the bar to entry was too high. There’s lots of extremely valuable but esoteric design knowledge that remotely being aware of or having access to can be tremendously helpful.
Stack overflow didn’t understand or care it was helping system design to be better.
Architecture goes bad in hand with code and I don’t know how you can talk about either effectively on the whole with the ability to refer to the other. With out it the trees don’t always become a forest.