We're making the Dreamweaver mistake again

AI is putting design back in charge of code.

For twenty years, the industry worked to separate design from code. Designers designed. Developers built. A human translated between the two.

Now, the pendulum is swinging back. AI takes a design file and writes the code directly. This sounds fast. It feels efficient. But it creates a massive 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.

This is not a problem with designers. Designers do great work. A design file is judged on how it looks. A design system is judged on how it works, how it scales, and how it stays durable.

AI blurs this line. It treats a static design snapshot like a permanent foundation.

Here are the two main ways this fails:

  • Naming errors: Teams build code pipelines based on names designers choose in Figma. If a designer renames a variable, the entire code pipeline breaks. AI cannot tell the difference between a visual value and a functional intent.
  • Missing context: A design file shows one state of one screen. It does not show error states, loading states, or how a database feeds the UI. That logic lives in the code, not the design file.

The industry is trying to fix this. Google open-sourced DESIGN.md to give AI more structure. Tools like Fixel help catch "design drift" by checking code against Figma during testing.

But even with these tools, a gap remains.

A design is not a foundation. It is a snapshot.

The real solution is not to turn designers into engineers. The solution is to empower the UX engineer to own the "middle."

The middle is the bridge where:

  • Design tokens map to universal standards.
  • AI proposes code based on existing systems.
  • Humans make the final architectural decisions.

AI is great at the snapshot level. It helps you finish projects faster. But real value requires a foundation.

Do not let the design drive the code without a human gatekeeper. The role of the engineer is changing. You are no longer just translating. You are managing the contract between vision and system.

How do you decide what stays in your hands and what you give to the AI?

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

Optional learning community: https://t.me/GyaanSetuAi