8 Things I Wish I’d Known When I Started as a Web Developer

I have been in web development for more than five years and it’s been quite a journey — trying out different technologies and experimenting with different styles. I’ve been successful at times, but I’ve also had my fair share of disappointment. In this post, I’m going to talk about certain realizations I’ve had over the course of my life as a web developer, with the hope you can learn from my mistakes.

1. Write Clean Code

Source: funny-memes.org

Source: funny-memes.org

The first thing you realize when you start making large applications is that a huge amount of time is required for debugging. Often, you’ll spend more time debugging than writing new code.

In such a situation, it’s highly important you write properly indented and commented code, which adheres to best practices. Imagine you have hundreds of lines of code, and you have no idea what’s causing a small bug. What’s worse is that if you write unreadable code, you’ll probably fail to understand what each snippet does after some time. Are you sure you want to go down that path? Here are some tips to make writing clean code easier.

2. Language first, framework later

Source: Giphy

Source: Giphy

People often first learn the tricks of a framework, and then move on to the language. That’s actually not the right way to go.

The popularity of Django can be attributed to the strengths of Python — so it’s important that you get comfortable with Python before trying out Django and not the other way round.

The simple reason here is that if you know about the underlying language, it helps you understand how the framework works. If you have no idea about the trades of a a language, there is no way you will understand why something is done a certain way in the framework.

3. Learn JavaScript, not jQuery

Getting a bit more specific than the idea raised above, I would like to give special emphasis to JavaScript, which is the most accessible language in the world. Any device with a browser is capable of running a JavaScript application.

The mistake that young developers often make is to “learn jQuery”. Questions like these on Quora suggest that jQuery is a very popular option among people who have no idea how the underlying JavaScript works!

jQuery is just a set of wrapper functions written over JavaScript and the only reason people prefer jQuery is because of the fewer number of lines of code required. However, recent versions of JavaScript (or ECMAScript as it is originally known as) have made the syntax more user friendly, making many jQuery functions obsolete.

I am not saying using jQuery is wrong. I am just telling you to follow the correct learning path. If you have no idea about closures and namespaces in JavaScript, how would you explain the use of “$” in jQuery?

4. Don’t just read, implement

I’ve often seen developers read through tutorials or sometimes even whole books without anything much to show for it. However, my biggest concern is how much would you retain if you just read?

If you want to learn Ruby on Rails, try to develop a small application as you are going through the documentation or a set of tutorials. If you want to try the MEAN stack, get it running in your local machine and explore the different options — that’s the best way to learn!

5. Jack of all trades, Master of one

It’s good to explore new technologies, but one must remember to stick to one for most purposes. It’s always tempting for beginners to learn multiple languages at the same time, but it’s advisable to stick to one until you develop a certain level of mastery over it.

Once you have a go-to language for your day-to-day needs, you can move on to new ones. You may also changed your preferred language in this process, but attempting to master one before you move on to others is often a wise decision. Here’s some advice for choosing which one to start with.

6. Learn version control

In today’s world, it’s very rare that you work on a project alone. To collaborate with others, you need to learn something called version control!

Developers usually don’t dive into version control until they absolutely need to do so. However, as version control is necessary to work in a team, it’s a good idea to understand how it works and the basic commands that get you started early on.

7. Learn from the work of others

Mastering a technology on your own is great, but sometimes you learn a lot by just looking at the code of others. Be it your colleagues or random tutorials on the internet, try to find why someone approaches a problem in a certain way — and ask questions if necessary.

It’s also important for developers to realize that it’s impossible to know everything, but the knowledge is out there — you just need to Google it. As a beginner, if you’re stuck there is high probability that someone like you had the same problem in the past and the solution is somewhere out there in the internet (this often happens to the veterans too!)

8. Ask for code reviews (and enjoy them!)

Over the years, code reviews have immensely improved my programming skills. Proper code reviews take time on the part of the reviewer, so you should always ask others to review what you have written — your peers as well as mentors. It helps expose loopholes in your approach, and makes you learn. If you find someone who genuinely takes interest in reviewing your code, take their reviews seriously. Here’s a look at an advanced way to code review.

Lastly, never take code reviews personally. Code is like art — it’s difficult when someone points out errors in what you have created, but code reviews can only make you better — provided you take them the right way!


This post stems from my experiences as a web developer and what I have learned from events that have shaped my life. For further reading, check out this article on how to be a good developer.

What have you learned that you would have loved your younger self to have known? Let us know in the comments below.


  1. I’m guilty of a lot of those points as well, especially number 5’s: Jack of all trades, Master of none. When I first started out, I wanted to learn it all and I wanted to learn it all right that instant. I made the mistake of trying to learn too much at once and ended up slowing myself down and even becoming overwhelmed.

    A ninth point that others might find useful is to beware of snippets written by others. I’ve often found myself stuck during the coding process and used to run off to find a snippet that someone else has written to do what I need. Implementing other people’s code does work, and it’s not a bad thing to do, but make sure that you understand what it’s doing and how it works before you forget it. Much like you mentioned in your first point, at a bare minimum, leave a comment with a link to the page where you got the code to remind you what the code does (and also give credit where it’s due).

  2. I wish I had learned version control as soon as I was starting to write code. This could have saved me hours of headaches caused by accidentally deleted code. I had to rely on multiple copies of the same project on my PC.

  3. I definitely disagree with you - learning JQuery once you know JavaScript is trivial - a significant fraction of JQuery questions are asked by people who didn’t learn JavaScript first where the answer to their question is one or two lines of native JavaScript. Learning JavaScript after you know JQuery is not much different from if you didn’t already know JQuery and so you will spend time to learn it as if it were another completely new language.

    I created a site with examples of JavaScript and JQuery code - the several hundred JavaScript examples come first followed by 15 examples that cover JQuery completely - simply because most of the JQuery commands refer back to the JavaScript example that does the same thing and so whole groups of JQuery commands that are used the same way can be dealt with in a single example since the JavaScript page already covers everything else about what each JQuery command does.

    Of course there are lots of JavaScript pages that the JQuery doersn’t link to because there are lots of things that you can do with JavaScript where JQuery doesn’t help at all (such as being able to send information to the server where you don’t need a response back - which only requires 2 lines of JavaScript and where the shortest JQuery code to do the same is about 10 times longer - not counting the JQuery library).

  4. If you learn JavaScript properly then you will very quickly have your own library of code that fixes all of those quirks and can just use the ones you need. Plus once you know JavaScript a few seconds more and you will know jQuery as well - saving about 3/8 of the learning time to learn both.

    The way many people use jQuery it is like placing your house into your hand luggage to go on a short trip rather than just taking what you need.

    Also there are now two versions of JQuery - one that is huge and provides patches for every imaginable IE6 browser quirk - and one that provides the same functionality for modern browsers that is a small fraction of the size and becoming smaller all the time now that most JQuery commands are being adopted into JavaScript itself. The main purpose of JQuery wasn’t to fix the quirks, it was to add commands that the author considered should be in JavaScript and so JQuery itself should disappear within the next few years as what JQuery commands are not in ES6 (due for release in March) will be in ES7. Within 5 years JavaScript will still be around and JQuery will be the history of some of the commands (not implemented using the exact same command but doing the exact same thing).

11 more replies