If you have any questions, ask them
in the #course-data-engineering channel in DataTalks.Club slack.
To keep our discussion in Slack more organized, we ask you to follow these suggestions:
- First, review How to troubleshoot issues listed below.
- Before asking a question, check the FAQ.
- Before asking a question review the Slack Guidelines.
- If somebody helped you with your problem and it's not in FAQ, please add it there. It'll help other students.
- Zed Shaw (of the Learn the Hard Way series) has a great post on how to help others help you
- Check Stackoverflow guide on asking
The first step is to try to solve the issue on you own; get use to solving problems. This will be a real life skill you need when employeed.
- What does the error say? There will often be a description of the error or instructions on what is needed, I have even seen a link to the solution. Does it reference a specific line of your code?
- Restart the application or server/pc.
- Google it. It is going to be rare that you are the first to have the problem, someone out there has posted the issue and likely the solution. Search using: technology problem statement. Example:
pgcli error column c.relhasoids does not exist.- There are often different solutions for the same problem due to variation in environments.
- Check the tech’s documentation. Use its search if available or use the browsers search function.
- Try uninstall (this may remove the bad actor) and reinstall of application or reimplementation of action. Don’t forget to restart the server/pc for reinstalls.
- Sometimes reinstalling fails to resolve the issue but works if you uninstall first.
- Ask in Slack
- Take a break and come back to it later. You will be amazed at how often you figure out the solution after letting your brain rest. Get some fresh air, workout, play a video game, watch a tv show, whatever allows your brain to not think about it for a little while or even until the next day.
- Remember technology issues in real life sometimes take days or even weeks to resolve
- Before asking a question, check the FAQ.
- DO NOT use screenshots, especially don’t take pictures from a phone.
- DO NOT tag instructors, it may discourage others from helping you.
- Copy and paste errors; if it’s long, just post it in a reply to your thread.
- Use ``` for formatting your code.
- Use the same thread for the conversation (that means replying to your own thread).
- DO NOT create multiple posts to discuss the issue.
- You may create a new post if the issue reemerges down the road. Be sure to describe what has changed in the environment.
- Provide additional information in the same thread of the steps you have taken for resolution.