Posting Guidelines

This will serve primarily as a guide on what not to post in either topic openers or responses, as the guidelines for Asking Good Questions and Giving Good Answers are covered elsewhere.

Discourse offers us the ability to keep a permanent log of questions and answers for future students and classes to reference. This helps you by organizing problems past students have had and giving another resource for if you’re feeling stuck. However, due to its nature as a static site, we need to make sure it can serve only to improve students’ ability to learn. Following are a few guidelines designed to ensure this can be achieved.

Avoid posting solutions or large segments of code

With posts being public, we want to avoid situations where someone who’s stuck can either simply copy a solution or take someone else’s code fragment and fix the issues listed in responses. Either of these scenarios leads to a student who’s able to complete an assignment without learning how to solve the problem themselves, which is really the goal of all our assignments at LaunchCode.

The line between “enough code to get help” and “too much code” can be a tricky one to find, but as a general rule, Discovery and Unit 1 Questions should avoid having more than one line of pure code posted. You can avoid the need to post more by simply describing what you’ve tried and what’s going wrong or asking a slightly more vague version of your question. In the case where you need someone to look at your whole code for some reason, send it in a message to one of the instructors so that we can help without giving future students the answer.

Don't post without reading similar topics and previous responses

This resource only continues to be valuable while it’s helpfully organized, and having duplicate topics or responses will make it harder for future users to find the questions or answers they’re looking for.

If you post a question that’s already been answered in a previous topic, that’s a pretty clear sign that you haven’t exhausted your problem-solving arsenal before asking for help. One of the key skills for developers is the ability to use a variety of tools to fix an issue and become self-sufficient problem solvers, so if you just ask for help at the first sign of trouble, you won’t improve.

Similarly, just because you’ve read the first post in a thread and think you can help doesn’t mean you should immediately post your idea. Make sure you read any other responses in case your idea was already presented or further information by the original poster changed what response they might be looking for.

Keep responses on-topic

Even if you’re having an issue with the same problem or function, if your problem is unrelated to the one presented by the original post and you’re not the original poster, create a new topic! This way, if someone later down the road has an issue with that problem, they’ll have multiple threads dedicated to specific issues people have encountered without having to sort through one cluttered topic.

Stick to LaunchCode-focused content

This website should only be used for questions regarding LaunchCode and its courses. We simply don’t have the resources to respond to other questions and keep the site organized.

3 Likes