My linkedin feed is full of posts like “we stopped hiring junior frontend devs”, “AI replaces juns”, “use AI smart”. I really want to answer, not from position of hirer or a worker, but as a user.

My smartphone app glitches, a website for online ticket sale gives multiple error messages in three (3) different language for the same eror (true story), small store website takes so many resources I almost feel like there is some hidden Figma aoo running inside.
And all Linkedin is arguing about is “We don’t want more junior devs — Yeah, but whom are you gonna hire in ten years”.…

I used to look at Web Components like “what is this? Is it some modern thing I don’t understand, am I supposed to employ it now?”. As people move away from bloated JS SPA, some of them turn their attention to Web Components.

To not keep the suspense: Web Components are useless in their current design. The original idea of progressive enhancement is hopelessly lost, “you don’t need the JS framework” turned into Lit, Polymer, Stencil effectively creating frameworks on top of Web Components.…

I was looking for some convenient solution for simple self-hosted commenting, but instead was welcomed with a mix of personal playgrounds and vibecoding stands which are called “full-stack development” nowadays. I spent several days playing with those 3 commenting systems, studying and modifying their code, so this is not going to be a set of one-paragraph LLM-generated reviews, however, I’m still not deeply familiar with their codebase, so you might call it a “superficial code review”. In order of the encounter, here it goes…

I used to particupate in many discussions about microservices, but over time I began to notice one strange phenomena: when 10 people are talking about microservices every one of them has slightly different meaning of the word. It goes like this:
— Of course we use microservices. Our authorization lives in a separate microservice, game logic and stats live in the second microservices, and our PostgreSQL DB is a third microservice.…

I used to call myself a Rust hater, but really I was doing it just to compensate for the perceivable fanboyism e.g. Rust tops on stackoverflow surveys as most-loved language. There are many reasons to hate C++, and I hate C++ too. Lots of people were waiting for a better programming language, but got Rust instead.

There are several core problems with Rust:

1. Its compilation is slow. I mean SLOW. Slower than C++.…

Pretty much every person today by the age of 25 year has several teeth with fillings. I actually knew few people who already lost a tooth by that time (i.e. depulped tooth, refused to put a crown, tooth cracked).
It’s astonishing that galley slaves and other malnutritioned people actually had no problem with teeth. Yeah, they did not live long, but what I want to emphasize is that there is nothing forcing you to have cavities in teeth. It is also well known that dental caries epidemic started approximately the same time as sedentary agriculture.

https://www.thelancet.com/journals/lancet/article/PIIS0140-6736(97)11096-0/fulltext — RETRACTED: Ileal-lymphoid-nodular hyperplasia, non-specific colitis, and pervasive developmental disorder in children

Modern CPU-s suck horribly. All we were able to do in 30 years is to finally switch to a weak memory model and partially reduced instruction set…

There is a big project for TypeScript called Effect (https://effect.website/). I think their motto should be “we will sacrifice everything to not employ BEAM”.

I’m a bit late with a reaction, but I quited frontend development right when the madness hit the peak and it’s worth taking a glance back. It’s sad to conclude that madness won: we officially have approx 50-100 different JS-related frameworks