One thing about asking for help: take the time to ask the "whole" question. This is especially important with programming. If you just dump a snippet of code in code blocks in slack, it's really hard to understand what you're trying to do.

Here's a quick guide:

Grab yourself a @github account and use gist.github.com to post your *entire* code.

Select the language and format it to the best of your ability. You can then paste this link into Slack with your question.

Record a quick video showing you running the code.

Take the time to write out a "what did you try?" question. Don't just post "I got a 400 error what now?". Show us the code, show us the error.

I think sometimes when we ask for help we want to not be a burden, so we attempt to keep it super short and sweet, but this often has the opposite effect on experts. If you don't give most of the context, it forces people to go hunting for more context.

Most devs enjoy debugging. But most devs hate debugging communications. Don't be afraid to ask for help, but ask the whole question.

- What did you expect to happen?
- What is happening?
- What did you try?
- What version of the software(s) are you using?