From a060115f62061039758dd3cadae97889c4eadb1b Mon Sep 17 00:00:00 2001
From: Paul Buetow <paul@buetow.org>
Date: Mon, 26 Aug 2024 23:07:43 +0300
Subject: Update content for html

---
 gemfeed/2008-06-26-perl-poetry.html                |   15 +-
 gemfeed/2010-04-09-standard-ml-and-haskell.html    |   11 +
 .../2010-05-09-the-fype-programming-language.html  |   39 +-
 .../2011-05-07-perl-daemon-service-framework.html  |    7 +-
 ...2-05-run-debian-on-your-phone-with-debroid.html |   26 +-
 ...04-09-jails-and-zfs-on-freebsd-with-puppet.html |    7 +-
 ...inning-up-my-own-authoritative-dns-servers.html |   13 +-
 ...alistic-load-testing-with-ioriot-for-linux.html |   39 +-
 ...-22-dtail-the-distributed-log-tail-program.html |   27 +-
 ...021-05-16-personal-bash-coding-style-guide.html |   11 +-
 ...5-gemtexter-one-bash-script-to-rule-it-all.html |   15 +-
 gemfeed/2021-07-04-the-well-grounded-rubyist.html  |   15 +
 ...-08-01-on-being-pedantic-about-open-source.html |   21 +-
 gemfeed/2021-09-12-keep-it-simple-and-stupid.html  |    7 +-
 gemfeed/2021-10-22-defensive-devops.html           |   31 +-
 gemfeed/2021-11-29-bash-golf-part-1.html           |   15 +-
 ...-12-26-how-to-stay-sane-as-a-devops-person.html |   29 +-
 gemfeed/2022-01-01-bash-golf-part-2.html           |   15 +-
 ...022-02-04-computer-operating-systems-i-use.html |    7 +-
 gemfeed/2022-03-06-the-release-of-dtail-4.0.0.html |   11 +-
 gemfeed/2022-04-10-creative-universe.html          |   44 +-
 .../2022-05-27-perl-is-still-a-great-choice.html   |   27 +-
 gemfeed/2022-06-15-sweating-the-small-stuff.html   |   42 +-
 ...22-07-30-lets-encrypt-with-openbsd-and-rex.html |    7 +-
 ...2-08-27-gemtexter-1.1.0-lets-gemtext-again.html |   15 +-
 gemfeed/2022-09-30-after-a-bad-nights-sleep.html   |   22 +-
 .../2022-10-30-installing-dtail-on-openbsd.html    |   27 +-
 ...-tried-emacs-but-i-switched-back-to-neovim.html |   36 +-
 ...22-12-24-ultrarelearning-java-my-takeaways.html |   20 +-
 gemfeed/2023-01-23-why-grapheneos-rox.html         |   37 +-
 .../2023-02-26-how-to-shut-down-after-work.html    |   14 +-
 ...03-25-gemtexter-2.0.0-lets-gemtext-again-2.html |   19 +-
 ...4-01-never-split-the-difference-book-notes.html |   16 +
 ...ithms-and-data-structures-in-golang-part-1.html |   15 +-
 gemfeed/2023-05-01-unveiling-guprecords            |    1 +
 ...3-05-06-the-obstacle-is-the-way-book-notes.html |   32 +-
 ...3-06-01-kiss-server-monitoring-with-gogios.html |   15 +-
 ...17-career-guide-and-soft-skills-book-notes.html |   55 +-
 ...07-21-gemtexter-2.1.0-lets-gemtext-again-3.html |   11 +-
 gemfeed/2023-09-25-dtail-usage-examples.html       |   34 +-
 ...static-web-photo-albums-with-photoalbum.sh.html |   15 +-
 gemfeed/2023-11-11-mind-management-book-notes.html |   32 +-
 gemfeed/2023-12-10-bash-golf-part-3.html           |   15 +-
 ...4-02-04-from-babylon5.buetow.org-to-.cloud.html |   18 +
 ...quickly-logging-ideas-programmed-in-golang.html |   16 +-
 ...-04-01-KISS-high-availability-with-OpenBSD.html |   19 +-
 .../2024-05-01-slow-productivity-book-notes.html   |   26 +-
 ...03-projects-i-currently-dont-have-time-for.html |    7 +-
 ...2024-06-23-terminal-multiplexing-with-tmux.html |   24 +-
 gemfeed/2024-07-05-random-weird-things.html        |   25 +-
 .../2024-07-07-the-stoic-challenge-book-notes.html |   20 +-
 .../2024-08-05-typing-127.1-words-per-minute.html  |   21 +-
 gemfeed/atom.xml                                   | 1010 +++++++++++---------
 index.html                                         |    2 +-
 notes/a-monks-guide-to-happiness.html              |   12 +
 notes/career-guide-and-soft-skills.html            |   55 +-
 notes/influence-wihout-authority.html              |   11 +
 notes/mind-management.html                         |   32 +-
 notes/never-split-the-difference.html              |   16 +
 notes/slow-productivity.html                       |   26 +-
 notes/the-obstacle-is-the-way.html                 |   32 +-
 notes/the-power-of-neuroplasticity.html            |   14 +
 notes/the-stoic-challenge.html                     |   20 +-
 uptime-stats.html                                  |    2 +-
 64 files changed, 1338 insertions(+), 982 deletions(-)

diff --git a/gemfeed/2008-06-26-perl-poetry.html b/gemfeed/2008-06-26-perl-poetry.html
index 035d8a2a..dd706435 100644
--- a/gemfeed/2008-06-26-perl-poetry.html
+++ b/gemfeed/2008-06-26-perl-poetry.html
@@ -12,6 +12,12 @@
 <br />
 <span class='quote'>Published at 2008-06-26T21:43:51+01:00; Updated at 2021-05-04</span><br />
 <br />
+<span>Here are some Perl Poems I wrote. They don&#39;t do anything useful when you run them, but they don&#39;t produce a compiler error either. They only exist for fun and demonstrate what you can do with Perl syntax.</span><br />
+<br />
+<span>Wikipedia: "Perl poetry is the practice of writing poems that can be compiled as legal Perl code, for example the piece known as Black Perl. Perl poetry is made possible by the large number of English words that are used in the Perl language. New poems are regularly submitted to the community at PerlMonks."</span><br />
+<br />
+<a class='textlink' href='https://en.wikipedia.org/wiki/Perl'>https://en.wikipedia.org/wiki/Perl</a><br />
+<br />
 <pre>
  &#39;\|/&#39;                                  *
 -- * -----
@@ -39,20 +45,11 @@ _~~|~/_|_|__/|~~~~~~~ |  / ~~~~~ |   | ~~~~~~~~
 <br />
 <ul>
 <li><a href='#perl-poetry'>Perl Poetry</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
 <li>⇢ <a href='#mathpl'>math.pl</a></li>
 <li>⇢ <a href='#christmaspl'>christmas.pl</a></li>
 <li>⇢ <a href='#shoppingpl'>shopping.pl</a></li>
 <li>⇢ <a href='#more'>More...</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>Here are some Perl Poems I wrote. They don&#39;t do anything useful when you run them, but they don&#39;t produce a compiler error either. They only exist for fun and demonstrate what you can do with Perl syntax.</span><br />
-<br />
-<span>Wikipedia: "Perl poetry is the practice of writing poems that can be compiled as legal Perl code, for example the piece known as Black Perl. Perl poetry is made possible by the large number of English words that are used in the Perl language. New poems are regularly submitted to the community at PerlMonks."</span><br />
-<br />
-<a class='textlink' href='https://en.wikipedia.org/wiki/Perl'>https://en.wikipedia.org/wiki/Perl</a><br />
-<br />
 <h2 style='display: inline' id='mathpl'>math.pl</h2><br />
 <br />
 <!-- Generator: GNU source-highlight 3.1.9
