I wonder what these requests for help look like. I idle in a handful of IRC channels devoted to various frameworks and languages. There are a handful of people who get berated, but it's nearly always people who come in and demand answers and are unwilling to do any leg work to describe their problem.<p>If it's gotten to the point where every single time you ask for help you're being bullied or berated, the common denominator is you. How are you going about asking? What venues are you asking in? What do you do to properly describe your problem? When people ask you to try things do you do it or argue that whatever they're suggesting can't be related?
I think a lot of people can relate to your experience (I spent a lot of time in front of a QBasic window and Flash).<p>When I read this though, I think I started getting what was happening:<p>>despite me having implemented best coding practice, and having my plugin include over 30 major original classes created by me.<p>It sounds like you might not really get what we mean by design patterns. I don't think number of classes is ever an interesting metric to people, but the fact that you mention it makes it sound like you might not 'get' what people are complaining about.<p>But I think another problem you might have is the people you're talking to the wrong crowd. Stack Overflow, for example, has a great community, and the people there show the utmost patience. It's truly one of the best communities on the internet(despite endless complaining here on HN about the proactive moderation)<p>The flip side is that you might actually be fighting back a bit too hard, and you might actually be the "annoying guy who doesn't want to understand". Always difficult with one-sided stories.
> I learned by copy and pasting novels of code, and did not read a single book, or take a single class<p>This is the problem. His story sounds familiar to mine at first, but a generation apart. I was taught to self-learn, read books, and first figure out the right question to ask. Then, and only then, ask the questions. Copy and pasting doesn't have to be terrible. Copy, paste, and then figure out what the heck it's doing, and then modify it to your own purposes. Iterate. Read books. Google stuff. I only mention the generational thing because the lack of opening a book seems to be just that. My generation did that, his does not. I can easily see how he probably gets shut down a lot without understanding why.<p>So, advice from someone who started by copying and pasting... Read the book. RTFM. Use google, and only ask questions when you're confident what the question is. If someone makes fun of your classes, don't whine, just go read about OO design and patterns and make them better. Above all, this is not acceptable:<p>> which has the code almost unchanged since then at gamebrave.com<p>You should always be improving. This is the statement that clued me in to wannabe syndrome. It's ok to want to be something. It's not ok to expect that something to get handed to you. Read the books, take the classes (these days with MOOCs there is no excuse). Put in the work, and soon you'll be the one ignoring the noobs.
If you love programming there's no reason to let unhelpful online responses get you down. Keep looking for good people that can help you online, they do exist. And keep trying to improve the way you learn and the way you get information from others. Eric Raymond's "How To Ask Questions The Smart Way" might be helpful [1].<p>[1] <a href="http://www.catb.org/~esr/faqs/smart-questions.html" rel="nofollow">http://www.catb.org/~esr/faqs/smart-questions.html</a>