Asking for help

If you get stuck, our Slack community is the right place to ask for help. Our members are generally happy to assist, but following these guidelines will make it much easier for others to help you effectively.

Avoid meta questions

Meta questions are questions about asking questions (e.g., “Can I ask a question about X?”). They add an unnecessary step and delay getting the help you need.

Don’t ask to ask, just ask. If you have a question, post it directly in the appropriate channel. The people who can help will see it and respond.

Examples of meta questions to avoid:

  • “Can I ask a question about data science here?” - just ask your data science question directly. That’s what this Slack exists for.
  • “Is there anyone who knows marketing? I have a question about it.” - just ask your marketing question directly. If someone knows the answer, they’ll respond.
  • “Has anyone done Machine Learning Zoomcamp? I have a question about it.” - just ask your question about Machine Learning Zoomcamp. If someone has done it, they’ll answer.

Code problems and errors

When something doesn’t work and you need help figuring it out, we’ll be happy to help. To get the best assistance quickly, please follow these recommendations:

  • Use threads for errors. First describe the problem briefly in the main channel, then put the actual error message and code in a thread.
  • Copy-paste text, don’t screenshot. Don’t take screenshots of your code or terminal output. Instead, copy-paste the error message and code as text. Use code blocks (three backticks) to format your code. Text is searchable, easier to read, and allows helpers to copy your code if needed.
  • Never photograph your screen. Don’t take pictures of your code with a phone. It’s even harder to read than screenshots. Always copy-paste text. In rare cases when you need to show what happens on your screen visually (like a UI issue), a screenshot is acceptable, but code and errors should always be text.

Homework help

We’re generally happy to help with your homework, provided that you show genuine effort from your side and are transparent about the source of your question.

  • Show your work. Don’t just copy-paste an exercise and expect others to solve it for you. Share what you’ve tried, what you understand, and where you’re stuck.
  • Be transparent. Clearly state that it’s a homework assignment. This helps people provide appropriate guidance (teaching concepts rather than just giving answers).
  • Ask for guidance, not answers. Frame your question to ask for help understanding concepts or debugging your approach, rather than asking for the complete solution.

For more detailed guidance on asking homework questions effectively, consult this guide from StackOverflow.

The same principles apply to interview take-home assignments. We’re happy to help, but be transparent and focus on understanding concepts rather than getting complete solutions.