Skip to content

Design Over Implementation

alex-krentsel's meta-observation after reading the openclaw source: "Code quality is dead." The OpenClaw implementation is, in his words, gross — "I would get fired for writing this kind of code at Google, it would never get merged in." And yet it works beautifully. The architecture, by contrast, is "actually quite nice." He concludes: implementation abstractions no longer matter; design abstractions matter more.

The claim

In a world where an LLM can author, refactor, and debug implementation at near-zero cost, the scarce resource is not careful code — it's correct decomposition:

  • What are the right layers?
  • What are the right boundaries between them?
  • What's the right abstraction for sessions, for memory, for time?

OpenClaw's three layers (connectors / gateway controller / agent runtime), its session-as-process abstraction (sessions-as-processes), and its time-control primitives (heartbeat-and-cron) are all good design decisions. The code inside each box is admittedly messy — but the boxes are right. Since LLMs can rewrite the code inside the boxes cheaply, only the boxes accrete value.

  • Peter Steinberger: "Taste is the new engineering moat" — see agent-taste. Design-over-implementation is the architectural sibling of taste-over-output.
  • Mitchell Hashimoto: the harness is the real artifact; the code is a byproduct.
  • Ryan Lopopolo: agent-legible-software — the humans' job is to design abstractions the agent can navigate; the agent writes the lines.
  • Brett Taylor (via Ryan): "Software dependencies are going away — they can just be vendored." Same compression: implementation is cheap, integration/design is not.

Counter-stress

Krentsel is clear this is not "throw out good code" — it's "don't confuse good code for good design." The evidence for OpenClaw's success comes despite its code quality, so code quality is not sufficient. But he doesn't claim code quality is harmful; he claims it's no longer the bottleneck. If the design is wrong, no amount of clean code saves you (and vice versa).

Implication for how to build

  • Spend human hours on the 3-layer picture, the abstractions, the naming.
  • Let the agent write the code. Accept that it will be ugly.
  • Pair this with harness-engineering — the harness is exactly where the good design lives.

Pairs with

Cross-references