From 465b646ef1d7677cf49cf62f578cc0f8c924e018 Mon Sep 17 00:00:00 2001
From: Paul Buetow <paul@buetow.org>
Date: Sat, 2 Oct 2021 21:57:26 +0300
Subject: Publishing new version

---
 gemfeed/atom.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'gemfeed/atom.xml')

diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index 3fe65114..e18e0cce 100644
--- a/gemfeed/atom.xml
+++ b/gemfeed/atom.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <feed xmlns="http://www.w3.org/2005/Atom">
-    <updated>2021-10-02T21:54:42+03:00</updated>
+    <updated>2021-10-02T21:57:11+03:00</updated>
     <title>buetow.org feed</title>
     <subtitle>Having fun with computers!</subtitle>
     <link href="gemini://buetow.org/gemfeed/atom.xml" rel="self" />
@@ -67,7 +67,7 @@
 <h2>KISS for programmers</h2>
 <p>Not to mention, keeping things simple and stupid also reduces the potential malicious attack surface. It's not just about the software and services you use and operate. It's also about the software you write. Here is a nice article about the KISS principle in software development:</p>
 <a class="textlink" href="https://thevaluable.dev/kiss-principle-explained/">https://thevaluable.dev/kiss-principle-explained/</a><br />
-<h1>Then KISS is not KISS anymore</h1>
+<h1>When KISS is not KISS anymore</h1>
 <p>There is, however, a trap. The more you spend time with things, the more these things feel natural to you and you become an expert. The more you become an expert, the more you introduce more abstractions and other clever ways of doing things. For you, things seem to be KISS still, but another person may not be an expert and might not understand what you do. One of the fundamental challenges is to keep things really KISS. You might add abstraction upon abstraction to a system and don't even notice it until it is too late.</p>
 <p>Enough ranted for now :-). E-Mail me your thoughts at comments@mx.buetow.org!</p>
             </div>
-- 
cgit v1.2.3