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 cannot even begin to describe the amount of gratitude I feel toward others in this field who spend their free time answering questions and in writing useful blog posts and tutorials; not to mention the scores of free ebooks available from their authors along with the numerous open source projects that are freely available to everyone everywhere to study or use.
I can only guess that the author was having a bad day when he/she wrote this post. But despite some nasty mannerisms here and there; it seems apparent that the online tech community is comprised of a lot of people willing to share helpful information with others; without reservation or any expectation of compensation (other than rep points, perhaps).
Some people revel in the 'secret clubhouse' mentality of being the only people to understand how some program works or something.
In the end, it's a balance of efforts. While it would take the expert 15 minutes to craft a good explanatory reply, it would take the asker a few minutes to type it into Google and read the first few responses that pop up. For any good question, the burden of time should be on the asker.
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.
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:
> which has the code almost unchanged since then at gamebrave.com
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.
Also, gamebrave was changed many times, and I improved it as much as I could, the layout changed many times as I learned more effective ways to write code. I just stopped working on it at one point because I wasn't getting anything out of improving the website, I wanted to move on, and try a new project. It wasn't going to ever be a really business, it was just a way for me to learn how to write web code.
Also, this is my early story, and was fed mainly by curiosity, and not a formal education plan. Based on a lot of advice I have received, I will be reading books on programming topics that interest me.
I will suggest the following advice; take it with whatever worth you might... work on improving Gamebrave. A LOT of developers I hire and work with love to constantly move to something new, something that will challenge them in a new way, allow them to use their new abilities, new technologies, etc. Resist this desire, and you will find success. Those developers come and go, and I certainly spent my own time doing this. But starting new is easy. It's not difficult to get through the hello world phase and get something started. What's truly difficult is pushing something past that plateau feeling into something even better or more effective.
And it's that skill (of resisting newness) that will get you hired full time, and indeed what I look for. If someone says they get passionate about debugging or refactoring, it's worth a thousand people who like starting from scratch. So go and open up your old code, improve it, maybe figure out how to turn that sucker into some passive income, figure out a way to get people there. Trust me, learning this Zen of development will be much better for your future career (assuming you want to do this full time). There's a reason that old OS/2 and mainframe people get jobs worth twice what their peers get for slinging javascript.
This goes both ways: If you're and expert annoyed by this moron who can't even state his question properly, point him to this tutorial and leave it at that.
When I read this though, I think I started getting what was happening:
>despite me having implemented best coding practice, and having my plugin include over 30 major original classes created by me.
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.
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)
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.
