|
| 1 | +--- |
| 2 | +title: "Asking Questions" |
| 3 | +layout: default |
| 4 | +nav_order: 15 |
| 5 | +parent: Zoomcamp Logistics |
| 6 | +description: "How to ask for help in DataTalks.Club zoomcamp Slack channels." |
| 7 | +--- |
| 8 | + |
| 9 | +# Asking Questions |
| 10 | + |
| 11 | +If you have a course question, ask it in the course-specific Slack channel. Use the course FAQ first, then post in Slack if you still need help. Do not ask technical questions in Telegram; Telegram is for announcements. |
| 12 | + |
| 13 | +Course channels and FAQs: |
| 14 | + |
| 15 | +- Data Engineering Zoomcamp: [`#course-data-engineering`](https://app.slack.com/client/T01ATQK62F8/C01FABYF2RG), [FAQ](https://datatalks.club/faq/data-engineering-zoomcamp.html). |
| 16 | +- Machine Learning Zoomcamp: [`#course-ml-zoomcamp`](https://app.slack.com/client/T01ATQK62F8/C0288NJ5XSA), [FAQ](https://datatalks.club/faq/machine-learning-zoomcamp.html). |
| 17 | +- MLOps Zoomcamp: [`#course-mlops-zoomcamp`](https://app.slack.com/client/T01ATQK62F8/C02R98X7DS9), [FAQ](https://datatalks.club/faq/mlops-zoomcamp.html). |
| 18 | +- LLM Zoomcamp: [`#course-llm-zoomcamp`](https://app.slack.com/client/T01ATQK62F8/C06TEGTGM3J), [FAQ](https://datatalks.club/faq/llm-zoomcamp.html). |
| 19 | +- AI Dev Tools Zoomcamp: [`#course-ai-dev-tools-zoomcamp`](https://app.slack.com/client/T01ATQK62F8/C09HWT76L95). |
| 20 | +- Stocks Analytics Zoomcamp: [`#course-stocks-analytics-zoomcamp`](https://datatalks-club.slack.com/archives/C06L1RTF10F). |
| 21 | + |
| 22 | +For Slack norms that apply across all DataTalks.Club channels, see [Community Guidelines]({{ '/general/guidelines/' | relative_url }}) and [Slack channels]({{ '/general/slack/' | relative_url }}). For which channel to use for what, see [Communication Channels]({{ '/courses/zoomcamp-logistics/communication/' | relative_url }}). |
| 23 | + |
| 24 | +## Before Asking |
| 25 | + |
| 26 | +Try to narrow the problem first. You do not need to solve it alone, but a few minutes of investigation makes it much easier for others to help. |
| 27 | + |
| 28 | +1. Read the error message carefully. Check whether it names a file, line number, missing dependency, missing environment variable, port conflict, or permission problem. |
| 29 | +2. Check the course FAQ and the module README. |
| 30 | +3. Search Slack for the exact error message. |
| 31 | +4. Search the web using the tool name and the core error text. |
| 32 | +5. Check the documentation for the tool you are using. |
| 33 | +6. Restart the application, notebook kernel, Docker container, or terminal session if the problem looks state-related. |
| 34 | +7. If the setup may be broken, try reinstalling or recreating the environment, then record what changed. |
| 35 | + |
| 36 | +It is normal for technical problems to take time. If you are stuck after trying the steps above, ask in Slack. |
| 37 | + |
| 38 | +## How to Ask in Slack |
| 39 | + |
| 40 | +Start a new message in the course channel with a short problem summary. Then put details in a thread so the main channel stays readable. |
| 41 | + |
| 42 | +Include: |
| 43 | + |
| 44 | +- What you are trying to do. |
| 45 | +- The module, lesson, homework, or project step you are working on. |
| 46 | +- The exact command you ran. |
| 47 | +- The full error message as text. |
| 48 | +- Your operating system. |
| 49 | +- Your Python version, Docker version, or tool version when relevant. |
| 50 | +- What you already tried. |
| 51 | +- A link to your GitHub repository if the problem depends on your code. |
| 52 | + |
| 53 | +Use triple backticks for code, commands, and error output: |
| 54 | + |
| 55 | +<pre><code>``` |
| 56 | +paste the error here |
| 57 | +```</code></pre> |
| 58 | + |
| 59 | +## What to Avoid |
| 60 | + |
| 61 | +- Do not post screenshots of code or error messages when text is available. |
| 62 | +- Do not take photos of your screen with a phone. |
| 63 | +- Do not tag instructors for ordinary troubleshooting questions. |
| 64 | +- Do not create multiple posts for the same issue. |
| 65 | +- Do not delete the question after it is solved. Other students may need the same answer later. |
| 66 | + |
| 67 | +Screenshots are useful only when the visual state matters, such as a browser UI, dashboard, form, or chart. Even then, also include the relevant text and context. |
| 68 | + |
| 69 | +## Threads |
| 70 | + |
| 71 | +Use the same thread for the whole conversation. If the error output is long, put it in the thread rather than the main channel message. |
| 72 | + |
| 73 | +If the issue reappears later, you can start a new post. Explain what changed since the previous issue: new module, new machine, different command, updated dependency, recreated environment, or different data. |
| 74 | + |
| 75 | +## After You Get an Answer |
| 76 | + |
| 77 | +Reply with what fixed the problem. If the answer is useful and missing from the FAQ, contribute it back: |
| 78 | + |
| 79 | +- For public DataTalks.Club FAQ pages, use the [FAQ proposal form](https://github.com/DataTalksClub/faq/issues/new?template=faq-proposal.yml). |
| 80 | +- For course-specific Google Docs FAQs, add the answer there if the course team allows edits, or post the suggested FAQ entry in Slack. |
| 81 | + |
| 82 | +This keeps future students from getting stuck on the same issue. |
0 commit comments