My issue isn't with answering questions. Everyone here is at a different level and have different areas of interest. The problem lies with the lack of basic troubleshooting concepts. You don't have to know all the ins and outs of a computer to at least narrow down the issue. From there, you simply have to take that information over to Google and most of the time the answer is solved. I realize sometimes you have to read a LOT of sites and collect tid bits of information from each, then put them together yourself, but that's just what you have to do. In doing so, you will pick up other knowledge along the way and help your understanding of the problem. Research, research, research.
For someone to come in here and ask a question, without spending the time to troubleshoot and research, is abusing what this site is all about. We are not here to do your job for you, and I certainly don't expect anyone to do my job for me. I have asked a question or two on here in the past, sure it's a great place to get help after you have exhausted your own resources.
Sometimes I have to research a problem for hours, even days on a few occasions. That is simply part of being a technician. I have learned far more while researching then I ever will by asking questions. One thing that makes a tech a good tech, is the ability to find an answer to something he/she doesn't know. I don't know everything, no one does. I don't pretend to have the answers if I don't either, but I do know how to research. Sometimes research involves reading, watching, listening, and even EXPERIMENTING. Sure, it's a pain in the arse to load up a VM and try to replicate the issue and monitor what's going on, but you learn so much more in the process.
It should be the goal of every technician to continually educate yourself. It's an essential skill to apply various bits of information in relation to each other. New techs need to stop trying to learn "fixes" and start learning concepts of why, how, and where. Those basic fundamental concepts, along with knowing where to research, are the building blocks of what makes a tech.
Someone asking a question that could have been solved by basic research, or basic troubleshooting based on concepts, appears to me, as a technician who doesn't take real pride in his work.
I have no interest in helping an individual who is an EU just being to cheap to pay for a fix, or a tech who is looking for an easy ride with no pride in his/her work. However, if someone truly wants to learn, I will give them all the time in the world to teach them how to develop and recognize the basic concepts and fundamentals of troubleshooting.
I have too, became frustrated with things here and have stopped posting as much. An end user coming here to ask a question is simply against the rules. A member answering those end user questions is, in my opinion, violating the rules as well. I ignore the questions of end users, but I am highly disappointed in the members here who ignore the rules and answer their questions. We are supposed to be a community, and to me, that means not intentionally breaking the rules that have helped shape this community.
Okay, my rant is over
