#1 Coding Out Logic
JavaScript is a functional programming language. To code something out you must first know how it works. For example, if you were going to build a keystrokes visualizer on a webpage. First, you would have to detect keystrokes. Next, you would have to light up the key on the webpage. If the key stays pressed, it must light up for as long as it does.
#2 Code Sprinting
Sometimes you need to write out large blocks of code in a quick time frame. To do so, you need to sit down and spam that keyboard with intense focus. To do so, you must code sprint. You're not running a marathon, you are sprinting. You are vast amounts of coding brain power in a quick interval.
#3 Figuring Out The Problem
When building projects, there will be times when the code isn't working. There will also be times you won't even know what isn't working with your code. Finding out what's wrong with your code is a tricky but critical component of debugging.
#4 Fixing The Problem
When building projects, there are times when tricky problems arise. Finding the solutions to them, if done inefficiently, is time-consuming. To be more time efficient you must have a system ingrained into your mind. Whenever a tricky problem arises, you should instinctively start to find a solution. You should also accumulate knowledge over time, especially when you aren't encountering problems. By doing so, you're preparing for tricky problems to arise. If prepared, you won't have to scavenge the internet for a solution.
#5 Reading Code
Do you remember those times you are scanning some code, and a large block of complicated code shows up? You're crying inside, realizing reading through it will split your brain. Nobody should write code like that in the first place because nobody should have to read code like that. But at times you need brain power to understand the logic of even efficiently written code.
#6 Improving Your Project
When working on a project, you are never done, but sometimes you get to a point where you complete a component. You can then work on another component, or improve that one by improving the code. Sometimes this is for a personal sense of satisfaction over the code written. Sometimes this is necessary when your code is less than satisfactory. One way to do that is to add more features. When building a project, you need to think of new components to add to it. You don't need features pumped out, but thinking of new ideas is critical to improving a project. You must always be thinking of ideas for features as a developer.
#7 Writing Efficient Code
More lines do not equal better code! Fewer lines do not equal efficient code! You must find that sweet spot of balance for the code you write. Don't write hundreds of lines for what is possible in tens. Don't condense the crap out of everything. Stop making it unreadable!
BONUS! Code To Image Tools
Code-to-image tools help you become a better-liked developer. By sharing code better, you will make it less of a hassle/strain on people's eyes. You'll be making code snippets visually appealing. To learn more about code-to-image tools, check out my recent post about them!
Comments