diff --git a/gemfeed/2010-04-09-standard-ml-and-haskell.html b/gemfeed/2010-04-09-standard-ml-and-haskell.html
index cfb3d39d..b6dd2301 100644
--- a/gemfeed/2010-04-09-standard-ml-and-haskell.html
+++ b/gemfeed/2010-04-09-standard-ml-and-haskell.html
@@ -18,6 +18,17 @@
 <br />
 <span>Haskell is also a "pure functional" programming language, whereas SML also makes explicit use of imperative concepts. I am by far not a specialist in either of these languages, but here are a few functions implemented in both SML and Haskell:</span><br />
 <br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
+<br />
+<ul>
+<li><a href='#standard-ml-and-haskell'>Standard ML and Haskell</a></li>
+<li>⇢ <a href='#defining-a-multi-data-type'>Defining a multi-data type</a></li>
+<li>⇢ <a href='#processing-a-multi'>Processing a multi</a></li>
+<li>⇢ <a href='#simplify-function'>Simplify function</a></li>
+<li>⇢ <a href='#delete-all'>Delete all</a></li>
+<li>⇢ <a href='#delete-one'>Delete one</a></li>
+<li>⇢ <a href='#higher-order-functions'>Higher-order functions</a></li>
+</ul><br />
 <h2 style='display: inline' id='defining-a-multi-data-type'>Defining a multi-data type</h2><br />
 <br />
 <span>Standard ML:</span><br />
diff --git a/gemfeed/2010-05-09-the-fype-programming-language.html b/gemfeed/2010-05-09-the-fype-programming-language.html
index 019bae8d..b3fb7a77 100644
--- a/gemfeed/2010-05-09-the-fype-programming-language.html
+++ b/gemfeed/2010-05-09-the-fype-programming-language.html
@@ -12,6 +12,12 @@
 <br />
 <span class='quote'>Published at 2010-05-09T12:48:29+01:00; Updated at 2021-05-05</span><br />
 <br />
+<span>Fype is an interpreted programming language created by me for learning and fun. The interpreter is written in C. It has been tested on FreeBSD and NetBSD and may also work on other Unix like operating systems such as Linux based ones. Besides learning and fun, there is no other use case of why Fype exists as many other programming languages are much faster and more powerful.</span><br />
+<br />
+<span>The Fype syntax is straightforward and uses a maximum look ahead of 1 and an effortless top-down parsing mechanism. Fype is parsing and interpreting its code simultaneously. This means that syntax errors are only detected during program runtime. </span><br />
+<br />
+<span>Fype is a recursive acronym and means "Fype is For Your Program Execution" or "Fype is Free Yak Programmed for ELF". You could also say, "It&#39;s not a hype - it&#39;s Fype!".</span><br />
+<br />
 <pre>
       ____                                      _        __       
      / / _|_   _ _ __   ___    _   _  ___  __ _| |__    / _|_   _ 
@@ -21,12 +27,35 @@
            |___/|_|            |___/                        |___/ 
 </pre>
 <br />
-<span>Fype is an interpreted programming language created by me for learning and fun. The interpreter is written in C. It has been tested on FreeBSD and NetBSD and may also work on other Unix like operating systems such as Linux based ones. Besides learning and fun, there is no other use case of why Fype exists as many other programming languages are much faster and more powerful.</span><br />
-<br />
-<span>The Fype syntax is straightforward and uses a maximum look ahead of 1 and an effortless top-down parsing mechanism. Fype is parsing and interpreting its code simultaneously. This means that syntax errors are only detected during program runtime. </span><br />
-<br />
-<span>Fype is a recursive acronym and means "Fype is For Your Program Execution" or "Fype is Free Yak Programmed for ELF". You could also say, "It&#39;s not a hype - it&#39;s Fype!".</span><br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
 <br />
+<ul>
+<li><a href='#the-fype-programming-language'>The Fype Programming Language</a></li>
+<li>⇢ <a href='#object-oriented-c-style'>Object-oriented C style</a></li>
+<li>⇢ <a href='#data-types'>Data types</a></li>
+<li>⇢ <a href='#syntax'>Syntax</a></li>
+<li>⇢ ⇢ <a href='#comments'>Comments</a></li>
+<li>⇢ ⇢ <a href='#variables'>Variables</a></li>
+<li>⇢ ⇢ <a href='#synonyms'>Synonyms</a></li>
+<li>⇢ <a href='#statements-and-expressions'>Statements and expressions</a></li>
+<li>⇢ ⇢ <a href='#parenthesis'>Parenthesis</a></li>
+<li>⇢ ⇢ <a href='#basic-expressions'>Basic expressions</a></li>
+<li>⇢ ⇢ <a href='#bitwise-expressions'>Bitwise expressions</a></li>
+<li>⇢ ⇢ <a href='#numeric-expressions'>Numeric expressions</a></li>
+<li>⇢ <a href='#control-statements'>Control statements</a></li>
+<li>⇢ <a href='#scopes'>Scopes</a></li>
+<li>⇢ <a href='#definedness-'>Definedness </a></li>
+<li>⇢ <a href='#system-'>System </a></li>
+<li>⇢ ⇢ <a href='#io-'>I/O </a></li>
+<li>⇢ <a href='#procedures-and-functions'>Procedures and functions</a></li>
+<li>⇢ ⇢ <a href='#procedures'>Procedures</a></li>
+<li>⇢ ⇢ <a href='#nested-procedures'>Nested procedures</a></li>
+<li>⇢ ⇢ <a href='#functions'>Functions</a></li>
+<li>⇢ ⇢ <a href='#nested-functions'>Nested functions</a></li>
+<li>⇢ <a href='#arrays'>Arrays</a></li>
+<li>⇢ <a href='#fancy-stuff'>Fancy stuff</a></li>
+<li>⇢ <a href='#may-the-source-be-with-you'>May the source be with you</a></li>
+</ul><br />
 <h2 style='display: inline' id='object-oriented-c-style'>Object-oriented C style</h2><br />
 <br />
 <span>The Fype interpreter is written in an object-oriented style of C. Each "main component" has its own .h and .c file. There is a struct type for each (most components at least) component, which can be initialized using a "COMPONENT_new" function and destroyed using a "COMPONENT_delete" function. Method calls follow the same schema, e.g. "COMPONENT_METHODNAME". There is no such as class inheritance and polymorphism involved. </span><br />
diff --git a/gemfeed/2011-05-07-perl-daemon-service-framework.html b/gemfeed/2011-05-07-perl-daemon-service-framework.html
index 869c5a8c..ac7615cf 100644
--- a/gemfeed/2011-05-07-perl-daemon-service-framework.html
+++ b/gemfeed/2011-05-07-perl-daemon-service-framework.html
@@ -12,6 +12,8 @@
 <br />
 <span class='quote'>Published at 2011-05-07T22:26:02+01:00; Updated at 2021-05-07</span><br />
 <br />
+<span>PerlDaemon is a minimal daemon for Linux and other Unix like operating systems programmed in Perl. It is a minimal but pretty functional and fairly generic service framework. This means that it does not do anything useful other than providing a framework for starting, stopping, configuring and logging. To do something useful, a module (written in Perl) must be provided.</span><br />
+<br />
 <pre>
    a&#39;!   _,,_ a&#39;!   _,,_     a&#39;!   _,,_
      \\_/    \  \\_/    \      \\_/    \.-,
@@ -23,7 +25,6 @@
 <br />
 <ul>
 <li><a href='#perl-daemon-service-framework'>Perl Daemon (Service Framework)</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
 <li>⇢ <a href='#features'>Features</a></li>
 <li>⇢ <a href='#quick-guide'>Quick Guide</a></li>
 <li>⇢ <a href='#how-to-configure'>How to configure</a></li>
@@ -34,10 +35,6 @@
 <li>⇢ ⇢ <a href='#your-own-module'>Your own module</a></li>
 <li>⇢ <a href='#may-the-source-be-with-you'>May the source be with you</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>PerlDaemon is a minimal daemon for Linux and other Unix like operating systems programmed in Perl. It is a minimal but pretty functional and fairly generic service framework. This means that it does not do anything useful other than providing a framework for starting, stopping, configuring and logging. To do something useful, a module (written in Perl) must be provided.</span><br />
