The AI asteroid is hitting frontend web development
The asteroid currently hitting front end web development
Nolan Lawson, a veteran frontend developer and former browser performance engineer, argues that AI coding assistants are reshaping the field. He observes that many prominent educators are leaving or pivoting, and that agents are increasingly handling frontend tasks with less human oversight. He predicts a decline in emphasis on developer experience and standards that only improve authoring ergonomics, while noting that agents' familiarity with React is driving framework choices. Despite the bleak outlook, he suggests that educating agents about architectural principles and building agent-friendly websites could be fruitful directions for frontend education.
For better or worse, React is heavily overrepresented in the training weights, and “agent experience” is starting to matter more than developer experience.
- comrade1234
My wife's experience is managing teams and has been involved in creating corporate websites using contractors. She doesn't know anything about html at all. She just manages people.
She's now working on a biotech start-up pre-funding. They have pretty much zero money. They want to redesign their website.
I set her up with my deepseek key and she's been using flash-v4 with image detection (I think deepseek says it's still experimental). She just provides the current website, tells how she wants it to look and it works great. I mean it's obviously ai generated but she gets quick results and is able to tweek things to look better by just telling deepseek what to do. She was even able to change the text in one of their images to its new product name without having to contact the graphic designer.
This is a simple example. Basically it's one of those earlier jobs that you could get someone to bid on for $x but now you can do yourself for $20.
- etoxin
I was originally a Flash developer, when that died when Steve Jobs banned it from iPhones, I pivoted to frontend. I got to see web evolve over the next decade or so and loved every part of it.
Now, still as a frontend engineer albeit much more senior. The writing is on the wall, again. It's time to reskill for AI.
It's not bad news.
We as experienced engineers are needed to help build in the guardrails, frameworks, the new tooling, etc. There is a lot of work that is needed that requires actual engineers with technical experience.
Like the early internet, I see this as a new beginning and we get to decide how it evolves.
- CqtGLRGcukpy
There is going to come one day that companies (and any website owner) will wish they didn't use AI and instead used a simple (maybe even plain-text) website. That will come when people really need information from that website but can't get to it.
https://sparkbox.com/foundry/helene_and_mobile_web_performan...
Discussion regarding that post: https://news.ycombinator.com/item?id=46494734
- thelastgallon
I can't wait for the asteroid to hit C-Suite and senior execs. These are the most meaningless jobs and easiest to automate, with the most cost savings.
- rickbergfalk
> Meanwhile, Cursor and Viget have blogged about migrating their codebases from Solid and Lit, respectively, to React.
That was maddening to read. Here I was thinking we should all be migrating to better performing frontend solutions. Does it really take an agent that many more tokens to write Lit or regular HTML and HTMX?
- cube00
> If you write a React component with an agent, though, then the risk of just yolo’ing it into production is (typically) much lower.
If your state management gets out of sync with the form controls your users are working with it can become pretty high risk because now users see one thing and something else actually gets sent to the backend.
- tuesdaynight
In my useless opinion, most people are not aware of how big AI is and how bigger it will be in 3~5 years. It's not worthy to be worried about it, because it will be a global problem, but there are people who are completely blind about it
- Supermancho
> The frontend is less risky to just hand to an agent.
The smaller the problem, the less risky it is to do this, regardless of the nature of the problem. This is not a frontend-specific issue today.