Over the years that followed, I considered getting a formal education, and I could see the value in doing so, but in the end:
- It was too expensive.
- I struggled with learning in a classroom setting.
- I was already making comfortable progress.
But it’s not like this was always an effortless process. I wasn’t just learning how to code for the web, after all. I was also learning how to learn, and that’s what we’re about to discuss.
Here are five steps for teaching yourself web development.
1. Pick an area of web development that excites you.
You can’t just “become a web developer” by reading a certain book or watching a certain number of videos. Web development is a big field and trying to be a jack-of-all-trades will likely leave you exhausted, frustrated, and only a little further ahead than when you first started.
Being a web developer is like being a scientist. There are foundational ideas that apply across disciplines but, ultimately, you need to specialize. You have to commit to something forever though — it’s easier to move to another area once you’ve mastered one — nor will you be limited by your choice. Someone who is intricately familiar with PHP can do a lot more than someone with a basic grasp of ten cutting-edge web technologies.
2. Ignore (most of) the “guidance” from seasoned web developers.
Seasoned web developers usually offer well-intentioned advice to beginners that is completely impractical to implement. This is because they:
- Don’t remember being a beginner.
- Expect too much from someone who just needs to grasp the basics.
- Have preferences based on problems you may never encounter. (Such as issues with scaling to millions of users.)
Ask what language you should learn, for instance, and the debate that follows won’t be what’s best suited for you. It’ll be a debate based heavily on the biases the developers themselves have developed through their work.
Here’s how I see it:
There are experienced web developers with great advice but, when advice is offered, ask yourself: Is this truly the best way for a beginner to approach this process? Or is this simply how the developer had wished they’d learned?
3. Give yourself a precise (and achievable) project.
After learning the basics of web development, try building something without following a book or tutorial. By far, this is the most effective way to:
- Get the thrill of making something.
- Discover the weak spots in your knowledge.
- Learn how to actually solve problems.
It doesn’t matter what choose to build but keep the scope of the project as small as possible. If you can forsee yourself spending days on this project, it’s too big. Make it smaller. You don’t want it to drag-on.
Also make sure to define an end-point for the project. What features will it have when you can label it “done”? You want to know when you’re allowed to feel satisfied with what you’ve made. (And this doesn’t have to mean when the project is ready for the world since there’s no need to publish the creation.)
Depending on what area of web development you specialise in certain projects may be simpler to create but here’s a few ideas worth considering:
- A to-do list application.
- A private blogging tool.
- A tool for tracking workouts.
Basically, any sort of project that’s main purpose is to track some basic data is a good way to test your knowledge as a beginner.
4. Commit to a specific amount of daily practice.
When you’re getting started with web development, you’ll make quick progress in some areas, but there’ll come a time when your progress slows and this is where a lot of beginners throw up their hands in frustration, and give up.
This happens because beginners usually rely on achieving milestones to feel satisfied. Milestones aren’t predictable though. After getting a handle on the basics, you can go days or weeks without making significant leaps.
There is, however, an alternative approach:
Instead of focusing on achieving milestones, commit to learning and practicing web development for a specific amount of time every day. At least twenty minutes is a good starting point but there’s no precise limit or requirements. Just pick whatever length you can reasonably manage on a consistent basis.
The point in commiting to a time frame is that you’ll then allow youself to feel satisifaction for meeting that commitment. The milestones will continue to arrive, but as a pleasant by-product, rather than an unpredictable goal.
5. Engage with a significant amount of training material.
You may have seen the writing-focused video from Ira Glass where he suggests that people “do a lot of work.”
It’s a simple belief that leads to a state of skill, and the idea easily applies to web development. You have to write a lot of code if you want to be a developer but what a lot of people don’t realise is that the code doesn’t have to be your own. There’s an immense value in following along with the code from books and tutorials and video training material — like that covered on sites like SitePoint and in books and courses from sites like Learnable.
You do have to be engaged with the material — you should consider the purpose of each line of code as you’re writing it — but even though you’re “learning by rote”, you’re still learning.
Here’s what most people don’t consider:
The syntax isn’t the difficult part of web development. It’s a stumbling block for beginners but, afterward, the tricky part is determining how to think about how to solve certain problems. Here, the grand irony is that beginners often think of far more complex solutions than a professional would.
With this in mind, the benefit of following allow with an immense amount of training material is that:
- You can see how different developers solve different problems.
- You can see how different developers solve similar problems.
When you’re ready to work on your own projects, this exposure to how problems can be solved will provide the mental tools required to:
- Identify the core of what the actual problem is.
- Figure out what’s required to solve that problem.
You may not be able to recall any precise solutions, but that won’t matter. Most problems have been solved before, in some form or another, and half of the difficulty of “speaking in code” is understanding what you’re trying to say. Beyond that point, the syntax and details are far easier to grasp.
I’ve only shared a handful of “big picture” tips for teaching yourself web development, but they’re definitely things I wish someone had told me when I first got started.
If you’re already on your self-education journey, where did you begin? And how have your techniques for learning changed since first getting started?