-<br />
 <h2 style='display: inline' id='features'>Features</h2><br />
 <br />
 <span>PerlDaemon supports:</span><br />
diff --git a/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.html b/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.html
index 6a80b260..ca1ab4f3 100644
--- a/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.html
+++ b/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.html
@@ -12,6 +12,12 @@
 <br />
 <span class='quote'>Published at 2015-12-05T16:12:57+00:00; Updated at 2021-05-16</span><br />
 <br />
+<span>You can use the following tutorial to install a full-blown Debian GNU/Linux Chroot on an LG G3 D855 CyanogenMod 13 (Android 6). First of all, you need to have root permissions on your phone, and you also need to have the developer mode activated. The following steps have been tested on Linux (Fedora 23).</span><br />
+<br />
+<a href='./run-debian-on-your-phone-with-debroid/Deboroid.png'><img src='./run-debian-on-your-phone-with-debroid/Deboroid.png' /></a><br />
+<br />
+<span>A couple of years have passed since I last worked on Debroid. Currently, I am using the Termux app on Android, which is less sophisticated than a fully blown Debian installation but sufficient for my current requirements. The content of this site may be still relevant, and it would also work with more recent versions of Debian and Android. I would expect that some minor modifications need to be made, though. </span><br />
+<br />
 <pre>
  ____       _               _     _ 
 |  _ \  ___| |__  _ __ ___ (_) __| |
@@ -21,14 +27,18 @@
                                     
 </pre>
 <br />
-<span>You can use the following tutorial to install a full-blown Debian GNU/Linux Chroot on an LG G3 D855 CyanogenMod 13 (Android 6). First of all, you need to have root permissions on your phone, and you also need to have the developer mode activated. The following steps have been tested on Linux (Fedora 23).</span><br />
-<br />
-<a href='./run-debian-on-your-phone-with-debroid/Deboroid.png'><img src='./run-debian-on-your-phone-with-debroid/Deboroid.png' /></a><br />
-<br />
-<h2 style='display: inline' id='foreword'>Foreword</h2><br />
-<br />
-<span>A couple of years have passed since I last worked on Debroid. Currently, I am using the Termux app on Android, which is less sophisticated than a fully blown Debian installation but sufficient for my current requirements. The content of this site may be still relevant, and it would also work with more recent versions of Debian and Android. I would expect that some minor modifications need to be made, though. </span><br />
-<br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
+<br />
+<ul>
+<li><a href='#run-debian-on-your-phone-with-debroid'>Run Debian on your phone with Debroid</a></li>
+<li>⇢ <a href='#step-by-step-guide'>Step by step guide</a></li>
+<li>⇢ ⇢ <a href='#first-debootstrap-stage'>First debootstrap stage</a></li>
+<li>⇢ ⇢ <a href='#copy-debian-image-to-the-phone'>Copy Debian image to the phone</a></li>
+<li>⇢ ⇢ <a href='#second-debootstrap-stage'>Second debootstrap stage</a></li>
+<li>⇢ ⇢ <a href='#setup-of-various-scripts'>Setup of various scripts</a></li>
+<li>⇢ ⇢ <a href='#entering-debroid-and-enable-a-service'>Entering Debroid and enable a service</a></li>
+<li>⇢ ⇢ <a href='#include-to-android-startup'>Include to Android startup:</a></li>
+</ul><br />
 <h2 style='display: inline' id='step-by-step-guide'>Step by step guide</h2><br />
 <br />
 <span>All scripts mentioned here can be found on GitHub at:</span><br />
diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html
index 932fc897..42ed0847 100644
--- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html
+++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html
@@ -12,6 +12,8 @@
 <br />
 <span class='quote'>Published at 2016-04-09T18:29:47+01:00</span><br />
 <br />
+<span>Over the last couple of years I wrote quite a few Puppet modules in order to manage my personal server infrastructure. One of them manages FreeBSD Jails and another one ZFS file systems. I thought I would give a brief overview in how it looks and feels.</span><br />
+<br />
 <pre>
             __     __
            (( \---/ ))
@@ -36,16 +38,11 @@
 <br />
 <ul>
 <li><a href='#jails-and-zfs-with-puppet-on-freebsd'>Jails and ZFS with Puppet on FreeBSD</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
 <li>⇢ <a href='#zfs'>ZFS</a></li>
 <li>⇢ <a href='#jails'>Jails</a></li>
 <li>⇢ <a href='#inside-jail-puppet'>Inside-Jail Puppet</a></li>
 <li>⇢ <a href='#managing-multiple-jails'>Managing multiple Jails</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>Over the last couple of years I wrote quite a few Puppet modules in order to manage my personal server infrastructure. One of them manages FreeBSD Jails and another one ZFS file systems. I thought I would give a brief overview in how it looks and feels.</span><br />
-<br />
 <h2 style='display: inline' id='zfs'>ZFS</h2><br />
 <br />
 <span>The ZFS module is a pretty basic one. It does not manage ZFS pools yet as I am not creating them often enough which would justify implementing an automation. But let&#39;s see how we can create a ZFS file system (on an already given ZFS pool named ztank):</span><br />
diff --git a/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.html b/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.html
index 79a52f87..c60fb09c 100644
--- a/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.html
+++ b/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.html
@@ -12,12 +12,21 @@
 <br />
 <span class='quote'>Published at 2016-05-22T18:59:01+01:00</span><br />
 <br />
-<h2 style='display: inline' id='background'>Background</h2><br />
-<br />
 <span>Finally, I had time to deploy my authoritative DNS servers (master and slave) for my domains "buetow.org" and "buetow.zone". My domain name provider is Schlund Technologies. They allow their customers to edit the DNS records (BIND files) manually. And they also allow you to set your authoritative DNS servers for your domains. From now, I am making use of that option.</span><br />
 <br />
 <a class='textlink' href='http://www.schlundtech.de'>Schlund Technologies</a><br />
 <br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
+<br />
+<ul>
+<li><a href='#spinning-up-my-own-authoritative-dns-servers'>Spinning up my own authoritative DNS servers</a></li>
+<li>⇢ <a href='#all-freebsd-jails'>All FreeBSD Jails</a></li>
+<li>⇢ <a href='#pf-firewall'>PF firewall</a></li>
+<li>⇢ <a href='#puppet-managed-bind-zone-files'>Puppet managed BIND zone files</a></li>
+<li>⇢ <a href='#the-result'>The result</a></li>
+<li>⇢ <a href='#monitoring'>Monitoring</a></li>
+<li>⇢ <a href='#dns-update-workflow'>DNS update workflow</a></li>
+</ul><br />
 <h2 style='display: inline' id='all-freebsd-jails'>All FreeBSD Jails</h2><br />
 <br />
 <span>To set up my authoritative DNS servers, I installed a FreeBSD Jail dedicated for DNS with Puppet on my root machine as follows:</span><br />
diff --git a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.html b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.html
index 743cd5a6..6265b2f5 100644
--- a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.html
+++ b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.html
@@ -12,6 +12,16 @@
 <br />
 <span class='quote'>Published at 2018-06-01T14:50:29+01:00; Updated at 2021-05-08</span><br />
 <br />
+<span>This text first was published in the german IT-Administrator computer Magazine. 3 years have passed since and I decided to publish it on my blog too. </span><br />
+<br />
+<a class='textlink' href='https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot'>https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot</a><br />
+<br />
+<span>I havn&#39;t worked on I/O Riot for some time now, but all what is written here is still valid. I am still using I/O Riot to debug I/O issues and pattern once in a while, so by all means the tool is not obsolete yet. The tool even helped to resolve a major production incident at work caused by disk I/O.</span><br />
+<br />
+<span>I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of plain old Systemtap (or alternatively: Newer versions of Systemtap can also use BPF as the backend I have learned). Also, when I wrote I/O Riot initially, I didn&#39;t have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency.</span><br />
+<br />
+<span>Pleace notice that some of the screenshots show the command "ioreplay" instead of "ioriot". That&#39;s because the name has changed after taking those.</span><br />
+<br />
 <pre>
        .---.
       /     \
