From 22eb46d0f1c44ced2c1e481a680764b4fd7ff0a3 Mon Sep 17 00:00:00 2001 From: Eshel Yaron Date: Wed, 5 Apr 2023 14:17:06 +0300 Subject: [PATCH] * The Self-Healing Code Fallacy: fix quoting --- src/posts/2023-04-05-the-self-healing-code-fallacy.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/posts/2023-04-05-the-self-healing-code-fallacy.org b/src/posts/2023-04-05-the-self-healing-code-fallacy.org index 05f7a5a..3afc1b4 100644 --- a/src/posts/2023-04-05-the-self-healing-code-fallacy.org +++ b/src/posts/2023-04-05-the-self-healing-code-fallacy.org @@ -54,7 +54,7 @@ doesn't it? And fuck it, who's to say if it gets it wrong. Back to the self-healing code from Min Choi's tweet, the biggest problem I have with this idea is the premise that fixing code is somewhat similar to how living organisms heal. Healing is when your -body restores a "previous" good state after enduring some trauma. If +body restores a previous "good" state after enduring some trauma. If your code would self-heal whenever you broke it, that'd just mean it's reverting your changes time after time. You'd be stuck with a self-preserving, "Hello, World!"-printing, CI-passing piece of -- 2.39.2