]> git.eshelyaron.com Git - esy-publish.git/commitdiff
* The Self-Healing Code Fallacy: fix quoting
authorEshel Yaron <me@eshelyaron.com>
Wed, 5 Apr 2023 11:17:06 +0000 (14:17 +0300)
committerEshel Yaron <me@eshelyaron.com>
Wed, 5 Apr 2023 11:17:06 +0000 (14:17 +0300)
src/posts/2023-04-05-the-self-healing-code-fallacy.org

index 05f7a5ac3e5a9f953d5c557bcf300163161c2f05..3afc1b4d4cd640c7514646cf1dd9c16f6b4b4d8f 100644 (file)
@@ -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