@@ -23,18 +33,23 @@
 jgs\__/&#39;---&#39;\__/
 </pre>
 <br />
-<h2 style='display: inline' id='foreword'>Foreword</h2><br />
-<br />
-<span>This text first was published in the german IT-Administrator computer Magazine. 3 years have passed since and I decided to publish it on my blog too. </span><br />
-<br />
-<a class='textlink' href='https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot'>https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot</a><br />
-<br />
-<span>I havn&#39;t worked on I/O Riot for some time now, but all what is written here is still valid. I am still using I/O Riot to debug I/O issues and pattern once in a while, so by all means the tool is not obsolete yet. The tool even helped to resolve a major production incident at work caused by disk I/O.</span><br />
-<br />
-<span>I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of plain old Systemtap (or alternatively: Newer versions of Systemtap can also use BPF as the backend I have learned). Also, when I wrote I/O Riot initially, I didn&#39;t have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency.</span><br />
-<br />
-<span>Pleace notice that some of the screenshots show the command "ioreplay" instead of "ioriot". That&#39;s because the name has changed after taking those.</span><br />
-<br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
+<br />
+<ul>
+<li><a href='#realistic-load-testing-with-io-riot-for-linux'>Realistic load testing with I/O Riot for Linux</a></li>
+<li><a href='#the-article'>The article</a></li>
+<li>⇢ <a href='#background-existing-techniques'>Background: Existing Techniques</a></li>
+<li>⇢ <a href='#benchmarking-the-email-cloud-at-mimecast'>Benchmarking the Email Cloud at Mimecast</a></li>
+<li>⇢ <a href='#using-io-riot'>Using I/O Riot</a></li>
+<li>⇢ ⇢ <a href='#installation'>Installation</a></li>
+<li>⇢ ⇢ <a href='#recording-of-io-events'>Recording of I/O events</a></li>
+<li>⇢ ⇢ <a href='#test-preparation'>Test preparation</a></li>
+<li>⇢ ⇢ <a href='#test-initialization'>Test Initialization</a></li>
+<li>⇢ ⇢ <a href='#replay'>Replay</a></li>
+<li>⇢ <a href='#io-riot-is-open-source'>I/O Riot is Open Source</a></li>
+<li>⇢ <a href='#systemtap'>Systemtap</a></li>
+<li>⇢ <a href='#more-refereces'>More refereces</a></li>
+</ul><br />
 <h1 style='display: inline' id='the-article'>The article</h1><br />
 <br />
 <span>With I/O Riot IT administrators can load test and optimize the I/O subsystem of Linux-based operating systems. The tool makes it possible to record I/O patterns and replay them at a later time as often as desired. This means bottlenecks can be reproduced and eradicated. </span><br />
diff --git a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.html b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.html
index fc51064a..df7e05e1 100644
--- a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.html
+++ b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.html
@@ -12,13 +12,24 @@
 <br />
 <span class='quote'>Published at 2021-04-22T19:28:41+01:00; Updated at 2021-04-26</span><br />
 <br />
+<span>This article first appeared at the Mimecast Engineering Blog but I made it available here in my personal internet site too.</span><br />
+<br />
+<a class='textlink' href='https://medium.com/mimecast-engineering/dtail-the-distributed-log-tail-program-79b8087904bb'>Original Mimecast Engineering Blog post at Medium</a><br />
+<br />
+<span>Running a large cloud-based service requires monitoring the state of huge numbers of machines, a task for which many standard UNIX tools were not really designed. In this post, I will describe a simple program, DTail, that Mimecast has built and released as Open-Source, which enables us to monitor log files of many servers at once without the costly overhead of a full-blown log management system.</span><br />
+<br />
+<span>At Mimecast, we run over 10 thousand server boxes. Most of them host multiple microservices and each of them produces log files. Even with the use of time series databases and monitoring systems, raw application logs are still an important source of information when it comes to analysing, debugging, and troubleshooting services.</span><br />
+<br />
+<span>Every engineer familiar with UNIX or a UNIX-like platform (e.g., Linux) is well aware of tail, a command-line program for displaying a text file content on the terminal which is also especially useful for following application or system log files with tail -f logfile.</span><br />
+<br />
+<span>Think of DTail as a distributed version of the tail program which is very useful when you have a distributed application running on many servers. DTail is an Open-Source, cross-platform, fairly easy to use, support and maintain log file analysis &amp; statistics gathering tool designed for Engineers and Systems Administrators. It is programmed in Google Go.</span><br />
+<br />
 <a href='./dtail-the-distributed-log-tail-program/title.png'><img alt='DTail logo image' title='DTail logo image' src='./dtail-the-distributed-log-tail-program/title.png' /></a><br />
 <br />
 <h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
 <br />
 <ul>
 <li><a href='#dtail---the-distributed-log-tail-program'>DTail - The distributed log tail program</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
 <li>⇢ <a href='#a-mimecast-pet-project'>A Mimecast Pet Project</a></li>
 <li>⇢ <a href='#differentiating-from-log-management-systems'>Differentiating from log management systems</a></li>
 <li>⇢ <a href='#combining-simplicity-security-and-efficiency'>Combining simplicity, security and efficiency</a></li>
@@ -29,20 +40,6 @@
 <li>⇢ <a href='#for-the-future'>For the future</a></li>
 <li>⇢ <a href='#open-source'>Open Source</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>This article first appeared at the Mimecast Engineering Blog but I made it available here in my personal internet site too.</span><br />
-<br />
-<a class='textlink' href='https://medium.com/mimecast-engineering/dtail-the-distributed-log-tail-program-79b8087904bb'>Original Mimecast Engineering Blog post at Medium</a><br />
-<br />
-<span>Running a large cloud-based service requires monitoring the state of huge numbers of machines, a task for which many standard UNIX tools were not really designed. In this post, I will describe a simple program, DTail, that Mimecast has built and released as Open-Source, which enables us to monitor log files of many servers at once without the costly overhead of a full-blown log management system.</span><br />
-<br />
-<span>At Mimecast, we run over 10 thousand server boxes. Most of them host multiple microservices and each of them produces log files. Even with the use of time series databases and monitoring systems, raw application logs are still an important source of information when it comes to analysing, debugging, and troubleshooting services.</span><br />
-<br />
-<span>Every engineer familiar with UNIX or a UNIX-like platform (e.g., Linux) is well aware of tail, a command-line program for displaying a text file content on the terminal which is also especially useful for following application or system log files with tail -f logfile.</span><br />
-<br />
-<span>Think of DTail as a distributed version of the tail program which is very useful when you have a distributed application running on many servers. DTail is an Open-Source, cross-platform, fairly easy to use, support and maintain log file analysis &amp; statistics gathering tool designed for Engineers and Systems Administrators. It is programmed in Google Go.</span><br />
-<br />
 <h2 style='display: inline' id='a-mimecast-pet-project'>A Mimecast Pet Project</h2><br />
 <br />
 <span>DTail got its inspiration from public domain tools available already in this area but it is a blue sky from-scratch development which was first presented at Mimecast’s annual internal Pet Project competition (awarded with a Bronze prize). It has gained popularity since and is one of the most widely deployed DevOps tools at Mimecast (reaching nearly 10k server installations) and many engineers use it on a regular basis. The Open-Source version of DTail is available at:</span><br />
diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.html b/gemfeed/2021-05-16-personal-bash-coding-style-guide.html
index d9eddf4e..b9d1b46c 100644
--- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.html
+++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.html
@@ -12,6 +12,10 @@
 <br />
 <span class='quote'>Published at 2021-05-16T14:51:57+01:00</span><br />
 <br />
