Communicating with (out) code | olano.dev
This makes sense to me, but also makes me very sad inside. It wasn’t that long ago that “code is read more than written” was folk knowledge. Harold Abelson famously wrote that “Programs must be written for people to read, and only incidentally for machines to execute”, and Donald Knuth proposed to, “instead of instructing a computer what to do, rather explaining to human beings what we want a computer to do”. In this view, every one of the issues quoted above translates directly to programming: a social contract is broken when generating code takes less effort than reviewing it; there’s cognitive dissonance when code works but it’s not quite clear why or how; there’s something lost when the naming, commenting, and modularization were passively accepted instead of guided by intuitive expertise—something off when no mental model of another human is informing those decisions.
Vraiment bonne reflexion, ça me touche beaucoup car j’étais franchement de cet avis : le code doit être beau, lisible, bien organisé autant pour les autres devs que pour la machine. C’est beaucoup moins le cas dans mon quotidien et en lisant ces phrases je ressens une certaine tristesse. Cela dit, dans mon boulot actuel, peu de mon code était relu même avant les agents de code, et l’élégance de mon code n’était vraiment que pour mon propre plaisir. Dans d’autres boîtes, je sais que ça aurait été bien différent.
The thing is that by communicating with code we didn’t just produce working software: we were also building knowledge. Real-world software systems represent, even determine business processes and human interactions. The systems are often the best specification of those processes, a better source-of-truth than what documentation or any one expert can provide. Even in the most worse-is-better, get-the-job-done enterprise environments, code was the best means we programmers had to learn and communicate about the system—and, through it, the business. Making code self-explanatory and augmenting it with domain context is how we built a shared mental model of the problem we were trying to solve.
Le building knowledge reste au coeur de mon activité de développement, avec ou sans IA. L’avenir me dira si j’arrive à capitaliser autant dessus où si ça deviendra un vrai calvaire de retrouver quoi, comment et pourquoi. Pour moi mon boulot reste de comprendre et de savoir comment ça va se comporter.
The thing is that by communicating with code we didn’t just produce working software: we were also building knowledge. Real-world software systems represent, even determine business processes and human interactions. The systems are often the best specification of those processes, a better source-of-truth than what documentation or any one expert can provide. Even in the most worse-is-better, get-the-job-done enterprise environments, code was the best means we programmers had to learn and communicate about the system—and, through it, the business. Making code self-explanatory and augmenting it with domain context is how we built a shared mental model of the problem we were trying to solve.
Ce n’est pas du tout mon cas, et c’est un argumentaire que j’ai beaucoup de mal à contrer, car sur le papier oui, ça semble bien. Mais la vérité est bien différente. Sur le papier, le CRM vibe-codé par un commercial dans ma boîte était testé, full-green, audité dans tous les sens et à répétition. Mais ça n’empêche que maintenant, c’est de la merde.
Intentionally or not, teams adopting them turn their projects into code-only-for-machines.
Oui
I obviously prefer code-for-humans, but I have to admit its alleged superiority is founded on folklore and anecdotal evidence.
As long as it’s apparently more cost-effective, code-for-machines will prevail.
Dur à accepter.
Or maybe we can bring communication back, try to place it somewhere else in the process. Code was never a particularly good communication tool, anyway, just the best we had in the context of handcrafted software. Maybe we could step back, if only to recover some of that builder joy, to preserve some of the humanity, and ask ourselves: if not in the code, and not in the code generation process, where do people go in this brave new software development world?
Dans les specs ? J’ai passé pas mal de temps à créer des systèmes, les architecturer, les corriger, les adapter sans jamais écrire une ligne de code ou de configuration. Toutes les conversations avaient lieu autour de ces specs, elles étaient versionnées, liées, testées. Le boulot n’en était pas moins intéressant, en tout cas pour moi. Pour d’autres, sûrement plus techniciens, ce n’était pas du tout du travail intéressant.
Extraits cités issus de ce lien visité le , crédits : Facundo Olano