Sent on Jun 15, 2016

How to ask good coding questions that get you a great reply

How have you been? You haven’t heard from me in two weeks because I was on a much needed holiday. I spent the last few days in Inner Mongolia, of which, three days were in a desert. It was fun ^^

Being in nature taught me things about myself that I never noticed before. I found out how burned out I am even though I’m doing work I love.

One of the things that caused me to burn out was answering coding questions.

Most questions I received weren’t worded in a way that I can answer immediately. I had to ask clarifying questions before I can provide satisfactory answers. This process drains a lot of my time and energy.

But I still want to answer questions because I want to help. I know getting your questions answered is important to you.

However, to keep my sanity, I’m imposing a few guidelines to help you ask better questions. Your questions should:

  1. Be specific (Ask one thing only)
  2. Be clear and concise
  3. Show that you’ve done work before asking the question

To help you out, here’s an article that explains why questions should be crafted with these guidelines. I also analyzed two questions I received and showed you how to improve them.

Don’t worry if English isn’t your native language. Simple words often work better than fanciful ones to get a question across.

Finally, I want to let you know that I’m switching the way I answer questions starting from today. If you want to ask me a question (Design, Frontend, Backend, Life etc), please head over to this Github repo and file an issue. I’ll reply. You can still send it via email, just don’t be alarmed if I get you to file an issue :)

I want to handle questions via Github because:

  1. This way, your questions don’t get lost in my inbox.
  2. I (might) have answered your question before. You can search for them easily on the Github issues.
  3. It’s much easier for me to search through Github issues and point people towards the correct answers than write a new reply for every question that comes my way.
  4. (This last one is a fantasy). If you asked questions, I’ll have more materials to talk about in blog posts (where I expand the replies). At the moment, everything gets lost in emails and I have to think of new topics every week. So ask away!

TL;DR

In short, I’m burned out from answering questions, but I still want to answer them. Read this blog post about how you to craft your questions if you want me to answer yours. Finally, send questions via Github Issues to this Github Repo instead of sending it to me via email.

Hope you have a great week ahead!

Stay awesome,
Zell