Working and collaborating with other people is an important part of working as a web developer. Therefore, we at The Odin Project encourage you to participate in our online chat community and forum, where we can all grow together and help each other learn web development. While you’re at it, you can check out our Facebook page and follow us on Twitter @TheOdinProject.
First, create a free GitHub account. As you will discover, GitHub is an integral part of the development workflow.
Learning web development will be a long and arduous journey, but you can make the marathon a lot more fun by pairing up with others. Connecting with fellow learners is a great way to bounce ideas off each other and motivate one another to keep going. Furthermore, helping others that are a few steps behind you is a great way to deepen your own understanding and make your learning stick.
When you’re slogging through the desert of despair, where your code doesn’t work or even make sense to you anymore, you can find an oasis of knowledge and encouragement in our community. Veterans at The Odin Project love to help fill in knowledge gaps and provide new insights and perspectives on how to improve your code. We’ve all been there before!
Remember that project you struggled so hard to figure out and that you’re so proud of finishing? Through our community, you will get to share your work and progress with those who fully appreciate how much hard work went into it.
We are working hard to update existing lessons and produce new content, so we would love to hear your feedback on the lessons and projects. We hope you find the lessons fun, engaging, and informative and find the projects challenging but achievable. So please let us know your thoughts!
As most of the projects are designed to push you to your limit, please remember that there is always a community to turn to! You don’t need to know how to solve every problem straight away, BUT you do need to have a general idea of where you are going. This becomes really important when asking your questions because sometimes the problem is your approach and not your code.
If you’re feeling stuck, it’s a good time to pause and take a breather. Break the problem down into little pieces and then decide what is really holding you back. We call this technique rubber duck debugging. If this method doesn’t yield a solution for you, it’s time to reach out to the community and ask for help.
When asking your question, please remember to include the context:
If you can’t pinpoint the problem, you can share a screenshot. This is especially useful for showing the output of commands in the command line. In Discord, drag and drop your screenshot image file into the chat box to upload it. In the forums, hit the ‘Upload’ button on a new reply.
If the puzzle still can’t be solved, push your project to GitHub so that others can comb through and debug the code. You’ll learn all about GitHub and how to do this very soon.
Asking your questions in a readable format helps everyone debug them better. Here are some ways to go about that:
If you’re having trouble on the command line, make sure to include both your input and the error message you’re getting.
In the chat rooms and forums, code can be displayed differently from normal sentences by using backticks (``), which can be found above the Tab key on US and UK keyboards. Backticks are not the same as single quotation marks (‘’), which are found to the left of the Enter key.
For a single line of code:
`#use one backtick at both ends`
For multiple lines of code:
In Discord, you can also use code highlighting to add color to your code by specifying the language:
Your Colorful Code
/giphy hito say hi to everyone.
/helpfor more information on chat commands.