+<span>Lately, I have been polishing and writing a lot of Bash code. Not that I never wrote a lot of Bash, but now as I also looked through the Google Shell Style Guide, I thought it is time also to write my thoughts on that. I agree with that guide in most, but not in all points. </span><br />
+<br />
+<a class='textlink' href='https://google.github.io/styleguide/shellguide.html'>Google Shell Style Guide</a><br />
+<br />
 <pre>
    .---------------------------.
   /,--..---..---..---..---..--. `.
@@ -29,7 +33,6 @@
 <br />
 <ul>
 <li><a href='#personal-bash-coding-style-guide'>Personal Bash coding style guide</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
 <li>⇢ <a href='#my-modifications'>My modifications</a></li>
 <li>⇢ ⇢ <a href='#shebang'>Shebang</a></li>
 <li>⇢ ⇢ <a href='#two-space-soft-tabs-indentation'>Two space soft-tabs indentation</a></li>
@@ -48,12 +51,6 @@
 <li>⇢ <a href='#use-common-sense-and-be-consistent'>Use common sense and BE CONSISTENT.</a></li>
 <li>⇢ <a href='#advanced-bash-learning-pro-tip'>Advanced Bash learning pro tip</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>Lately, I have been polishing and writing a lot of Bash code. Not that I never wrote a lot of Bash, but now as I also looked through the Google Shell Style Guide, I thought it is time also to write my thoughts on that. I agree with that guide in most, but not in all points. </span><br />
-<br />
-<a class='textlink' href='https://google.github.io/styleguide/shellguide.html'>Google Shell Style Guide</a><br />
-<br />
 <h2 style='display: inline' id='my-modifications'>My modifications</h2><br />
 <br />
 <span>These are my modifications to the Google Guide.</span><br />
diff --git a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.html b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.html
index c242897b..6870aa14 100644
--- a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.html
+++ b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.html
@@ -12,6 +12,10 @@
 <br />
 <span class='quote'>Published at 2021-06-05T19:03:32+01:00</span><br />
 <br />
+<span>You might have read my previous blog posts about entering the Geminispace, where I pointed out the benefits of having and maintaining an internet presence there. This whole site (the blog and all other pages) is composed in the Gemtext markup language.</span><br />
+<br />
+<span>This comes with the benefit that I can write content in my favourite text editor (Vim). </span><br />
+<br />
 <pre>
                                                                o .,&lt;&gt;., o
                                                                |\/\/\/\/|
@@ -57,8 +61,7 @@
 <br />
 <ul>
 <li><a href='#gemtexter---one-bash-script-to-rule-it-all'>Gemtexter - One Bash script to rule it all</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
-<li>⇢ ⇢ <a href='#motivation'>Motivation</a></li>
+<li>⇢ <a href='#motivation'>Motivation</a></li>
 <li>⇢ <a href='#output-formats'>Output formats</a></li>
 <li>⇢ <a href='#taking-it-as-far-as-i-should-but-no-farther'>Taking it as far as I should, but no farther</a></li>
 <li>⇢ ⇢ <a href='#modularization-'>Modularization </a></li>
@@ -71,13 +74,7 @@
 <li>⇢ <a href='#future-features'>Future features</a></li>
 <li>⇢ <a href='#conclusion'>Conclusion</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>You might have read my previous blog posts about entering the Geminispace, where I pointed out the benefits of having and maintaining an internet presence there. This whole site (the blog and all other pages) is composed in the Gemtext markup language.</span><br />
-<br />
-<span>This comes with the benefit that I can write content in my favourite text editor (Vim). </span><br />
-<br />
-<h3 style='display: inline' id='motivation'>Motivation</h3><br />
+<h2 style='display: inline' id='motivation'>Motivation</h2><br />
 <br />
 <span>Another benefit of using Gemini is that the Gemtext markup language is easy to parse. As my site is dual-hosted (Gemini+HTTP), I could, in theory, just write a shell script to deal with the conversion from Gemtext to HTML; there is no need for a full-featured programming language here. I have done a lot of Bash in the past, but I am also often revisiting old tools and techniques for refreshing and keeping the knowledge up to date here.</span><br />
 <br />
diff --git a/gemfeed/2021-07-04-the-well-grounded-rubyist.html b/gemfeed/2021-07-04-the-well-grounded-rubyist.html
index 9fb36fef..93d48859 100644
--- a/gemfeed/2021-07-04-the-well-grounded-rubyist.html
+++ b/gemfeed/2021-07-04-the-well-grounded-rubyist.html
@@ -24,6 +24,21 @@
 <br />
 <span>Yukihiro Matsumoto, the inventor of Ruby, said: "I wanted a scripting language that was more powerful than Perl and more object-oriented than Python" - So I can see where some of the similarities come from. I personally don&#39;t believe that Ruby is more powerful than Perl, though, especially when you take CPAN and/or Perl 6 (now known as Raku) into the equation. Well, it all depends on what you mean with "more powerful". But I want to stay pragmatic and use what&#39;s already used at my workplace.</span><br />
 <br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
+<br />
+<ul>
+<li><a href='#the-well-grounded-rubyist'>The Well-Grounded Rubyist</a></li>
+<li>⇢ <a href='#my-ruby-problem-domain'>My Ruby problem domain</a></li>
+<li>⇢ <a href='#being-stuck-in-ruby-mediocrity'>Being stuck in Ruby-mediocrity</a></li>
+<li>⇢ <a href='#o-reilly-safari-books-online'>O&#39;Reilly Safari Books Online</a></li>
+<li>⇢ <a href='#key-takeaways'>Key takeaways</a></li>
+<li>⇢ ⇢ <a href='#everything-is-an-object'>"Everything" is an object</a></li>
+<li>⇢ ⇢ <a href='#normal-objects-and-singleton-objects'>"Normal" objects and singleton objects</a></li>
+<li>⇢ ⇢ <a href='#domain-specific-languages'>Domain specific languages</a></li>
+<li>⇢ ⇢ <a href='#ruby-is-self-ish'>Ruby is "self-ish"</a></li>
+<li>⇢ ⇢ <a href='#functional-programming'>Functional programming</a></li>
+<li>⇢ <a href='#perl'>Perl</a></li>
+</ul><br />
 <h2 style='display: inline' id='my-ruby-problem-domain'>My Ruby problem domain</h2><br />
 <br />
 <span>I wrote a lot of Ruby code over the last couple of years. There were many small to medium-sized tools and other projects such as Nagios monitoring checks, even an internal monitoring &amp; reporting site based on Sinatra. All Ruby scripts I wrote do their work well; I didn&#39;t encounter any significant problems using Ruby for any of these tasks. Of course, there&#39;s nothing that couldn&#39;t be written in Perl (or Python), though, after all, these languages are all Turing-complete and all these languages also come with a huge set of 3rd party libraries :-).</span><br />
diff --git a/gemfeed/2021-08-01-on-being-pedantic-about-open-source.html b/gemfeed/2021-08-01-on-being-pedantic-about-open-source.html
index 87e281f4..3541472b 100644
--- a/gemfeed/2021-08-01-on-being-pedantic-about-open-source.html
+++ b/gemfeed/2021-08-01-on-being-pedantic-about-open-source.html
@@ -12,6 +12,8 @@
 <br />
 <span class='quote'>Published at 2021-08-01T10:37:58+03:00; Updated at 2023-01-23</span><br />
 <br />
+<span>I believe that it is essential to always have free and open-source alternatives to any kind of closed-source proprietary software available to choose from. But there are a couple of points you need to take into consideration. </span><br />
+<br />
 <pre>
                                            __
                                _____....--&#39; .&#39;
@@ -24,8 +26,25 @@
 &#39;^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^&#39; LGB - Art by lgbearrd
 </pre>
 <br />
-<span>I believe that it is essential to always have free and open-source alternatives to any kind of closed-source proprietary software available to choose from. But there are a couple of points you need to take into consideration. </span><br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
 <br />
+<ul>
+<li><a href='#on-being-pedantic-about-open-source'>On being Pedantic about Open-Source</a></li>
+<li>⇢ <a href='#the-costs-of-open-source'>The costs of open-source</a></li>
+<li>⇢ <a href='#commercial-providers'>Commercial providers</a></li>
+<li>⇢ <a href='#earning-on-open-source'>Earning on open-source</a></li>
+<li>⇢ <a href='#open-source-organizations-and-individual-contributors'>Open-source organizations and individual contributors</a></li>
+<li>⇢ <a href='#lesser-known-projects-and-the-charm-of-clunkiness'>Lesser known projects and the charm of clunkiness</a></li>
+<li>⇢ <a href='#the-security-aspect'>The security aspect</a></li>
+<li>⇢ <a href='#always-watch-out-for-open-source-alternatives'>Always watch out for open-source alternatives</a></li>
+<li>⇢ <a href='#what-about-mobile'>What about mobile?</a></li>
+<li>⇢ <a href='#know-the-alternatives'>Know the alternatives</a></li>
+<li>⇢ <a href='#you-can-t-control-it-all'>You can&#39;t control it all</a></li>
+<li>⇢ <a href='#the-middle-way'>The middle way</a></li>
+<li>⇢ <a href='#the-downside-of-being-a-nobody'>The downside of being a nobody</a></li>
+<li>⇢ <a href='#mobile-open-source-oses-are-still-evolving'>Mobile open-source OSes are still evolving</a></li>
+<li>⇢ <a href='#conclusion'>Conclusion</a></li>
+</ul><br />
 <h2 style='display: inline' id='the-costs-of-open-source'>The costs of open-source</h2><br />
 <br />
 <span>One benefit of using open-source software is that it doesn&#39;t cost anything, right? That&#39;s correct in many cases. However, in some cases you still need to spend a significant amount of time configuring the software to work for you. It will be more expensive to use open-source software than proprietary commercial one if you aren&#39;t careful. </span><br />
diff --git a/gemfeed/2021-09-12-keep-it-simple-and-stupid.html b/gemfeed/2021-09-12-keep-it-simple-and-stupid.html
index 615fff39..12797bdb 100644
--- a/gemfeed/2021-09-12-keep-it-simple-and-stupid.html
+++ b/gemfeed/2021-09-12-keep-it-simple-and-stupid.html
@@ -12,6 +12,8 @@
 <br />
 <span class='quote'>Published at 2021-09-12T09:39:20+03:00; Updated at 2023-03-23</span><br />
 <br />
+<span>A robust computer system must be kept simple and stupid (KISS). The fancier the system is, the more can break. Unfortunately, most systems tend to become complex and challenging to maintain in today&#39;s world. In the early days, so I was told, engineers understood every part of the system, but nowadays, we see more of the "lasagna" stack. One layer or framework is built on top of another layer, and in the end, nobody has got a clue what&#39;s going on.</span><br />
+<br />
 <pre>
   _______________                        |*\_/*|_______
   |  ___________  |     .-.     .-.      ||_/-\_|______  |
@@ -31,7 +33,6 @@
 <br />
 <ul>
 <li><a href='#keep-it-simple-and-stupid'>Keep it simple and stupid</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
 <li>⇢ <a href='#need-faster-hardware'>Need faster hardware</a></li>
 <li>⇢ <a href='#too-complex-to-be-replaced'>Too complex to be replaced</a></li>
 <li>⇢ ⇢ <a href='#on-cobol'>On COBOL</a></li>
@@ -46,10 +47,6 @@
 <li>⇢ <a href='#when-kiss-is-not-kiss-anymore'>When KISS is not KISS anymore</a></li>
 <li>⇢ <a href='#other-relevant-readings'>Other relevant readings</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>A robust computer system must be kept simple and stupid (KISS). The fancier the system is, the more can break. Unfortunately, most systems tend to become complex and challenging to maintain in today&#39;s world. In the early days, so I was told, engineers understood every part of the system, but nowadays, we see more of the "lasagna" stack. One layer or framework is built on top of another layer, and in the end, nobody has got a clue what&#39;s going on.</span><br />
-<br />
 <h2 style='display: inline' id='need-faster-hardware'>Need faster hardware</h2><br />
 <br />
 <span>This not just makes the system much more complex, difficult to maintain and challenging to troubleshoot, but also slow. So more experts are needed to support it. Also, newer and faster hardware is required to make it run smoothly. Often, it&#39;s so much easier to buy speedier hardware than rewrite a whole system from scratch from the bottom-up. The latter would require much more resources in the short run, but in the long run, it should pay off. Unfortunately, many project owners scare away from it as they only want to get their project done and then move on.</span><br />
diff --git a/gemfeed/2021-10-22-defensive-devops.html b/gemfeed/2021-10-22-defensive-devops.html
index f81976d8..fa66c14d 100644
--- a/gemfeed/2021-10-22-defensive-devops.html
+++ b/gemfeed/2021-10-22-defensive-devops.html
@@ -12,6 +12,16 @@
 <br />
 <span class='quote'>Published at 2021-10-22T10:02:46+03:00</span><br />
 <br />
+<span>I have seen many different setups and infrastructures during my carreer. My roles always included front-line ad-hoc fire fighting production issues. This often involves identifying and fixing these under time pressure, without the comfort of 2-week-long SCRUM sprints and without an exhaustive QA process. I also wrote a lot of code (Bash, Ruby, Perl, Go, and a little Java), and I followed the typical software development process, but that did not always apply to critical production issues.</span><br />
+<br />
+<span>Unfortunately, no system is 100% reliable, and you can never be prepared for a subset of the possible problem-space. IT infrastructures can be complex. Not even mentioning Kubernetes yet, a Microservice-based infrastructure can complicate things even further. You can take care of 99% of all potential problems by following all DevOps best practices. Those best practices are not the subject of this blog post; this post is about the sub 1% of the issues arising from nowhere you can&#39;t be prepared for. </span><br />
+<br />
+<span>Is there a software bug in a production, even though the software passed QA (after all, it is challenging to reproduce production behaviour in an artificial testing environment) and the software didn&#39;t show any issues running in production until a special case came up just now after it got deployed to production a week ago? Are there multiple hardware failure happening which causes loss of service redundancy or data inaccessibility? Is the automation of external customers connected to our infrastructure putting unexpectedly extra pressure on your grid, driving higher latencies and putting the SLAs at risk? You bet the solution is: Sysadmins, SREs and DevOps Engineers to the rescue. </span><br />
+<br />
+<span>You agree that fixing production issues this way is not proactive but rather reactive. I prefer to call it defensive, though, as you "defend" your system against a production issue. But, at the same time, you have to take a cautious (defensive) approach to fix it, as you don&#39;t want to make things worse. </span><br />
+<br />
+<span>Over time, I have compiled a list of fire-fighting automation strategies, which I would like to share here. </span><br />
+<br />
 <pre>
                                                             c=====e
                                                                H
@@ -22,16 +32,19 @@
                            ASCII Art by Clyde Watson
 </pre>
 <br />
-<span>I have seen many different setups and infrastructures during my carreer. My roles always included front-line ad-hoc fire fighting production issues. This often involves identifying and fixing these under time pressure, without the comfort of 2-week-long SCRUM sprints and without an exhaustive QA process. I also wrote a lot of code (Bash, Ruby, Perl, Go, and a little Java), and I followed the typical software development process, but that did not always apply to critical production issues.</span><br />
-<br />
-<span>Unfortunately, no system is 100% reliable, and you can never be prepared for a subset of the possible problem-space. IT infrastructures can be complex. Not even mentioning Kubernetes yet, a Microservice-based infrastructure can complicate things even further. You can take care of 99% of all potential problems by following all DevOps best practices. Those best practices are not the subject of this blog post; this post is about the sub 1% of the issues arising from nowhere you can&#39;t be prepared for. </span><br />
-<br />
-<span>Is there a software bug in a production, even though the software passed QA (after all, it is challenging to reproduce production behaviour in an artificial testing environment) and the software didn&#39;t show any issues running in production until a special case came up just now after it got deployed to production a week ago? Are there multiple hardware failure happening which causes loss of service redundancy or data inaccessibility? Is the automation of external customers connected to our infrastructure putting unexpectedly extra pressure on your grid, driving higher latencies and putting the SLAs at risk? You bet the solution is: Sysadmins, SREs and DevOps Engineers to the rescue. </span><br />
-<br />
-<span>You agree that fixing production issues this way is not proactive but rather reactive. I prefer to call it defensive, though, as you "defend" your system against a production issue. But, at the same time, you have to take a cautious (defensive) approach to fix it, as you don&#39;t want to make things worse. </span><br />
-<br />
-<span>Over time, I have compiled a list of fire-fighting automation strategies, which I would like to share here. </span><br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
 <br />
+<ul>
+<li><a href='#defensive-devops'>Defensive DevOps</a></li>
+<li>⇢ <a href='#meet-defensive-devops'>Meet Defensive DevOps</a></li>
+<li>⇢ <a href='#don-t-fully-automate-from-the-beginning'>Don&#39;t fully automate from the beginning</a></li>
+<li>⇢ <a href='#develop-code-directly-on-production-systems'>Develop code directly on production systems</a></li>
+<li>⇢ ⇢ <a href='#don-t-make-it-worse'>Don&#39;t make it worse</a></li>
+<li>⇢ <a href='#test-your-code'>Test your code</a></li>
+<li>⇢ <a href='#automation'>Automation</a></li>
+<li>⇢ <a href='#out-of-office-hours'>Out of office hours</a></li>
+<li>⇢ <a href='#retrospective'>Retrospective</a></li>
+</ul><br />
 <h2 style='display: inline' id='meet-defensive-devops'>Meet Defensive DevOps</h2><br />
 <br />
 <span>Defensive DevOps is a term I invented by myself. I define it this way:</span><br />
diff --git a/gemfeed/2021-11-29-bash-golf-part-1.html b/gemfeed/2021-11-29-bash-golf-part-1.html
index f68f9975..658a8584 100644
--- a/gemfeed/2021-11-29-bash-golf-part-1.html
+++ b/gemfeed/2021-11-29-bash-golf-part-1.html
@@ -12,6 +12,12 @@
 <br />
 <span class='quote'>Published at 2021-11-29T14:06:14+00:00; Updated at 2022-01-05</span><br />
 <br />
+<span>This is the first blog post about my Bash Golf series. This series is about random Bash tips, tricks and weirdnesses I came across. It&#39;s a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content.</span><br />
+<br />
+<a class='textlink' href='./2021-11-29-bash-golf-part-1.html'>2021-11-29 Bash Golf Part 1 (You are currently reading this)</a><br />
+<a class='textlink' href='./2022-01-01-bash-golf-part-2.html'>2022-01-01 Bash Golf Part 2</a><br />
+<a class='textlink' href='./2023-12-10-bash-golf-part-3.html'>2023-12-10 Bash Golf Part 3</a><br />
+<br />
 <pre>
      &#39;\                   .  .                        |&gt;18&gt;&gt;
        \              .         &#39; .                   |
@@ -27,7 +33,6 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 <br />
 <ul>
 <li><a href='#bash-golf-part-1'>Bash Golf Part 1</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
 <li>⇢ <a href='#tcpip-networking'>TCP/IP networking</a></li>
 <li>⇢ <a href='#process-substitution'>Process substitution</a></li>
 <li>⇢ <a href='#grouping'>Grouping</a></li>
@@ -37,14 +42,6 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 <li>⇢ <a href='#-aka-the-null-command'>: aka the null command</a></li>
 <li>⇢ <a href='#no-floating-point-support'>(No) floating point support</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>This is the first blog post about my Bash Golf series. This series is about random Bash tips, tricks and weirdnesses I came across. It&#39;s a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content.</span><br />
-<br />
-<a class='textlink' href='./2021-11-29-bash-golf-part-1.html'>2021-11-29 Bash Golf Part 1 (You are currently reading this)</a><br />
-<a class='textlink' href='./2022-01-01-bash-golf-part-2.html'>2022-01-01 Bash Golf Part 2</a><br />
-<a class='textlink' href='./2023-12-10-bash-golf-part-3.html'>2023-12-10 Bash Golf Part 3</a><br />
-<br />
 <h2 style='display: inline' id='tcpip-networking'>TCP/IP networking</h2><br />
 <br />
 <span>You probably know the Netcat tool, which is a swiss army knife for TCP/IP networking on the command line. But did you know that the Bash natively supports TCP/IP networking?</span><br />
diff --git a/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html b/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html
index 03ce06d1..3e102bfe 100644
--- a/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html
+++ b/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.html
@@ -12,6 +12,12 @@
 <br />
 <span class='quote'>Published at 2021-12-26T12:02:02+00:00; Updated at 2022-01-12</span><br />
 <br />
+<span>Log4shell (CVE-2021-44228) made it clear, once again, that working in information technology is not an easy job (especially when you are a DevOps person). I thought it would be interesting to summarize a few techniques to help you to relax.</span><br />
+<br />
+<span>(PS: When I mean DevOps, I also mean Site Reliability Engineers and Sysadmins. I believe SRE, DevOps Engineer and Sysadmin are just synonym titles for the same job).</span><br />
+<br />
+<a class='textlink' href='https://en.wikipedia.org/wiki/Log4Shell'>https://en.wikipedia.org/wiki/Log4Shell</a><br />
+<br />
 <pre>
                                      )
                              )      ((     (
@@ -34,12 +40,25 @@
   ~~~~~&#39;
 </pre>
 <br />
-<span>Log4shell (CVE-2021-44228) made it clear, once again, that working in information technology is not an easy job (especially when you are a DevOps person). I thought it would be interesting to summarize a few techniques to help you to relax.</span><br />
-<br />
-<span>(PS: When I mean DevOps, I also mean Site Reliability Engineers and Sysadmins. I believe SRE, DevOps Engineer and Sysadmin are just synonym titles for the same job).</span><br />
-<br />
-<a class='textlink' href='https://en.wikipedia.org/wiki/Log4Shell'>https://en.wikipedia.org/wiki/Log4Shell</a><br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
 <br />
+<ul>
+<li><a href='#how-to-stay-sane-as-a-devops-person-'>How to stay sane as a DevOps person </a></li>
+<li>⇢ <a href='#set-clear-expectations'>Set clear expectations</a></li>
+<li>⇢ <a href='#always-respond-to-requests-but-set-expectations-and-boundaries'>Always respond to requests but set expectations and boundaries</a></li>
+<li>⇢ ⇢ <a href='#dealing-with-requests'>Dealing with requests</a></li>
+<li>⇢ ⇢ <a href='#escalation-is-only-a-tool'>Escalation is only a tool</a></li>
+<li>⇢ <a href='#think-positively'>Think positively</a></li>
+<li>⇢ <a href='#go-slower-even-if-you-could-go-faster'>Go slower even if you could go faster</a></li>
+<li>⇢ ⇢ <a href='#you-work-in-a-team'>You work in a team</a></li>
+<li>⇢ ⇢ <a href='#don-t-rush'>Don&#39;t rush</a></li>
+<li>⇢ <a href='#you-are-not-a-superhero'>You are not a superhero</a></li>
+<li>⇢ ⇢ <a href='#give-away-some-of-your-superpowers'>Give away some of your superpowers</a></li>
+<li>⇢ <a href='#don-t-jump-on-all-problems-immediately'>Don&#39;t jump on all problems immediately</a></li>
+<li>⇢ <a href='#force-breaks-and-shutdown-now'>Force breaks; and shutdown now</a></li>
+<li>⇢ <a href='#block-time-every-day-for-personal-advance'>Block time every day for personal advance</a></li>
+<li>⇢ <a href='#more'>More</a></li>
+</ul><br />
 <h2 style='display: inline' id='set-clear-expectations'>Set clear expectations</h2><br />
 <br />
 <span>It&#39;s important to set clear expectations. It can be difficult to guess what others expect or don&#39;t expect from you. If you know exactly what you are supposed to do, you can work towards a specific goal and don&#39;t worry about all the other noise so much.</span><br />
diff --git a/gemfeed/2022-01-01-bash-golf-part-2.html b/gemfeed/2022-01-01-bash-golf-part-2.html
index d3054a89..a24819f4 100644
--- a/gemfeed/2022-01-01-bash-golf-part-2.html
+++ b/gemfeed/2022-01-01-bash-golf-part-2.html
@@ -12,6 +12,12 @@
 <br />
 <span class='quote'>Published at 2022-01-01T23:36:15+00:00; Updated at 2022-01-05</span><br />
 <br />
+<span>This is the second blog post about my Bash Golf series. This series is random Bash tips, tricks and weirdnesses I came across. It&#39;s a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content.</span><br />
+<br />
+<a class='textlink' href='./2021-11-29-bash-golf-part-1.html'>2021-11-29 Bash Golf Part 1</a><br />
+<a class='textlink' href='./2022-01-01-bash-golf-part-2.html'>2022-01-01 Bash Golf Part 2 (You are currently reading this)</a><br />
+<a class='textlink' href='./2023-12-10-bash-golf-part-3.html'>2023-12-10 Bash Golf Part 3</a><br />
+<br />
 <pre>
     &#39;\       &#39;\                   .  .                |&gt;18&gt;&gt;
       \        \              .         &#39; .           |
@@ -27,7 +33,6 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 <br />
 <ul>
 <li><a href='#bash-golf-part-2'>Bash Golf Part 2</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
 <li>⇢ <a href='#redirection'>Redirection</a></li>
 <li>⇢ <a href='#here'>HERE</a></li>
 <li>⇢ <a href='#random'>RANDOM</a></li>
@@ -36,14 +41,6 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 <li>⇢ ⇢ <a href='#-e'>-e</a></li>
 <li>⇢ ⇢ <a href='#pipefail'>pipefail</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>This is the second blog post about my Bash Golf series. This series is random Bash tips, tricks and weirdnesses I came across. It&#39;s a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content.</span><br />
-<br />
-<a class='textlink' href='./2021-11-29-bash-golf-part-1.html'>2021-11-29 Bash Golf Part 1</a><br />
-<a class='textlink' href='./2022-01-01-bash-golf-part-2.html'>2022-01-01 Bash Golf Part 2 (You are currently reading this)</a><br />
-<a class='textlink' href='./2023-12-10-bash-golf-part-3.html'>2023-12-10 Bash Golf Part 3</a><br />
-<br />
 <h2 style='display: inline' id='redirection'>Redirection</h2><br />
 <br />
 <span>Let&#39;s have a closer look at Bash redirection. As you might already know that there are 3 standard file descriptors:</span><br />
diff --git a/gemfeed/2022-02-04-computer-operating-systems-i-use.html b/gemfeed/2022-02-04-computer-operating-systems-i-use.html
index a4d7e8f2..0cf2ce27 100644
--- a/gemfeed/2022-02-04-computer-operating-systems-i-use.html
+++ b/gemfeed/2022-02-04-computer-operating-systems-i-use.html
@@ -12,6 +12,8 @@
 <br />
 <span class='quote'>Published at 2022-02-04T09:58:22+00:00; Updated at 2022-02-18</span><br />
 <br />
+<span>This is a list of Operating Systems I currently use. This list is in no particular order and also will be updated over time. The very first operating system I used was MS-DOS (mainly for games) and the very first Unix like operating system I used was SuSE Linux 5.3. My first smartphone OS was Symbian on a clunky Sony Ericsson device.</span><br />
+<br />
 <pre>
               /(        )`
               \ \___   / |
