Game Development Community

dev|Pro Game Development Curriculum

Plan for Ben Garney

by Kyle Carter · 12/29/2004 (5:31 pm) · 11 comments

A quick foreword: If you want to have a say on what features go into the upcoming revision of TorqueScript, please see my last plan and post! Now, onto the rest of the plan...

How To Ask Questions: The Smart Way <-- Please Read This.

This document outlines a very good set of guidelines for asking technical questions. Although GG's products aren't in quite the same category as, say, Apache or GCC, we have a lot more in common with them than with, say, Word or Excel. We wouldn't be where we are without our open codebase and an active, vibrant community.

Asking and answering smart questions is an absolutely critical part of the culture here, what makes this a worthwhile place to be if you're an indie game developer. Naturally, there are plenty of things that get discussed that aren't Torque-specific, but smart questions are a universal goal to shoot for.

A bad question leeches knowledge or wastes people's time. A good question gets you an answer you need. A great question gives the community a chance to shine, for people to come together, for everyone to benefit. Great questions make threads that people will go back and read for years to come.

And asking great questions isn't necessarily all that hard. See the link for details. :) This is a great read for anyone, newbie or veteran, experienced or not.

(And for you foreign guys - it's available in a LOT of different languages: Chinese Czech Danish Estonian French German Hebrew Hungarian Italian Japanese Polish Russian Spanish Swedish Turkish.)

A lot of us GG "old timers" have noticed that as the community here grows, it's changing. This is a good thing. The newbies of today are the veterans of tomorrow, so to speak. :) But for it to grow in a healthy way, we all need to establish values, set the tone. People that come here often comment on how they love the prompt responses to their questions, the knowledgeable people, the willingness to help and to problem-solve.

I am excited to have that be the perception of our community! A community reflects its members, and we have some really awesome people in our community. They donate their time and experience, often thanklessly. And by so doing, they attract more peoplel like themselves - and impress everyone else. This is a very positive thing.

But as the community grows, as more people come through, the game changes. A community of ten thousand is different than a community of a hundred. A community of a hundred thousand is different yet again. Growth brings change. Things that were once implicit have to become conscious decisions. As the garage grows, we have to learn how to welcome people in, how to help them be the best they can be, and show them how they can help others, including ourselves.

Personally, just speaking for myself, I want GG to be the kind of place:
  • Where we have fun. (Why make it a drag to be here?)
  • Where we are dedicated to making fun and interesting games. (It's GarageGames, not GarageTech. Although I think we all really like tech a lot. ;)
  • Where there is a high level of game development expertise. (Best of the best! In code, art, and design!)
  • Where there are places for all levels of ability (like Jeff says - from Cradle to Grave). (Newbies won't drown in our community.)
  • Where we have a strong culture of asking smart questions, sharing resources, and helping one another finish projects.
  • Where we welcome and enable coders and artists of all types. (Programming is only half the equation!)

Of course, there's a gap between saying something and making it so, especially in a large community... But without goals, we'll never get anywhere. :) These are the goals I'm shooting for.

#1
12/29/2004 (5:46 pm)
Though I do find the GarageGames homepage quite informative and enticing, I must admit I can't seem to locate the information you are referencing on it.

Perhaps you meant: How To Ask Questions: The Smart Way?
#2
12/29/2004 (6:05 pm)
I did, updated and fixed. Thanks, Mark!
#3
12/29/2004 (6:37 pm)
"Writing like a l33t script kiddie hax0r is the absolute kiss of death and guarantees you will receive nothing but stony silence (or, at best, a heaping helping of scorn and sarcasm) in return."

This includes things like "any1" or "u" or "ne1" . That's just lazy.
Things like that were acceptable back when us amatuer radio operators used CW (morse code), but seriously people, learn to type.
#4
12/29/2004 (7:36 pm)
My project is between milestones at the moment, which means that I am both asking, and answering questions as I am able on the forums. I can't stress enough how important it is to follow Ben's advice!

Hell, most of the time, my questions are either too verbose to get answers, or I answer them myself after a couple of hours, but even so, I can promise that before a question comes to the forums from me, I've spent the 20-30 hours researching not only the forums, the resources, and the code itself, but tried a lot of similar (if not particularly appropriate in some cases!) techniques or examples from the source itself.

Personally, I believe in the "answer to question" ratio--which means that if you haven't provided more answers in recent posts then you've asked questions, your chances of gettting an answer that meets your needs is very low.

Then again, if you reserve your questions for those times when you are REALLY stuck, sometimes the senior experts come through!

Speaking of which...Ben, any idea why the terrain editor works so well at small granularity but my networked deformation objects don't?
/duck

I also firmly believe in the "research to knee-jerk response" ratio (something I just made up myself!)--which is explained very well in the web article Ben linked to.

Sometimes when you ask a question, you get a very accurate and on-point response telling you exactly what to do to resolve your issue, but that will only happen when someone has just recently finished "fixing" an exact duplicate, or reasonably close facsimile of the question you asked.

More often, you will get pointers, suggestions, or possible areas of code to look at as possibilities. If you can read responses of that nature and immediately reply "Yes, I looked at that, but it doesn't actually apply, due to well thought out analysis here, do you have any other areas to look at?" then you know you are on the right track in your research and question process.

No one knows TGE at an infinite level---everyone has areas of the code that they simply "don't get". The most important thing anyone can learn about asking questions on the forums is to reserve the posts for when you are really lost, and just maybe the experienced community members will take the time to research your question and give you a solution that helps!
#5
12/30/2004 (3:58 am)
Quote:Writing like a l33t script kiddie hax0r is the absolute kiss of death
Aaahh, and I was just starting to get the hang of 1337-talk ... another knowledge down the drain...

Seriously, I have yet to find a community with such a well mannered forum as this one.
But, I do think that the growth has become noticable in some areas, requiring a higher level of moderation wich in turn require more of GG staff time.
Not an ideal solution tough since I believe that Jeff & Co. is best fit bringing us the coolest indie-game-stuff possible.

A responsability for all forum users is to take a moment to think about how they come across when they post a response to a perhaps strange or ill-formed question...

just my 2c.
#6
12/30/2004 (4:56 am)
We should also keep in mind that some people ask seemingly dumb (opposite of smart?) questions because they are new to the topics and are not sure of what terminology to use. And if you don't know the terminology then you can't accurately search the forums.

I had a problem with light maps but I didn't know what the problem was called and so I had no idea for what to search. Someone was nice enough to point out that it was a light map problem I searched for the term and found answers. The point is is that I didn't ask the question in a smart way but only because I didn't know how to, not because it wasn't a smart question.

Just something to keep in mind when we see these not so smart questions.

Steven, your rule about replying more than asking is a nice rule in theory but right now I have to ask more than I answer because I just don't know enough to answer anything accurately. Having people answer questions for the sake of answering them is a waist of time for all and clutters the forums with noise. But you make a good point in that as you learn be willing to transfer knowledge back to the community. Nobody likes a knowledge vacuum or IP (Intellectual Property) cloaking.
#7
12/30/2004 (1:27 pm)
Ben, off topic but when is your forest pack going to be available :)?
#8
01/01/2005 (2:15 pm)
@Joe: Stephen has a good point, but I think it's possible to ask questions in a way that contribute to the community - ie, answering isn't the only way to contribute. To my mind, any time a thread has a good, clear question (preferably with screenshots or other exhibits ;), and it gets answered, it's a good, valuable thread... because it can be used over and over again, hopefully, to answer the same question. The goal is to never have a question asked more than once. ;)

@Ashely: When it's done! :)
#9
01/01/2005 (3:32 pm)
"When it
#10
01/04/2005 (2:39 am)
Opps, posted in the wrong window. :) That doc is great, thank for the link.

Ben
#11
01/05/2005 (6:45 am)
I disagree with David Bunt. Leet speak is annoying. Shortening words is just shortening words. Use of "u" and "l8r" just save keystrokes. I work all day as a consultant and all night as a game dev and then for fun I play computer games. My hands take a beating and anything I can do to avoid the carpool and the tunnel is a GOOD thing as far as I can see.

neway cu l8r