We're Making the Dreamweaver Mistake Again

AI is putting design back in charge of code.

For twenty years, we worked to separate these roles. Designers designed. Developers built. A human acted as the bridge.

AI changes this. You point a model at a design file and it generates components. The design drives the code again.

This sounds efficient, but it carries a risk.

In the old Dreamweaver days, a human sat in the middle. That person enforced quality. With AI, the design goes straight to code with no one in the driver's seat.

There are two things you must understand:

  • Design files are not design systems. A file is judged on how it looks. A system is judged on reuse, durability, and states. AI blurs this line.
  • AI is great for static sites. If you just need a snapshot, use it. The problem starts when you build a reusable system, like a custom CMS or a dynamic UI.

The real failure happens in the details.

Teams often build code pipelines around Figma variable names. Naming is a design choice, but AI turns it into a rigid contract. If a designer renames one variable, the whole pipeline breaks.

A design is a static snapshot. It shows one screen in one state. It does not show:

  • Loading or error states.
  • Content-driven vs. fixed layouts.
  • How a CMS feeds the data.

That context lives in a developer's head, not in a design file.

Industry leaders are trying to fix this. Google released DESIGN.md to give AI more structure. Tools like Fixel help catch design drift by validating code against Figma.

But even the best tools have limits. They can extract pixels or tokens, but they cannot make architectural decisions. They cannot decide whether to reuse an existing component or build a new one.

The future is not about design driving code. It is about a middle ground.

I believe this middle ground requires:

  • Typed CSS inputs at build time.
  • AI proposing how designs map to your existing system.
  • UX engineers making the final decision on behavior and meaning.

AI makes designers more responsible for code quality. Because the design becomes the code, there is no one left to gatekeep the translation.

We must not write the UX engineer out of the loop. We need people to own the mapping and the contract between design and system.

How do you decide what the AI proposes and what stays yours to decide?

Source: https://dev.to/slafleche/were-making-the-dreamweaver-mistake-again-on-purpose-this-time-ema