For beginners, the most important skill is paying attention to details. Debugging error messages is extremely important. In fact, error messages are just a part of programming: they will be seen by both inexperienced and highly experienced developers. The only difference is that the more experience you have in handling error messages, the less time you will spend fixing them. The reason is as follows: over time, you will learn how to read error messages and quickly extract relevant details about the problem. The first time you see an error message, you need to spend some time understanding its actual meaning. But after seeing hundreds of error messages (you will see hundreds!), you will be able to identify the location of the problem and the relevant details needed to solve it. You should learn from every error message you solve. Don't just fix the error and move on; understand what is wrong with the code you are fixing. By learning from each error, you will be able to correct it faster the next time you make the same mistake.
Initially, you may seek help for every error message you encounter. Over time, you will learn to reduce the frequency of seeking help by carefully examining your code and doing smart Google searches.
The turning point stage is one of the most frustrating stages of learning to code, but in many ways, it is the only important stage. It is the point where you gradually stop relying on tutorials and start solving problems for which no one has prepared a solution for you.
The speed of coding at the turning point stage will be 10 to 20 times slower than before!!!
- I still feel like I'm in the abyss! I'm just getting more comfortable knowing that it's where I have to go!
There are two turning points in development.
The turning point in web development is the point where you can build any database-driven application you want. This means being able to build a web application with many pages that can store and retrieve information from a simple database. Web developers call it "mastering CRUD". At this stage, you should also be able to integrate with any third-party library (e.g. Ruby gem) by simply following the documentation or blog posts provided on GitHub.
The turning point in algorithms and data structures is a less obvious turning point, but it is actually more important. Those who conquer this point not only have a solid understanding of the fundamentals of programming and deep knowledge of solving complex coding challenges, but also have mastery over the programming language they are using.
What really matters in the end is:
- Having a solid grasp of web development frameworks
- Having a solid grasp of writing algorithmically complex code in any programming language
For each lesson, try to do something beyond the scope of the tutorial you are learning from. If the tutorial you are learning from provides "challenges" or "self-directed" sections, complete all of them. Solving self-directed challenges will give you valuable experience in working without structured guidance.
Try to rely on tutorials as little as possible.
In a certain lab, the teacher often guides students on how to integrate certain gems or work with provided documentation. Many students don't simply follow the instructions explained in tutorials for beginners, but instead follow the documentation and use the tutorial as a backup. Being comfortable with reading and following documentation on GitHub will help you when you are on your own.
Focus on the essentials and use repetition. Learn how to do common things like starting an application from scratch, pushing a new application to GitHub and Heroku, and building database migrations early on.
Pushing through the turning point can be challenging. Here are some tips to help you get through it:
Understand that this is a difficult process and be easy on yourself. Also, set realistic expectations. You can't compare the "superhero" learning tutorial speed with the "snail" self-learning speed. Remember, you are learning a lot, but at this stage, you are learning a completely new skill of solving new problems on your own.
If you are struggling with confidence, know that your feelings are completely normal. Keep working. If you continue to struggle, try talking to someone who has recently gone through the turning point. They will be able to understand where you are and assure you that what you are experiencing is temporary. Stay consistent in your work, but don't overwork yourself. Know that at this stage of the game, you can only work for a maximum of about 6 hours a day. Working in a state of exhaustion will only prolong the time it takes for you to reach the turning point.
The best way to gain confidence at this stage is to overcome any doubts you have. Your emotions may start to feel like a roller coaster. Sometimes, you will feel like you are on fire, but after struggling with the same problem for 15 hours, you will usually feel the opposite.
It can be frustrating not knowing whether something will take you 5 minutes or 5 hours, but the surge of confidence you need will come every time you successfully complete and implement a new feature. After solving some difficult problems without any help, you will become addicted to the feeling of building something outside of your comfort zone.