@@ -37,7 +39,6 @@
 <br />
 <ul>
 <li><a href='#computer-operating-systems-i-used'>Computer operating systems I use(d)</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
 <li>⇢ <a href='#fedora-linux'>Fedora Linux</a></li>
 <li>⇢ <a href='#endeavouros'>EndeavourOS</a></li>
 <li>⇢ <a href='#freebsd'>FreeBSD</a></li>
@@ -59,10 +60,6 @@
 <li>⇢ ⇢ <a href='#other-oses-i-only-had-a-glance-at'>Other OSes I only had a glance at...</a></li>
 <li>⇢ ⇢ <a href='#other-oses-which-seem-interesting'>Other OSes which seem interesting...</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>This is a list of Operating Systems I currently use. This list is in no particular order and also will be updated over time. The very first operating system I used was MS-DOS (mainly for games) and the very first Unix like operating system I used was SuSE Linux 5.3. My first smartphone OS was Symbian on a clunky Sony Ericsson device.</span><br />
-<br />
 <h2 style='display: inline' id='fedora-linux'>Fedora Linux</h2><br />
 <br />
 <span>Fedora Linux is the operating system I use on my primary (personal) laptop. It&#39;s a ThinkPad X1 Carbon Gen. 9. Lenovo which comes along with official Lenovo Linux support. I already noticed hardware firmware updates being installed directly through Fedora from Lenovo. Fedora is a real powerhouse, cutting-edge and reasonably stable at the same time. It&#39;s baked by Red Hat.</span><br />
