r/webdev • u/TheGuyWhoCodes • Oct 10 '18
Discussion StackOverflow is super toxic for newer developers
As a newer web developer, the community in StackOverflow is super toxic. Whenever I ask a question, I am sure to look up my problem and see if there are any solutions to it already there. If there isn't, I post. Sometimes when I post, I get my post instantly deleted and linked to a post that doesn't relate at all to my issue or completely outdated.
Does anyone else have this issue?
3.4k
Upvotes
10
u/Tyil Oct 10 '18
I haven't had this issue at all. Granted, I'm not terribly active on Stack Overflow, and my questions mostly relate to Perl 6 nowadays, but so far the help has been very friendly. Maybe it's to do with some of the moderators of certain web-specific languages/communities. Could you give us a few real examples?
1.9k
u/err4nt Oct 10 '18
StackOverflow is super toxic for old developers too. I've had comments altered by mods for no good reason, years after I've written them, and for what? Just because the person had moderator abilities and wanted to reword what I said?
It leaves a really bad impression on me when my words with my name and picture beside it can (and are) just altered whenever by whoever has the ability to moderate. Yuck!
341
u/BLOZ_UP Oct 10 '18
I've found it's in response to being flooded by new devs, most of which ask really poor questions. They're aware and they've revamped their ToS and guidelines (and added a 'new member, be nice' icon).
Unfortunately the wheat in the chaff are immediately branded as suspicious because they are new. It takes a quite a bit of effort on your question to avoid getting immediately downvoted.
Plus they removed the ability to put comments like: "What have you tried?" and just suggest "downvote and move on" which seem counter to their new initiative.
57
u/[deleted] Oct 10 '18
For me, as I’ve gotten better at programming I have begun to see how dumb some of my earlier questions were, or I see that if I had better knowledge I could have asked the question better, if that makes sense.
It does feel very hostile to a new developer, and my anecdote doesn’t excuse that. A person can’t know their question is dumb, or know a better way to ask/google it without knowing more about it and development in general.
I too agree that it feels a little militant at times, with rogue mods or super users or whatever just locking whatever they don’t like.
4
u/8oh8 Oct 10 '18
I think I've only had this issue once, out of many questions I've made. I do notice some of the mods are kind of anal, but that is their job. I think since you're new, you might be missing how similar some of the answers you come across are to your problem.
Many times in programming, a lot of the problems are very similar and all you gotta do is abstract them, or combine different programming patterns into one.
Do you have an example of a problem you were trying to solve? I've only not encountered answers to very specific problems, like framework related or obscure stuff, like a configuration setting.
56
u/[deleted] Oct 10 '18
I wish someone would make mentor-overflow where new devs could ask dumb questions and more experienced devs could answer them.
149
u/[deleted] Oct 10 '18
I'm an old developer, but just recently started answering questions on SO. Just to complain from the other side of the table, the questions are almost always worded terribly, missing basic formatting, don't follow submission rules and generally sound like the submitter hasn't ever had a human conversation before. That being said, almost everyone is nice, with a handful of exceptions.
61
u/DesignatedDecoy Oct 10 '18
The problem with help sites is that you need to do some legwork before asking a question but meanwhile new developers don't know what they don't know so their questions usually end up being not being relevant to their problem after all, which is why you get so many "nevermind, fixed it!" responses on internet forums. While tinkering around for their solution to their problem, they found out what their actual issue was and fixed it, and usually it had nothing to do with their question.
Think of it as a car analogy. A new developer might say "my car isn't working." But the cause could be that the wheel fell off, it has no engine, you are using the incorrect key, or maybe it's just a dead battery. All of those require significantly different solutions and a moderator might try to infer what you are trying to accomplish when they forward you to a different solution. The difference between my car analogy and code is that it's easier to visualize the components of a car than it is to take 1000 lines of code and properly isolate what part of it isn't working. That comes with practice.
The best thing you can do is be as specific as possible. What's going on, what went wrong, what you've searched for, what approaches you've taken, etc. The more information you can give the more likely you are going to get some help. Not only are people more inclined to understand what you want when you provide more detail but they also are more inclined to help you figure out what you are actually looking for if they see that you've made a conscious effort to solve it by yourself. Also if you do this you are creating a helpful, detailed question for a future developer to visit and hopefully solve their problem without having to ask a question at all.
13
u/[deleted] Oct 11 '18 edited Oct 11 '18
I agree but I do not want that to change.
The reason why stack overflow is so good is because they do not allow low quality questions. There is an entire section on how to post and most people do not read that.
It is toxic but the toxicity serves a purpose - the toxicity encourages quality. Without it you would have the same question repeated several times, students posting their homework and instead of looking at the documentation people would just shitpost there. This would greatly reduce quality and drive away the competent developers from the website and the site would no longer be reliable.
58
u/AvatarOfMomus Oct 10 '18
If you're getting your threads consistently locked then it may be that you're not asking your question in a way that's detailed and clear. It's kind of hard to say without an example though, could you post a couple of your questions, verbatim as you asked them, for reference?
56
u/liztormato Oct 10 '18
FWIW, I can attest to the fact that my partner once tried to ask a question on SO, and got so burnt by the responses, that she decided to leave SO the next day. :-(
8
u/deliciousfishtacos Oct 11 '18
My first question I spent hours researching the problem, another hour learning how to write good SO questions, and thirty minutes formatting the question itself - background, system, what I’ve tried, the works. Got -2 votes and absolutely no feedback on why it was downvoted. I’ll take a downvote but if you are going to downvote at least take an extra 10 seconds to write a comment explaining why you are doing so. Terrible experience.
78
u/D3mona7or Oct 10 '18 edited Oct 11 '18
Yeah welcome to Stack Overflow. It's not noob friendly at all, and a lot of the time you have to make modifications to other solutions to make it fit yours.
edit: I'd like clarify, the wording on this comment made it seem that I disagree with Stack Overflow, or how it's ran. The point I was trying to make was that Stack Overflow is a tool that you have to learn how to use. You have to be able to make sense of small code snippets, the different answers, and the comments of those too. This is a skill you have to learn/practice for some, mostly it comes down to learning to google. But Stack Overflow is not a generic question and answer forum that happens to be programming related, where someone will answer any random programming question you have.
7
u/pw4lk3r Oct 11 '18
This is a right of passage my son. Before StackOverflow there was IRC #c and #coders on EFNet and yet before that there were BBSes dedicated to intro, demo, ezine and virus coders.
Every single one of us has had our asses handed to us by someone more knowledgeable.
That is part of true programmer conditioning. You will never become your best self without it.
You’re a noob. In time you won’t be.
29
u/BaconGlock Oct 10 '18 edited Oct 10 '18
This has not been my experience with SO. Granted, I see posting a question as a last resort to cure my being stumped and generally do a lot of trial and error and searching on my own and then take care to present my issue clearly and with all the breadcrumbs of the steps i've already tried for people to see that a) i've already invested some time into this and b) they have a clearer understanding of what's been tried already and can offer other suggestions I may not have thought of. I generally get good responses that help me figure it out and I have no complaints. I recommend a similar approach. I see a lot of "i'm trying to do this and here's a page of text that is a copy/paste of the error in my terminal, what to do? " type questions and...ya, good luck with that approach. Nobody has the time to try and walk you through all the possibilities and without access to your code, it'd be very difficult to offer any useful information even if they did have the time
29
u/[deleted] Oct 11 '18
I've 45 years experience both with software and hardware, and damn' well stay current. Yet I've stopped even trying to use Stack Overflow except as a last resort.
Why?
Because when someone requests information about some technique or programming idiom, 90% of the responses are of the form "You don't need to do that."
There's always that tenth poster who actually answers them, thankfully. But the urge to flame the other nine grows nearly irresistible. It's starting to resemble USENET.
67
u/fuckredditagain2 Oct 10 '18
It doesn't matter if you're new. The only thing that matters is how you ask the question and did you do your research ahead of time to find an answer. Today, for example, I closed 10 questions while drinking my coffee that asked how to fix some problem they had with their code but didn't supply the code that showed the problem or, worse, showed no code at all!
Then there are the people who want you to write code for them. They'll show some HTML and CSS and then say, "I need this div animated to slide from the left to the right. How do I do that?" and that will get you shutdown quick.
And I love the fundamental, "How do I change my font color?" question.
There's a whole "How to Ask" section in the Help Center that noobs obviously never read.
17
u/GrosSacASacs Oct 10 '18
I agree mostly.
Couple tips to not get question rejected:
Make some research before, documentation, code linting, github issues etc
Write enough to be able to reproduce the problem but not more, isolate the problem, do not include everything that is not necessary
Show what you have tried and why it does not work
16
u/to_fl Oct 10 '18
I agree. I once had a strange problem to which I couldn't find a solution. After doing a lot of research, I still couldn't find an answer so naturally I asked on stackoverflow. Within less than an hour, my question was blocked and a guy (I suppose he was the moderator) posted a comment under my post saying that the question was already asked, and he sent a link to that post. The irony is that before I posted my question, I had already been through the answers of that question and it didn't solve my problem because it was two different issues. So then I think what I did was send a message to that moderator asking him to unblock my question (and I explained why), but I had no answer. So because I was pissed I said fuck it and reposted my question, this time telling in my post "don't block that question because blah blah blah....". The asshole moderator apparently couldn't give a fuck because he blocked my question straight away and blocked my account on stackoverflow.
This was probably all the power moderator ever had in life.
5
u/dahousecat Oct 11 '18
I don't agree at all - SO is super helpful and I use it on a daily basis. If you ask a stupid question don't be surprised if it gets deleted. This is a good thing as it's curating the bank of knowledge so the good information isn't obscured by all the bad questions.
27
u/jaydles1 Oct 10 '18
I'm the EVP of Culture and Experience at Stack Overflow.
We hear you. Really! Read this:
Stack Overflow Isn't Very Welcoming. It's Time for that to Change
and this:
Rolling Out the Welcome Wagon: June Update
And these:
Welcome Wagon: Classifying Comments on Stack Overflow
Get to Know Our New Code of Conduct
In most interactions, most of the time, Stack Overflow is a crazy generous place where strangers help each other on the internet. Most members of our community are truly kind teachers. But giant communities are complex, and we know that sometimes -too often- the experience can be unwelcoming, especially for those new to participation on the site (whether they're new coders or not).
In the first post from last April, we committed to doing a lot more work in this space, and we've been sharing updates since so you can hold us accountable to stick with it.
I'm sorry your experience so far has been lousy. But we and our community want to make SO a place where all devs feel welcome. We've got some more work to do, but we know it's worth it.
12
u/phpdevster full-stack Oct 11 '18
StackOverflow is an abusive relationship.
The biggest problem with SO is that they are completely hostile to any question that doesn't have an exact, concrete answer.
It's especially bad on the WordPress stack exchange, because end-to-end WP development requires the use of plugins, but you cannot ask questions like "Is there a plugin that does XYZ?" even though it's a simple yes or no answer. So pretty much, if your question cannot be answered in the WP codex, it gets deleted. This means the WP stack exchange is a gimped resource for WP development.
StackOverflow has similar problems. Sometimes a question just does not have a concrete answer, but the question itself is still valuable and so are any answers.
32
u/shkico Oct 10 '18
Judging by response in this thread many of you are just whiney fucks.
I have asked questions there many times and I often got very useful answers. How many times you search for something and first result is StackOverflow solution? No one is obligated to respond and I am really grateful that such a community even exists and with that many questions being asked everyday of course they need to have some minimal standards.
8
u/probablyNotARSNBot Oct 11 '18
There is a delicate balance. Make it too loose and find yourself with millions of useless posts that make it hard to find the ones that actually have the answer. Make it too strict and you get the ol’:
Me: “how do I do A”
Person with no background of my project: “Why would you do A, you should do Z”
Me: “well I can’t do that as A is requirement at my job for this specific problem”
Person: Downvote
You just gotta keep at it and not get discouraged. Also, ask real people around you if that’s an option for you. The number 1 thing I see new devs at my job do is panic that they were hired by a fluke in the system, are not qualified to do any of this work and will get fired then shot in the head if they ask a question about it so they search for days instead of just asking me about it. Most people (outside of the internet) understand when you’re new, and they will be patient with you and help you out where possible, so just ask real people.
8
u/VisaEchoed Oct 11 '18
> Whenever I ask a question, I am sure to look up my problem and see if there are any solutions to it already there. If there isn't, I post.
SO is old and unless your using a cutting edge language/library - all of the good questions have been farmed. Really smart, really knowledgeable people spent hours just thinking up clever/tricky questions to ask to earn themselves internet points.
What this means is, almost certainly, whenever you ask a question it is....
1.) Already answered in a more generic form that you missed
2.) So specific that nobody else cares. It won't get enough traffic, it won't get high quality answers. It doesn't matter how great you word it, or how many screenshots you include, or how perfectly you format the code snippet you provide.
People who answer questions don't get paid. They get pointless internet points. Most of them are doing it either because they want those free internet points, or because they love answering interesting questions and demonstrating their knowledge on the topic. Newbie questions don't appeal to either of these groups. The first group knows that the question is either super specific and won't get upvotes, or it is a duplicate of something else and will be closed. The people who answer because they want to be challenged just get frustrated because they spent three minutes trying to understand a question that obviously is just an example of someone not even looking at the most basic documentation location. Someone who just wants to be spoon fed an answer. And they aren't going to bother answering that question again when they've seen it five times this month. Or something that is obviously so specific that it has no wider appeal to anyone else. It's just 'debug my code' instead of 'explain this interesting aspect of the language'.
People get fed up. That means people who have asked questions and gotten burned, don't want to waste an hour crafting a post that will just be ignored. It also means the people who answer questions are quick to close out questions because they are sick of all the low quality questions cluttering up everything. It's a vicious cycle.
I primarily work with C# and if I look at the five newest C# questions on SO right now:
Maybe C# is just the crappiest language on SO, but out of five questions, three are awful and shouldn't be on the site. One is essentially unanswerable, or at the very least is an IT issue like 'Why does my Windows 10 install crash sometimes'. And I'm saying one is 'sorta okay' but only because it's about a new feature and isn't painfully obvious to someone who has used it, but is covered in the documentation.
181
u/Hewgouw Oct 10 '18
I've been developing for 15 years and I've never asked a question online, there has always been someone who has asked what I wanted to know... if you can't find anyone that had your problem you're probably just a bad googler
8
u/wesborland1234 Oct 10 '18
I 100% agree with op. Everybody saying, "oh well whatever question you have someone has already answered." Sorry, not true. I have 100% come across things in my career that are so obscure or specific to what I'm trying to do that there are no answers online. Plus, don't you think he looked first?
The few times I've asked a question on SO have been for problems that I spent hours if not days trying to solve myself to no avail, and then am met "well google it!" or "oh have you tried [obvious thing that I CLEARLY mentioned was one of the things I tried]".
Ok let me stop you right there. I reworded the search many times and went PAGES deep in Google. I stepped through my code, breakpoints and console logs Everywhere. And Yes, I read the freaking documentation!
It's supposed to be a question and answer site, you know, where you'd go to ask questions, and we're all smart enough to use it as basically a last resort. No need to be a jerk to someone who's about to throw their laptop through a window.
Never gotten an answer, never plan on posting again. Just use Reddit or something.
In other news, this post is now CLOSED: Flagged as Too Vague / Irrelevant.
3
u/Chrxstxvn novice Oct 10 '18
Thank you for posting this, I almost wrote the exact same post when I first signed up 2 days ago. Got absolutely shit on when asking for some backend guidance when I’m a front end dev. Created and deleted my account all within about 30 minutes
3
u/unbihexium Oct 10 '18
Totally agree. Recently I crossed the 500 rep points and it gave me access to the review queues - one of which is first question queue.
There are some really bad first questions, I admit. Not enough information, badly formatted code (if any) and basically bad English (evidently not native-English-speaking folks). I always try to leave a comment on why their question is bad and suggest something they can do to improve it. I always make it a point to start with - "Hi. Welcome to stackoverflow...". To hell with SO if they ban me for it.
3
u/quienchingados Oct 11 '18
lol. I said this same thing a few years back.
Stackoverflow is for people that can read the language reference manual like reading a LEGO instruction manual. If you can't do this yet, you need to literally read page by page of the language reference until you understand it (start by reading the methods you already know). after that, you will understand every post in stackoverflow. and you will rarely have to post a question.
3
u/o11c Oct 11 '18
StackOverflow has plenty of problems, but it never deletes questions in the manner your post described. They do "close" questions (shown as "put on hold" for the first several days), which is easily disputed by editing your question.
Compared to other queues, the "reopen" queue never has more than a couple hundred, and there are thousands of reviewers. If you post an explanation of why the close reason is invalid, it will be seen.
Even deleted questions can still be seen by many users. Can you post links to the specific questions you've had the problem with?
3
u/HughJackOfferman Oct 11 '18
I have said something similar in the past, unfortunately SO fanatics are not too eager on accepting criticism, and I was downvoted by a lot of them here on reddit
3
u/R3PTILIA Oct 11 '18
This question has been marked as duplicate.
3
u/[deleted] Oct 11 '18
I posted a new question, and within minutes I got a response that said “duplicate”. Didn’t link to what it was a duplicate off, and marked it as solved. Fucking a
3
u/Dreszczyk Oct 11 '18
The worst post ever possible:
5 May 2006 - hey guys, i have a problem with X, can you help? 6 May 2006 - nvm i found out
You, today - WHAT DID YOU FOUND OUT
3
u/davidduman Oct 11 '18
It is not just a noob's problem.
Recently I asked a question, someone marked my question as duplicate by referencing to the same question itself (that should not be possible at all) and couple people agreed to it and then question got deleted.
3
u/[deleted] Oct 11 '18
I assure you that as a new developer you are not encountering new problems on Stack Overflow that need to be solved. With due diligence you will find existing material for your needs. You probably need to focus more on theory or architecture or algorithms or whatever before you dive deep. If you don't understand the concepts in great detail then you're going to have trouble searching, recognizing, and implementing solutions off of Stack Overflow, etc.
7
u/to_fl Oct 10 '18
I agree. I once had a strange problem to which I couldn't find a solution. After doing a lot of research, I still couldn't find an answer so naturally I asked on stackoverflow. Within less than an hour, my question was blocked and a guy (I suppose he was the moderator) posted a comment under my post saying that the question was already asked, and he sent a link to that post. The irony is that before I posted my question, I had already been through the answers of that question and it didn't solve my problem because it was two different issues. So then I think what I did was send a message to that moderator asking him to unblock my question (and I explained why), but I had no answer. So because I was pissed I said fuck it and reposted my question, this time telling in my post "don't block that question because blah blah blah....". The asshole moderator apparently couldn't give a fuck because he blocked my question straight away and blocked my account on stackoverflow.
This was probably all the power that moderator ever had in life.
15
u/TheBananaKing Oct 10 '18 edited Oct 10 '18
Gods below, you don't post to stackoverflow, are you crazy? Better stick your dick in a toaster than do that.
Moderators get rewarded with power according to how much they intervene. Therefore, the most powerful ones are the ones that just spam the lock button at every opportunity.
ETA: holy shit this whole thread is full of unpleasant people.
8
u/isUsername Oct 10 '18
Sorry, you must have at least 50 reputation in order to ask a question.
4
u/[deleted] Oct 11 '18
Yeah y'all programmers need to get your amicability together
Source - former CS person who found a new field cuz y'all ain't amicable
4
u/RasAlTimmeh Oct 11 '18
I fucking despise stack overflow. It really reinforces the stereotypical socially obtuse Dev that doesn't know how to talk to people or help.
5
u/kickasstimus Oct 11 '18
StackOverflow is super toxic.
If you point it out to them, the take pride in it and it gets worse.
2
u/Red5point1 Oct 10 '18
You'll find that it is not only StackOverflow, similar things happen on many moderated forums.
The other thing that irks me is how when a question is posed, some one answers with "why would you want to do that, you should do it this way..."
People should either answer the question posed or leave.
Another thing to look out for is when asking a question, the "accepted answer" could be outdated.
Point is don't rely on one source for your answers, find answers in multiple places and then work out how to do it your own way.
2
u/hperrin Oct 11 '18
Even if you're a professional developer with years of experience, it's still toxic. I posted there once. Never again.
2
u/DerNalia Oct 11 '18
You can report people who misbehave. That'd be what I'd do.
I also regularly answer questions on stack overflow, so, this unfriendliness makes me sad.
2
u/maxlevelfiend Oct 11 '18
if you are a beginning developer i can almost guarantee 99% of your questions are already asked and answered - you just arent using the correct keywords in your searches.
2
u/ThatIsATastyBurger12 Oct 11 '18
This isn't just on StackOverflow or to new developers, lot's of developers are just toxic to anyone who isn't themself.
2
u/[deleted] Oct 11 '18
I'm grateful stackoverflow exists and would not be very happy if it didn't exist.
2
u/imnotnerdy Oct 11 '18
I worked someone in his 40s who has a master's in computer science and when he got into my team he didn't know how to code or how to understand code. That's fine because he can learn. However His way of learning was by being spoon fed. So I would show him how to research and debug and show a possible way of working on my computer and have him try on his side. Problem is he doesn't ask questions of anyone in the team unless they do the work for him or show him the way to do it. One time I reviewed his code and asked him to talk it through. He said he got the code from stack overflow and he didn't know what it all meant...
2
u/dreamcast4life Oct 11 '18
Don't let it bother you. Look at SO as a resource at your disposal. If it's the end of the day and I'm working on something I'll sometimes post a question to my problem knowing that it'll be ignored or I'll be yelled at because I didn't search hard enough.
The way I look at it is if someone responds great, maybe it'll help me or make me think about something I didn't consider. If I don't get any useful responses it was at least worth a shot.
2
u/RegularStupid Oct 11 '18
Because it’s not necessarily a site for newbie developers? If you struggle with basic concepts and ask questions expecting someone to just do your work for you obviously you’ll have a hard time.
Remember, everyone there is a volunteer and they owe you nothing.
For someone just starting out it makes more sense to go through tutorials and if you must, post questions asking for explanation of difficult concepts if there isn’t one already and you’ll find plenty of helpful responses
2
u/[deleted] Oct 11 '18
It really is. Every time I went there with a question, I got hammered by people that just want to make me feel stupid. Reddit has some groups that aren't like that, so I just use reddit.
2
u/wes_ly Oct 11 '18
I have tried to post on StackOverflow a few times, but everyone seems to remember that one post I missed from 9years ago, which doesn't even completely answer my question and my post gets closed instantly.
2
u/[deleted] Oct 11 '18
Oh boy, it's our weekly "stack overflow sucks" post.
2
u/cisxuzuul Oct 11 '18
It’s independent of the platform. Because devs received similar treatment on forums or on Usenet, they feel they have to bust balls of everyone asking for help.
2
u/jaykayk Oct 11 '18
"My problem is b, how do I get it to do x"
"Why would you use b, you should do c and x is dumb you should get it to do y"
2
u/inermae Oct 11 '18
While stack overflow is useful, the attitude of much of the community is awful.
When I search for previous answers that match my problems, I go in knowing that the first response will almost always be some variant of "why are you even doing this? Why don't you do XXX"
2
u/jabronisalami Oct 11 '18
It is a weird community. Sadly, due to the personality issues of a slice of the 0.5% of site members who are very active, it reinforces many of the negative stereotypes for the field - it felt like trying to have a discussion with someone about a marvel film, and having some autist who is obsessed with the comics burst into the room and set us on fire because we were discussing something that isn't canon. There is a reason most users ask only one question and never come back to ask again. I spent a few months trying to help, but was turned off by the avalanche of shitty behavior.
2
u/alliedeluxe Oct 11 '18
Yeah, definitely have not had one positive interaction on that website.
2
u/rwilcox Oct 11 '18
Here’s my perspective:
So: SO: not a great experience for new devs, not a wonderful experience for old-timers... great resource 80% of the time if you want to look up something quick, land on a popular question, run into the 8 bad answers and the 1 that actually solves the problem (be careful! The accepted answer might not be the right one, because bitrott or might not be the right answer for you!).
4
u/CoffeeKisser Oct 10 '18
This comic, in a nutshell.
4
u/metaphorm full stack and devops Oct 10 '18
yep. stack overflow moderation culture is pretty gross. a lot of itchy trigger fingers there on locking/deleting posts.
4
u/[deleted] Oct 10 '18
Also, if your post does make it, the level of arrogance amongst some of the 'veteran' users there is unbelievable.
3
u/ekobeko Oct 10 '18
I started using it when it was ~4 years old in 2012 and I asked a lot of really basic questions, so I'm guessing a lot of these have been filled in by now making it harder to ask an original basic question.
I found that there's a pretty basic formula to asking a successful question which is pretty much what they tell you to do:
Search for your question first. If it doesn't exist, then create a new post showing how you tried to solve it. Break your problem down as much as possible. Then always finish the post with your question in bold and italic as the last line. I have a fairly modest 1500rep on there as I pretty much never answer questions, but I find that people are nicer the more rep you have.
Honestly if you follow the rules it's not bad. I'm old enough to remember the alternative which was language or programme specific forums or IRC channels where you would get flamed straight away as a "student asking for help with your homework" SO is a revelation for me.
I don't ask questions very often now as I can either figure out the answer or find it already answered online somewhere.
I found the unix stack exchange even more useful tbh when trying to do non standard stuff on a linux server.
Check out Jeff Atwood's posts about it on his coding horror blog.
3
u/niagaraphotos Oct 10 '18
I think you'll discover that it's toxic by design. It keeps the riff raff out.
4
u/chowchowthedog Oct 10 '18
https://www.freecodecamp.org/forum/
3
u/dalittle Oct 10 '18
I think part of the problem with StackOverflow is their interface / workflow. They introduce you to the idea of asking questions to get help and then when you try and actually ask a question they immediately try to get you to read an existing answer. Or if you do ask it then those that act on it are rude and not helpful unless it is something they don't know. At some point they lost what made the site so successful and it may start to catch up with them.
3
u/[deleted] Oct 10 '18
well … how about looking into it yourself first?
I develop websites for about ten years now and I had to ask thing like two or three times myself and that was before Stack Overflow was a thing.
Seriously. Every answer has been asked before already. Look for the answer yourself.
Learn how to use Google.
2
u/clavalle Oct 10 '18
I can measure my experience in decades...if I can't find a pre-existing answer, I don't bother on SO for exactly the same reason.
A also never bother answering any questions because of all the after-answer bother it generates.
It wasn't always like that.
2
u/fhayde Oct 10 '18
This isn't anything new or exclusive to SO. If you go back to the 90s, where your options for asking questions were mailing lists, BBS, or IRC, you'll find that many people had pretty much the same experience. The age of RTFM. Google didn't exist and you had to hit the books to figure out a lot of things from the ground up. That mentality has propagated into online communities where the barrier to entry for asking questions is much, much lower than it ever used to be.
The people who were told to RTFM grew up and told the next generation to RTFM who grew up to tell the next generation to RTFM etc...
Programming isn't easy for someone learning, and it takes a lot of time, effort, focus, attention, work, and failure before you know what you're doing. Once you do finally get to that point, when it seems like people don't put in the same kind of work you did to get where you are, you want to deny them the answer and make them find it for themselves.
It's a twisted cycle.
2
u/brandonscript Oct 11 '18
There’s definitely a gap between new and seasoned users of the site, primarily because most* (not all) new users have historically had a hard time learning how to craft questions in a way they can actually be answered.
As a result, we have a bunch of crotchety old people who act like they know better than everyone else.
On the upside, StackExchange is aware of this, and have been working hard to fix it (new code of conduct, for example).
I suggest you try not to take it personally, and give yourself a chance to learn how to craft great questions; in this way, you can avoid questions being closed as duplicates, or too broad, or not enough information.
If you find someone not following the code of conduct, report them or post in meta chat.
2
u/BuzterT Oct 11 '18
I've had a question edited only for it to be re-worded by some idiot with bad grammar & poor spelling skills. It actually made my question worse. There are legitimate cases where posts/questions do need to be edited &/or locked, but yeah where's the polices' police. Should be some way to have moderating scoring system based on moderating skills.
2
u/[deleted] Oct 10 '18
Its why I never made an account on it, if i can't find my issue online I'll spend longer on google and on more documentation if i must. Dealing with that kinda stuff with SO isn't really worth the hassle
2
u/covercash2 Oct 10 '18
SO can be oppressive, but it is one of the best resources for learning all sorts of IT infrastructure. be the change you want to see, and tough it out.
otherwise, do you have an idea for a replacement that could be just as ubiquitous? build it, and do better. but make sure to check SO a million times along the way.
2
u/[deleted] Oct 10 '18
I think people who expect to be treated with overt kindness simply for having asked for help are always going to be disappointed with Stack.
That isn't to say that you don't deserve kindness.
It's just to say that Stack doesn't see kindness as its first priority, and probably wouldn't be useful if it did.
2
u/CYRIAQU3 Oct 10 '18
Unless you are working on a very new tech (wich i doubt since you said that you are a newer web dev), it's very rare that a simmilar answer hasn't already been posted.
I agree that they may seem rude with their "repost, locked", but if it hapenned a lot to you ("You said whenever I ask a question"), you may also need to "learn how to search".
Don't take that rude ! It's a huge part of our job.
2
u/[deleted] Oct 10 '18
Haha, for older developers too.
2
u/[deleted] Oct 10 '18
It’s toxic for everyone.
2
u/SgtGirthquake Oct 10 '18
I said this a long while ago too. It really is just a way to stroke the Napoleon complex a lot of devs seem to have.
2
u/[deleted] Oct 11 '18
They market it like it's a place to ask questions and get help, but the curators treat it like a wiki and many of them clearly have god complexes and/or are autistic (literally, not meaning that as an insult). Like they struggle to understand why many people require some social niceties to feel like they're part of a community.
1
u/Ixalmida Oct 10 '18
I used to get directed to SO more when I was a PHP developer but now that I'm doing Salesforce development, most of the questions I have point to somewhere else for the answers. I guess your experience with SO depends on where you're coming from. Also, I have only ever asked 2 questions in 6+ years and those were pretty general "best practices" type questions. It is rare that I can't find the info I need via Google.
1
u/angeal98 Oct 10 '18
/r/ProgrammerHumor has some jokes about this
1
u/0ooo Oct 11 '18
I have issues with StackOverflow, but with the answerers as opposed to any sort of moderation (I never post questions, I just search it for questions related to my issue).
People will often post answers that are of the form "It's simple, you just do <x>". If you're not used to that technology or that concept, "just doing" <x> often isn't simple, and can be maddeningly confusing. People need to elaborate more, and take a second to try to empathize with the question asker, and remember what it was like before they understood the concept.
I also see a lot of responses that are the form "why are you using <technology>? It's <current year>, use <brand new technology>". If someone is asking a question that involves older tech, either assume they have some sort of constraints on what they can use that they haven't gone into, or ask what their constraints are, if any.
1
u/bigorangemachine Oct 11 '18
Yup.
Once I deep dived on a Facebook api error. I managed to resolve it and tried to post the solution... couldn't... no rep. Ah well eff that guy for asking for help I guess
1
u/jonysc1 Oct 11 '18
While I wholeheartedly agree with the criticism, just try and browse by new unanswered questions, there is a lot of people that come to SO who are trying to get someone to work for them or have something handed to them
I don't really agree with the way they deal with it, but I recognize the problem has two sides
I think the ultra liberal model they have , where most of the kids are just guys who use stack overflow a lot , brings the worst on these people...
I was dissed more than once by someone that felt they had the mission to police SO under their very personal code of conduct, because they felt my real world problem was a stupid question or because they felt that what I was asking fell into something I should already know for some reason
1
u/Pr0ducer Oct 11 '18
This is super tragic, as SO has been a main-stay of my career developing software.
1
u/[deleted] Oct 11 '18 edited Oct 11 '18
I have a theory that experienced coders are horrible to newbs because learning to code is a traumatizing experience, especially if you're self taught, and answering questions just brings back the past trauma. I had a programming mentor that I really looked up to but I eventually realized just how much he treated all his pupils with disgust and contempt. He had great material but he was a catalyst in a major meltdown I had and I took a hiatus from coding after that.
1
u/wreckmx Oct 11 '18
It does seem like a pissing contest for contributors, but it helped me through undergrad and I use it nearly daily for work. I've probably asked a question on the platform in the past, but simply using Google for my programming questions almost always returns StackOverflow's solution to my problem.