Create a feedback loop
Your goal is to maximize your time and condition your mind. Your most finite resource will be put to the best use if you can see it working or more importantly, failing.
There are two stages of the feedback loop. First you want to get to the point where you are able to view a valid error message about your code while trying to run it. It doesn’t matter if you are learning your first language or your 11th you will have to be able to copy and paste errors into google. This is “fail fast” in its most pure form.
Second, once you have a compiling and running project you need to be able to see the changes you make in code reflect in your UI or terminal output. As you write code you need to be able to make the connection between your changes and how it affected the program. This will inevitably lead you back to the first stage of the feedback loop where you break your code and are working on errors.
The feedback loop is simply like exercising. Your mind will become proficiently conditioned to preemptively recognizing details and patterns that make a piece of code work. If you can reframe the frustration a lot of new programmers feel and focus on the “process” you will start to notice two things. You will make fewer mistakes and you will start to solve problems in your head before even writing code. It’s truly “Muscle Memory”
Every programmer knows the punctuating joy of seeing something work, especially a problem you have spent considerable time on.
Find a tutorial or search results that work for you
Getting down and dirty with your feedback loops is the most important step to learning. It’s the glue between rote, understanding, application and correlation of the learning process.
The internet has commoditized information. It’s at your fingertips and that can be overwhelming. Fortunately, the variety will help you discover an instructor or writing style that works for you. Yes, you might end up wasting 12.99$ on a Udemy course that never gains traction with you. However, your time…
