My entry in the canon of explanation for why JS developers always seem so tired
And like any swimmer worth the salt in this particular sea, I'm compelled to write what I think about it.
Usually, the Churn is framed as a Very Bad Thing. In fact, this is such an accepted point of view that it's become a meme.
$el.fadeOut() and 22-year-olds shitting on 35-year-olds who call
$el.fadeOut(). It’s a mess.
And all of these different developers are writing Medium posts and Dev.to posts and personal blog posts about why their chosen stack is the Right One, which means that no matter what you think you’ll always find someone telling you You’re Right; but which also means that no matter what you think you’ll always find someone telling you that You’re Wrong: which can be confusing in the extreme if you are part of the half of all developers who have been doing this for less than 5 years.
Which, I think that’s what makes the Churn so painful: it’s not that there are lots of options, but that the discussion around those options is exhausting.
And this promotes burnout and instills in developers the sense that they will never been good enough. That there is always something new and exciting to learn around the corner. I have a real, gnawing sense of dread that if don’t keep moving, my skillset will, over 3 or 4 months, become obsolete: and I will become unemployable.
So what does this all look like in practice? It looks like an industry of developers with a tonof breadth and almost no depth. It looks devs with 5 years under their belt: 1 year of experience in 5 different technologies. It looks like a bunch of burnt-out white dudes with beards wandering around trying to see around corners; or maybe a few slightly-less burnt-out white dudes building up corners for everyone else to try and see around.
It just looks exhausting.
Walking up to the source of the Tees and Cross Fell.
BEM + utilities: a hybrid methodology
Yet another CSS methodology: one that works pretty well for me.