Subscribe to CurtisRutland.Write("...");        RSS Feed
***** 3 Votes

How we know you're not worth our time.

Icon 5 Comments
Most of the people who answer questions on this site are professionals. We do this for a living. Most of us have put up with enough shit just from work that we won't hesitate for a second to ignore your question if you give us an excuse. That's not to say we're jerks, looking for reasons to ignore you; it means that we're not going to work really hard to help you when you make it hard for us.

There are many obvious indicators, and I'll go through a few of them now. Hopefully you don't make any of these mistakes.

  • No source code. I'm not sure how many hundreds of times I've had to type this in one way or another, but we aren't going to write your project for you. Homework or actual work; it doesn't matter. None of us are going to do your job for you. Most of us love helping. The greatest reward for a forum expert is to see that someone comprehended the answer you posted and applied it to solve their problems.

    Handing you the code is not teaching. It's cheating. And it's also working for free. Screw that.

  • Spelling. Look, I understand English may not be your first language. That's fine, I don't expect you to spell everything perfectly. But for those of you that do speak English, I expect you to type it properly as well. Every modern browser has a built-in spell checker, and IE has addons that provide that capability. Get one. It honestly can make the difference. It lets us know that you respect us enough to treat us like the professionals we are.

    On that note, if you type "plz," especially with numerous extra "z"s, I close the browser window and ignore your question. It's a personal peeve, but one I've seen reflected in many of the other experts, here and other places. Just don't do it.

    And it's "code," not "codes" or "codez."

  • Overstating urgency. I'm a volunteer here. You're not paying me. Because of that, my time is mine, not yours. Just because you "urgently need codes plzzzz send quick" doesn't mean that I'm going to go out of my way to help. Your poor planing does not create an emergency on my part. I'll do my best to help, but don't start getting frustrated or impatient or I'll walk away and never look back.

    If your problem is urgent, clearly state so. A real timeline helps: "This is actually pretty urgent. The project is due in 48 hours." If I can help you in that timeframe, I'll do my best to. But that's different than just freaking out and begging. Which leads me to...

  • Begging. The entire point of this (and any) programming forum is for experts to help you. You don't need to beg us. If we can help, we will. Saying "plz plzzzz help im clueless help plz" isn't incentive for us to help. It's actually the opposite.

    The best thing you can do to get help is clearly state your problems, what you've tried to resolve them, the code where it's happening, and any error/exception messages. Which is a segue into:

  • Lack of effort/clarity. This is the big one. This is probably the most common way that we decide you're not worth our time. If it's not worth your time to clearly post what your problem is, then it's not worth our time to help you fix it.

I'll expand on effort and clarity, because it deserves its own section. Here are some dos and don'ts.

  • ...only post one sentence. If your question is simple enough to be fit into a single sentence, it's probably simple enough to use google to answer.
  • no code. We need to see your code to solve your problem. Conversely,
  • ALL your code. We don't need to see 4000 lines of auto-generated garbage to solve a problem in one method.
  • ...just say "It doesn't work." That's the most useless statement ever. What doesn't work? Does anything happen? Nothing? Is your code being executed? Does it throw an exception? These are the important things we need to know.

  • ...clearly post your entire problem.
  • relevant source code.
  • any exceptions, and indicate which line they're thrown at.
  • the steps you've tried to resolve your own problem.
  • ...respect the professionals trying to help you. This one's important!

Following these simple rules makes it much more likely that someone is going to help you. Number one rule: respect us, and we'll respect you.

5 Comments On This Entry

Page 1 of 1


09 August 2010 - 01:08 PM
Well said.


14 August 2010 - 01:33 PM
Indeed, well said.


14 August 2010 - 07:35 PM
They may have already entered their question in to a search engine, so tell them to google it is insulting.


14 August 2010 - 11:21 PM

AdamSpeight2008, on 15 August 2010 - 01:35 AM, said:

They may have already entered their question in to a search engine, so tell them to google it is insulting.

Actually this is very true. I can't count the number of times I have entered an error message into google only to find the first couple of pages are people asking the same question on forums and getting the same answer: "google it". If googling it is how I got there in the first place, then the person who posted that is a dick.

But most of us are good enough at searching for things that we can pretty much instantly distinguish between something you could find in the top few results on google and something that's more obscure, though. If I ever tell someone to go search for an answer I make sure I've taken 30 seconds out to try the search first, just in case.


19 August 2010 - 01:54 PM

AdamSpeight2008, on 14 August 2010 - 10:35 PM, said:

They may have already entered their question in to a search engine, so tell them to google it is insulting.

This is a double-edged sword. A lot of the time, the answers can be found in the documentation, but newbies don't always know what to search for. If someone asks "how can I compare Strings," I'll reply "take a look at the String class (link to Java API). Note that you can search for a class' definition by searching Java class-name 6, and the result is usually on the first page." On the other hand, "I'm looking for a number base converter" should get the Google it response in my opinion. Either that, or ask them for an MIT Ph.D thesis paper in return. ;)

@: Good entry. :^:
Page 1 of 1

Trackbacks for this entry [ Trackback URL ]

There are no Trackbacks for this entry

Recent Entries

Recent Comments

1 user(s) viewing

1 Guests
0 member(s)
0 anonymous member(s)