I can't speak for everyone, but in the 6 years and 4 companies I've worked for, we have hired only 2 front-end engineers. Full stack is simply what we want a vast majority of the time. So I'm not saying it's impossible to find something but just from a numbers perspective it's just not in demand (I worked at 2 startups and 2 mid-size companies, big tech probably does hire front end devs, but I can't say for sure).
As a frontend developer, with the usual caveats of anecdotal experience etc, I'm somewhat inclined to agree when talking about regular employment. Over the last decade or so I've worked in companies that range from a few employees in total to thousands of people, and most of the time I'm either the frontend guy or one of a very small handful. Most of the time the value you bring to the table from the technical side is unblocking other people, that is, making sure the design system is consistent, everything builds, nasty frontend-specific bugs are fixed, etc. Everything else can be delegated to generalists which gives the company a lot more flexibility around how to hire and arrange work.
The one place where this trend does not hold in my experience is contracting. I've done a fair bit of it throughout my career and being a frontend development contractor or similar is like selling hot cakes if you bring a lot of experience to the table. The main customers are generally companies who don't have that one guy who figures out frontend stuff and in the end they have a critical mass of mess that they hire someone from the outside to come in and fix pronto.
I don't think I'm alone in that if I'm reading something that is anywhere near a 1-star, I don't finish it. And then go on to not leave a review. This skews my ratings indeed, because not every book I start is between 3-5 stars, but almost every book I _finish_ is.
Have been reading "What's Our Problem?: A Self-Help Book for Societies" by Tim Urban? I've been loving it, and he talks about the importance of 2 counterparties identifying what _is_, before distinguishing what _should be_.
This is an era where "what you listen to" is entirely a personal choice, no 2 groups of people hear the exact same set of songs unless they want to. Same goes for movies, TV, any consumed media really.
Interesting that the top 2 comments (when reading this) are at opposite ends of the sentiment spectrum over the name. Personally I think it's one of those names that sucks to use in conversation but great to use on the command line. Of course aliasing or abbreviations can also get you there.
I believe a very similar use case was the original primary function of Richard's compression algorithm in the show Silicon Valley. Which of course was entirely underutilizing the technology but that was the joke.
reply