Updated on May 25, 2020.
I ask everyone who subscribes to my daily developer tips a simple question: “what’s the biggest challenge you face as a web developer?”
I get back a ton of interesting responses, but the one I see come up over and over again is some variation of this:
It’s hard to know what to focus on and what to ignore.
The pace of change is part of what makes this industry so exciting, but this obsession we seem to have with tools (and creating new ones) instead of maturing what we’ve already got it is exhausting. You don’t see the same level of tool churn on the backend.
I’ve done a few things to help both inoculate myself from the madness and focus on the right things.
- Just-in-time learning.
- Stable technology over “the new hotness.”
- Targeted listening.
Let’s dig deeper into each of these approaches, and how I use them to stay sane in a rapidly moving field.
Rather than trying to learn all the new things that come out, I dig into new tools if and when I need them. This is a trick I picked up from Sara Soueidan.
For example, CSS grids and flexbox are old news at this point, but I didn’t learn how to use them until recently. Old fashion floating div grids had served me “good enough” for the designs I’d implemented, so the gains from using the newer technology weren’t worth the time and stress spent trying to grok it.
I make sure I know about new technologies and techniques, even if I don’t learn how they work until I need them. This helps me figure out what to focus on and use, and when.
Knowing vanilla JS deeply also helps me pick up new tools more quickly, and better evaluate their strengths and weaknesses.
Stable technology over “the new hotness”
There’s a tendency in our field to jump onto the new thing constantly.
Use Grunt! No, now it’s Gulp.
WordPress all the things. Nope, now Jekyll for static sites. No, now Hugo.
I’ve learned that less sexy, more stable technology is a blessing. Less bugs, better documentation, more resources. And, organizations prefer to work with trusted, stable technology as well.
Now, I ignore the noise.
If I were thinking about JS frameworks for a project today, I think I’d basically only consider React or Vue (with a bias towards Vue). The rest is just noise.
When I was first applying for web developer roles, I talked to a UX director who told me,
“Mobile is a fad, and one that I think is almost over. No one wants to do [thing they built] on their phones.”
I immediately ended the interview and said it wasn’t a good fit (seriously).
In the course of interviewing for roles, I ran into numerous people who shared this view, or just didn’t know about RWD. This wasn’t that long ago. It was 2013, and that point, RWD was already mainstream, if not 100% the norm.
I want to make sure I’m never that old developer who misses a trend because I write it off as “just a fad.” I don’t want to become obsolete. I imagine that’s your fear, too.
There are a few ways I try to make sure that doesn’t happen.
Twitter is my best tool here. I only follow around 100 people (to keep the signal-to-noise ratio low). In that circle are some trusted people whose views I value tremendously.
When they talk about emerging technology, I know it’s important to pay attention to.
I also use Twitter, conferences, and in-person contacts to find people who do roles I think I may want to move into and learn more about their roles. I ask them what the emerging trends are, and how they seem their role changing as a result.
In addition to forming relationships with some awesome people, I get to learn about what other people do, what’s important to them, what sort of things they see happening and changing how they work, and so on.
It’s always super informative.
What about you? Have any career tips or tricks I left out?