If regenerating code becomes trivial, what's scarce is knowing what to regenerate and how to verify it. This series turns the software DNA idea into a concrete discipline: what files to write, where the agent improvises when we stay silent, and why teams that only measure output will ship more code, faster, that's more fragile. Theses with code, code with theses.
2 articles in this series
If regenerating is cheaper than maintaining, the rational strategy isn't to care for the code. It's to make it disposable by design and invest in what isn't disposable. The future of the engineer is writing DNA, not code.
Three weeks ago I argued that code would become disposable and what would matter is software DNA. I locked myself in to test whether that idea was actually writable. What came out: 24 files, two regenerations at less than a euro each, a public repo, and a fair bit of clarity about what harness engineering still doesn't solve.
The series keeps growing. Subscribe to the newsletter so you don't miss the next installments.
Join other engineers who receive reflections on career, leadership, and technology every week.
This newsletter is written in Spanish.