diff --git a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.html b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.html
index da64c4bd..28186457 100644
--- a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.html
+++ b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.html
@@ -12,6 +12,10 @@
 <br />
 <span class='quote'>Published at 2022-03-06T18:11:39+00:00</span><br />
 <br />
+<span>I have recently released DTail 4.0.0 and this blog post goes through all the new goodies. If you want to jump directly to DTail, do it here (there are nice animated gifs which demonstrates the usage pretty well):</span><br />
+<br />
+<a class='textlink' href='https://dtail.dev'>https://dtail.dev</a><br />
+<br />
 <pre>
                               ,_---~~~~~----._
                         _,,_,*^____      _____``*g*\"*,
@@ -30,7 +34,6 @@
 <br />
 <ul>
 <li><a href='#the-release-of-dtail-400'>The release of DTail 4.0.0</a></li>
-<li>⇢ <a href='#introduction'>Introduction</a></li>
 <li>⇢ <a href='#so-what-s-new-in-400'>So, what&#39;s new in 4.0.0?</a></li>
 <li>⇢ ⇢ <a href='#rewritten-logging'>Rewritten logging</a></li>
 <li>⇢ ⇢ <a href='#configurable-terminal-color-codes'>Configurable terminal color codes</a></li>
@@ -45,12 +48,6 @@
 <li>⇢ ⇢ <a href='#use-of-memory-pools'>Use of memory pools</a></li>
 <li>⇢ <a href='#what-s-next'>What&#39;s next</a></li>
 </ul><br />
-<h2 style='display: inline' id='introduction'>Introduction</h2><br />
-<br />
-<span>I have recently released DTail 4.0.0 and this blog post goes through all the new goodies. If you want to jump directly to DTail, do it here (there are nice animated gifs which demonstrates the usage pretty well):</span><br />
-<br />
-<a class='textlink' href='https://dtail.dev'>https://dtail.dev</a><br />
-<br />
 <h2 style='display: inline' id='so-what-s-new-in-400'>So, what&#39;s new in 4.0.0?</h2><br />
 <br />
 <h3 style='display: inline' id='rewritten-logging'>Rewritten logging</h3><br />
diff --git a/gemfeed/2022-04-10-creative-universe.html b/gemfeed/2022-04-10-creative-universe.html
index 96fb8cfe..ba44133d 100644
--- a/gemfeed/2022-04-10-cr