Essay

We Don't Need More Code. We Need Better Engines

Most engineers build solutions. A button. A modal. A form. Then they rebuild it again. We should build engines instead: systems that understand context, adapt to constraints, and evolve with the product.

I've been writing software for decades.

I've seen frameworks rise and fall, paradigms come and go, and teams rewrite the same problems over and over again, each time believing they're doing it better.

Most of the time, they aren't.

They're just reproducing the same patterns in slightly different shapes.

And now, with AI capable of writing code faster than any human, we're about to accelerate this problem dramatically.

Because if we don't change how we think about engineering, we're not going to build better systems.

We're just going to build bad systems faster.

The Problem Isn't Code

Code is no longer scarce.

Anyone can generate:

  • components
  • APIs
  • business logic
  • entire applications

But code was never the real problem.

The real problem has always been:

How do we build systems that survive 5, 10, 15 years without collapsing under their own weight?

The Industry Builds Solutions. We Should Build Engines

Most engineers build solutions.

A button. A modal. A form.

Then they rebuild it again. And again.

That's not engineering. That's repetition.

We should build engines instead.

Systems that:

  • understand context
  • adapt to constraints
  • evolve with the product
  • produce consistent outcomes

Think Like a Game Engine

What people love in games like Red Dead Redemption 2 is not handcrafted detail everywhere.

It's engines working together:

  • physics
  • animation
  • AI

That's what creates immersion.

We should build software the same way.

What This Means

Write once. Adapt everywhere.

A component should understand:

  • where it lives
  • how dense the UI is
  • accessibility needs
  • constraints

Not be hardcoded.

Interactive demo: the same component, rendered across three different surfaces. Switch between them to see how context changes rendering, without changing the component.

Interactive Demonstration
◈
Context Awarenessinline

A component that knows where it lives renders itself appropriately. Same code, different surface.

The same component, rendered across three different surfaces. Switch between them to see how context changes rendering, without changing the component.

Developer Experience Matters

Bad DX compounds over years.

Good systems:

  • reduce repetition
  • guide decisions
  • scale with teams

Interactive demo: density is a first-class design constraint. This article adapts in real time. Try it.

Interactive Demonstration

Reading density

Changes paragraph spacing, line height, and rhythm across the whole article.

Density is a first-class design constraint. This article adapts in real time. Try it.

AI Changes the Game

AI will write code.

We must design systems.

The future belongs to those who define intent, not just code.

Nubisco

I'm building Nubisco around one idea:

Fewer solutions. Better engines.

Final Thought

If AI writes code…

Then we must decide what should exist.

That is the real craft.

Fewer solutions. Better engines.