This is from my profile on the Stack Exchange network. It is necessarily brief
due to the hard character limit over there, but most of the tips here apply to
any other technical Q&A platform, including freelance sites. There are two
sections: the first is geared towards askers/requesters, and the second towards
answerers/workers.
Ask Questions That Get Answers
- If your problem is vague, large, immediate, or long-term, you need to find paid help. Codementor, Fiverr, Upwork, etc.
- Read How do I ask a good question?
- The search function is free. Use it.
- The Ask Wizard exists for a reason, so follow it!
- If there's a similar question, read the answers and comments and expect that you'll have to adapt them a bit to your use case.
- Documentation is also (usually) free. Read it!
- The problem you're having with [x library] is that you're using [x library] when [language/platform standard] works just fine.
- If your code was fine, and then you updated your dependencies/packages, and now it's not fine, check the bug reports/issues. If you don't know where to find them, searching will work. Example:
axios issue reports, firefox bug reports, pytorch bugs.
- There are almost 200 communities on the StackExchange network, including sites for Linux, DBAs, Wordpress, Gamedev, Code Review, and many others. Check here if your question isn't about a specific programming problem; there might be a better place to ask.
- To format code in your post, put three backticks on the line above the code, and three on the line below it. No more, no less. Exactly three. Not one and then three on the next line. Not three on separate lines.
- 50% of your problems will be solved by using a linter and integration with your editor. Go to duckduckgo.com and type in the language you're using, the editor you're using, and the word "linter." Example:
python vim linter. Read the first 5 links or so, set up whatever seems easiest.
Help Improve StackExchange's Bad Reputation
- Are you in a bad mood right now? Close the tab.
- Are you sure the question you're marking as a duplicate, low quality, etc., actually meets that criteria? Is there a Meta post about it? Have you read and understood the Meta post?
- Is the asker new to the site? Maybe they didn't read the docs on asking questions. Point them in the right direction and see if they update their question, before voting to close.
- Be professional! This isn't your friend group, this is a professional network of people looking for help. If you type out a comment that you wouldn't say in a meeting at work, don't say it here!
- Remember that you, once, were also a beginner. No one was born knowing the differences between regex engines or whatever, or knowing how to manipulate search engines into providing useful results instead of just ads.
- Step back if you're out of your depth. StackExchange reputation is just fake internet points, you don't need to answer if your answer is low-quality, and you don't need to spend more time than you're comfortable with on an exchange.