I don’t know about you, but I’m obsessed with testing my code. When I first started writing code, I was very concerned about testing my code. I thought I would have to hire a programmer to test it. That was before I’d gotten my first job. I used to sit in front of the computer and do my testing code.
I had to do testing code for me. I had to write the tests myself. I never thought my code could test my code, because I had to work on it. I was a little frustrated when I discovered my code was working just hard to make it more enjoyable. I was even annoyed when my code was not working when I got my first job.
The difference between me and most developers is that I’m a perfectionist. I really am. I don’t care about anything else in the world except my code. I don’t care about my code’s quality, it’s just my code. I want to make it perfect, I want to make it bulletproof. I didn’t get to that point in school because I was so focused on my code, but I’ve made it that way since I took that first job.
The problem was that I was way too distracted by my own work and my own projects. I was having trouble focusing on my main project. It was a lot of work for me and my own projects that I didn’t really understand in the first place.
Well if you want to improve your skills, I recommend working on some of your own code. In the same way that you should learn to do the dishes before you get your food into the toaster, you should learn to code before you learn to cook. Your code will save you time in the long run, because it will save you from having to do the dishes or cook your own food.
JavaScript is one of those things that’s easier to learn than it is to do. You can learn it pretty quick and pretty easily, and if you’re not quite good enough yet to create a website with a few hundred lines of code, I don’t think you need to worry about it. I learned this stuff long ago, and it’s still just as easy, and still more efficient, than I expected it to be.
My first experience with JavaScript was back at the beginning of the internet when I worked at a startup. My job was to make a web app that had to be interactive to be successful. The only JavaScript I was allowed to use was for the interactive part. I had to create a whole bunch of Javascript that did very little except fetch data from the server or display it. To me, this was simple because you could just write a bunch of lines of code to make a simple webpage.
The problem was that this wasn’t very efficient. Back then I could just hack together a webpage on my own with a few lines of Javascript, but now I know it can often be more efficient to hire someone to do it for you. For instance, the most efficient way to write a Javascript function is to create an object that has a function as a property and pass the object as an argument to that function. This approach is called “functional programming.
JavaScript is not a first-class language. While it can be written in a functional fashion, it’s also imperative. This means that Javascript code is generally simpler than some other languages, but may be more verbose. This doesn’t mean you shouldn’t use it. You should use it to solve problems that you know how to solve with other languages, however.
For the purposes of testing Javascript, I would recommend using a tool like Selenium to run tests over a webpage. A more modern replacement is Mocha, which is a Javascript library that can be used to test Javascript code. It also comes in a library that can be used for testing code with frameworks like AngularJS.