Skip to content
All posts
2 min read

AI Won't Replace Front-End Engineers

Models generate components in seconds. That was never the hard part of the job.

  • #ai
  • #frontend
  • #career

Every few months someone announces that frontend is finished, because a model can now turn a sentence into a component. I use these tools every day, and I am not worried. Not because they are bad. They are genuinely good. I am not worried because writing the code was never the hard part of this job.

The easy part got easier

LLMs are brilliant at the bit that was already easy. Boilerplate, a form, a card, wiring up a hook. Ask for a component and you get a reasonable one in seconds. That is real, and I lean on it happily. It clears the busywork so I can spend my attention on the parts that actually need it.

The hard part is still hard

The hard part of frontend is judgment. Which of the ten ways to build this is right for this codebase. What happens on a slow connection, on a 320px screen, with a screen reader, when the API hands back an empty array. What we should not build at all. None of that lives in the prompt, and a model will cheerfully give you confident code that ignores every bit of it.

Here is a real example. I asked for a delete control and got this.

<div className="button" onClick={handleDelete}>
  Delete
</div>

It renders. It clicks. It would sail through a quick look and ship. It is also broken. You cannot focus it with a keyboard, it has no role, and it does nothing when you press Enter or Space. To a screen reader user it may as well not exist. The fix is boring.

<button type="button" onClick={handleDelete}>
  Delete
</button>

The model did not know that mattered, because nobody told it. Knowing it matters, and catching it before it ships, is the job.

The work moves up a level

So the shape of the day changes. Less typing, more directing and reviewing. I spend more time writing a clear spec, reading a diff closely, and spotting the one subtle wrong thing than I do producing the first draft. That is a different skill from remembering API signatures, and honestly it is a more valuable one.

What actually protects you

Taste. Knowing what good looks like. Caring about the person on the worst device on the worst connection. Being able to say why one approach beats another, not just that it compiles. A model can produce a hundred variations of a thing. Deciding which one is correct is still yours, and that decision is where the value was hiding all along.

AI is not coming for the engineers who understand the browser, accessibility, and the people using the product. It is coming for the idea that frontend is just typing out components. It never was.