Why It’s a Good Idea to Be a JavaScript Developer, and What it Takes to Be One

I'm not what one might consider a back-end developer (or a web developer at all, for that matter), but the overgrowth of web tools in the web 2.0 aftermath has made web tools somewhat hard to ignore as of late, so I had to sporadically develop what can be considered back-end code. Even front-end, which I have done grudgingly.

To me, JS -- and in fact the whole web environment -- is a second-class citizen. I come from a vastly different background (embedded and systems programming), and the fact that people manage to write anything useful with today's web technologies is astounding. I honestly admire the craftiness of web developers, although I have very few good words to say about pretty much anything else that comes out of their hands.

I cannot help seeing them as second-class citizens because:

1. They are simply tools made for different purpose. HTML is there to annotate the structure of some content, CSS is to annotate its appearance, JS is for some limited interaction. What people managed to build with these limited tools, compared to the crap we were writing the last time when I seriously touched web programming (let's just say that PHP wasn't yet popular when that happened), is astounding, but I cannot help wondering if the web wouldn't be a lot better if people had actually stopped to think about better tools for a moment. Every time I see yet another awesome demonstration of a JS game, my initial enthusiasm is chased away by the realization that thirty years later, people are still enthusiastic about stuff you could make on an Amiga, were it not for the gazillion cycles wasted between the hundreds of abstraction layers involved in painting a pixel and for the latency involved with pretty much every I/O operation.

2. It's shaggy. Dear God, it's shaggy, full of barely-documented hacks. If you want your webpage to have a drop-down menu, there's a thousand something.js packages that help you do that, but all of them have their own quirks, their own issues with styling, their own little manner of use and so on. It reminds me of writing X11 applications using nothing but Xlib, when everyone was using their own menu widget that worked in a slightly different manner from every other application. The Unix desktop was not too fun to use back then, and the fact that people not only consider that kind of behaviour to be OK now, but actually want it, is beyond comprehension to me. It doesn't help that a large portion of the community seems to struggle with even the most basic programming concepts, which makes reading source code or documentation a very unpleasant experience.

3. The tooling is terrible (but this one is becomming less and less of a grievance).

  > I'm wondering if, rather than transform yourself into a 
  > magical-unicorn designer/hacker - it might be better to 
  > get solid at development, solid at design, but aim to 
  > only get good enough that you can manage people who are 
  > better at you in those areas?

Note that "we're still figuring out what this product is" stage startups really hope to find these "superhero" types, as they can litterally breathe life into a product by themselves. Larger companies can't depend on hiring people with all skill sets, as they're too rare.

I think what the recruiter meant when he said "those people don't exist" was really "those people aren't available to you." In a highly competitive job market, these "unicorns" can get any job they want, or even stay independent, and both make more money and have a higher quality of life than most startups could provide. Recruiters know this as they are the ones trying to locate these people, but hiring managers might not have this perspective.

Roles where demand exceeds supply often start receiving a lot of hype and faux-respect in a effort to attract people to bridge the gap. As soon as the gap is bridged adequately, people will go back to seeing JavaScript "ninjas" as the code-twiddlers they really are. It's similar to how soldiers are patriots/defenders/heroes when someone is required to dive on a grenade, but "grunts" otherwise.

The sad thing is, people let it go to their heads. Another sad thing is how easily these JavaScript developer types are swayed compared to other professions. I mean, who really takes pride in being called a "ninja", besides 12 year old boys?