Update content for html

10 files changed, 842 insertions, 399 deletions

diff --git a/about/resources.html b/about/resources.html
index 988723e7..359669ca 100644
--- a/about/resources.html
+++ b/about/resources.html
@@ -50,107 +50,107 @@
 <span>In random order:</span><br />
 <br />
 <ul>
-<li>DevOps And Site Reliability Engineering Handbook; Stephen Fleming; Audible</li>
-<li>Site Reliability Engineering; How Google runs production systems; O&#39;Reilly</li>
-<li>Effective Java; Joshua Bloch; Addison-Wesley Professional</li>
-<li>Ultimate Go Notebook; Bill Kennedy</li>
+<li>Funktionale Programmierung; Peter Pepper; Springer</li>
+<li>Tmux 2: Productive Mouse-free Development; Brain P. Hogan; The Pragmatic Programmers </li>
+<li>Clusterbau mit Linux-HA; Michael Schwartzkopff; O&#39;Reilly</li>
+<li>Programming Ruby 3.3 (5th Edition); Noel Rappin, with Dave Thomas; The Pragmatic Bookshelf</li>
 <li>100 Go Mistakes and How to Avoid Them; Teiva Harsanyi; Manning Publications</li>
+<li>Raku Fundamentals; Moritz Lenz; Apress</li>
+<li>Developing Games in Java; David Brackeen and others...; New Riders</li>
+<li>Raku Recipes; J.J. Merelo; Apress</li>
+<li>DevOps And Site Reliability Engineering Handbook; Stephen Fleming; Audible</li>
+<li>Amazon Web Services in Action; Michael Wittig and Andreas Wittig; Manning Publications</li>
 <li>Distributed Systems: Principles and Paradigms; Andrew S. Tanenbaum; Pearson</li>
+<li>Hands-on Infrastructure Monitoring with Prometheus; Joel Bastos, Pedro Araujo; Packt </li>
+<li>Systems Performance Tuning; Gian-Paolo D. Musumeci and others...; O&#39;Reilly</li>
+<li>The KCNA (Kubernetes and Cloud Native Associate) Book; Nigel Poulton</li>
+<li>Ultimate Go Notebook; Bill Kennedy</li>
+<li>Effective Java; Joshua Bloch; Addison-Wesley Professional</li>
 <li>Modern Perl; Chromatic ; Onyx Neon Press</li>
-<li>Go Brain Teasers - Exercise Your Mind; Miki Tebeka; The Pragmatic Programmers</li>
-<li>Polished Ruby Programming; Jeremy Evans; Packt Publishing</li>
-<li>Amazon Web Services in Action; Michael Wittig and Andreas Wittig; Manning Publications</li>
-<li>Raku Fundamentals; Moritz Lenz; Apress</li>
-<li>The DevOps Handbook; Gene Kim, Jez Humble, Patrick Debois, John Willis; Audible</li>
-<li>The Go Programming Language; Alan A. A. Donovan; Addison-Wesley Professional</li>
-<li>The Pragmatic Programmer; David Thomas; Addison-Wesley</li>
-<li>Programming Ruby 3.3 (5th Edition); Noel Rappin, with Dave Thomas; The Pragmatic Bookshelf</li>
-<li>Higher Order Perl; Mark Dominus; Morgan Kaufmann</li>
-<li>Pro Puppet; James Turnbull, Jeffrey McCune; Apress</li>
 <li>Learn You Some Erlang for Great Good; Fred Herbert; No Starch Press</li>
 <li>Systemprogrammierung in Go; Frank Müller; dpunkt</li>
-<li>Concurrency in Go; Katherine Cox-Buday; O&#39;Reilly</li>
-<li>The Docker Book; James Turnbull; Kindle</li>
-<li>Object-Oriented Programming with ANSI-C; Axel-Tobias Schreiner</li>
-<li>The Kubernetes Book; Nigel Poulton; Unabridged Audiobook</li>
-<li>97 things every SRE should know; Emil Stolarsky, Jaime Woo; O&#39;Reilly</li>
-<li>Think Raku (aka Think Perl 6); Laurent Rosenfeld, Allen B. Downey; O&#39;Reilly</li>
-<li>Systems Performance Tuning; Gian-Paolo D. Musumeci and others...; O&#39;Reilly</li>
+<li>Terraform Cookbook; Mikael Krief; Packt Publishing</li>
 <li>Learn You a Haskell for Great Good!; Miran Lipovaca; No Starch Press</li>
-<li>Clusterbau mit Linux-HA; Michael Schwartzkopff; O&#39;Reilly</li>
+<li>Polished Ruby Programming; Jeremy Evans; Packt Publishing</li>
+<li>21st Century C: C Tips from the New School; Ben Klemens; O&#39;Reilly</li>
 <li>Data Science at the Command Line; Jeroen Janssens; O&#39;Reilly</li>
 <li>Effective awk programming; Arnold Robbins; O&#39;Reilly</li>
-<li>Java ist auch eine Insel; Christian Ullenboom; </li>
-<li>Tmux 2: Productive Mouse-free Development; Brain P. Hogan; The Pragmatic Programmers </li>
-<li>DNS and BIND; Cricket Liu; O&#39;Reilly</li>
-<li>Funktionale Programmierung; Peter Pepper; Springer</li>
+<li>C++ Programming Language; Bjarne Stroustrup;</li>
+<li>The DevOps Handbook; Gene Kim, Jez Humble, Patrick Debois, John Willis; Audible</li>
+<li>Object-Oriented Programming with ANSI-C; Axel-Tobias Schreiner</li>
+<li>Concurrency in Go; Katherine Cox-Buday; O&#39;Reilly</li>
 <li>Kubernetes Cookbook; Sameer Naik, Sébastien Goasguen, Jonathan Michaux; O&#39;Reilly</li>
-<li>Terraform Cookbook; Mikael Krief; Packt Publishing</li>
-<li>The Practise of System and Network Administration; Thomas A. Limoncelli, Christina J. Hogan, Strata R. Chalup; Addison-Wesley Professional Pro Git; Scott Chacon, Ben Straub; Apress</li>
-<li>21st Century C: C Tips from the New School; Ben Klemens; O&#39;Reilly</li>
+<li>Perl New Features; Joshua McAdams, brian d foy; Perl School</li>
+<li>Site Reliability Engineering; How Google runs production systems; O&#39;Reilly</li>
+<li>Think Raku (aka Think Perl 6); Laurent Rosenfeld, Allen B. Downey; O&#39;Reilly</li>
+<li>Go Brain Teasers - Exercise Your Mind; Miki Tebeka; The Pragmatic Programmers</li>
 <li>Leanring eBPF; Liz Rice; O&#39;Reilly</li>
-<li>Developing Games in Java; David Brackeen and others...; New Riders</li>
-<li>C++ Programming Language; Bjarne Stroustrup;</li>
+<li>The Practise of System and Network Administration; Thomas A. Limoncelli, Christina J. Hogan, Strata R. Chalup; Addison-Wesley Professional Pro Git; Scott Chacon, Ben Straub; Apress</li>
+<li>Java ist auch eine Insel; Christian Ullenboom; </li>
+<li>The Go Programming Language; Alan A. A. Donovan; Addison-Wesley Professional</li>
+<li>DNS and BIND; Cricket Liu; O&#39;Reilly</li>
+<li>97 things every SRE should know; Emil Stolarsky, Jaime Woo; O&#39;Reilly</li>
+<li>The Kubernetes Book; Nigel Poulton; Unabridged Audiobook</li>
+<li>The Docker Book; James Turnbull; Kindle</li>
 <li>Programming Perl aka "The Camel Book"; Tom Christiansen, brian d foy, Larry Wall &amp; Jon Orwant; O&#39;Reilly</li>
-<li>Raku Recipes; J.J. Merelo; Apress</li>
-<li>Perl New Features; Joshua McAdams, brian d foy; Perl School</li>
-<li>The KCNA (Kubernetes and Cloud Native Associate) Book; Nigel Poulton</li>
-<li>Hands-on Infrastructure Monitoring with Prometheus; Joel Bastos, Pedro Araujo; Packt </li>
+<li>Higher Order Perl; Mark Dominus; Morgan Kaufmann</li>
+<li>The Pragmatic Programmer; David Thomas; Addison-Wesley</li>
+<li>Pro Puppet; James Turnbull, Jeffrey McCune; Apress</li>
 </ul><br />
 <h2 style='display: inline' id='technical-references'>Technical references</h2><br />
 <br />
 <span>I didn&#39;t read them from the beginning to the end, but I am using them to look up things. The books are in random order:</span><br />
 <br />
 <ul>
-<li>Relayd and Httpd Mastery; Michael W Lucas</li>
+<li>The Linux Programming Interface; Michael Kerrisk; No Starch Press </li>
 <li>Go: Design Patterns for Real-World Projects; Mat Ryer; Packt</li>
 <li>Algorithms; Robert Sedgewick, Kevin Wayne; Addison Wesley</li>
+<li>Groovy Kurz &amp; Gut; Joerg Staudemeier; O&#39;Reilly</li>
+<li>Understanding the Linux Kernel; Daniel P. Bovet, Marco Cesati; O&#39;Reilly</li>
 <li>Implementing Service Level Objectives; Alex Hidalgo; O&#39;Reilly</li>
+<li>Relayd and Httpd Mastery; Michael W Lucas</li>
 <li>BPF Performance Tools - Linux System and Application Observability, Brendan Gregg; Addison Wesley</li>
-<li>The Linux Programming Interface; Michael Kerrisk; No Starch Press </li>
-<li>Understanding the Linux Kernel; Daniel P. Bovet, Marco Cesati; O&#39;Reilly</li>
-<li>Groovy Kurz &amp; Gut; Joerg Staudemeier; O&#39;Reilly</li>
 </ul><br />
 <h2 style='display: inline' id='self-development-and-soft-skills-books'>Self-development and soft-skills books</h2><br />
 <br />
 <span>In random order:</span><br />
 <br />
 <ul>
-<li>The Off Switch; Mark Cropley; Virgin Books (RE-READ 1ST TIME)</li>
+<li>Getting Things Done; David Allen</li>
+<li>Slow Productivity; Cal Newport; Penguin Random House</li>
+<li>The Phoenix Project - A Novel About IT, DevOps, and Helping your Business Win; Gene Kim and Kevin Behr; Trade Select</li>
+<li>Meditation for Mortals, Oliver Burkeman, Audiobook</li>
 <li>Atomic Habits; James Clear; Random House Business</li>
-<li>Stop starting, start finishing; Arne Roock; Lean-Kanban University  </li>
-<li>Never Split the Difference; Chris Voss, Tahl Raz; Random House Business</li>
-<li>Deep Work; Cal Newport; Piatkus</li>
-<li>Ultralearning; Scott Young; Thorsons</li>
-<li>The Good Enough Job; Simone Stolzoff; Ebury Edge</li>
+<li>Influence without Authority; A. Cohen, D. Bradford; Wiley</li>
+<li>The 7 Habits Of Highly Effective People; Stephen R. Covey; Simon &amp; Schuster UK</li>
+<li>So Good They Can&#39;t Ignore You; Cal Newport; Business Plus</li>
+<li>The Bullet Journal Method; Ryder Carroll; Fourth Estate</li>
+<li>Staff Engineer: Leadership beyond the management track; Will Larson; Audiobook</li>
 <li>Solve for Happy; Mo Gawdat (RE-READ 1ST TIME)</li>
-<li>The Phoenix Project - A Novel About IT, DevOps, and Helping your Business Win; Gene Kim and Kevin Behr; Trade Select</li>
+<li>Eat That Frog!; Brian Tracy; Hodder Paperbacks</li>
+<li>The Obstacle Is The Way; Ryan Holiday; Profile Books Ltd</li>
+<li>101 Essays that change the way you think; Brianna Wiest; Audiobook</li>
+<li>The Off Switch; Mark Cropley; Virgin Books (RE-READ 1ST TIME)</li>
 <li>The Daily Stoic; Ryan Holiday, Stephen Hanselman; Profile Books</li>
-<li>Eat That Frog; Brian Tracy</li>
+<li>The Joy of Missing Out; Christina Crook; New Society Publishers</li>
+<li>Consciousness: A Very Short Introduction; Susan Blackmore; Oxford Uiversity Press</li>
+<li>Never Split the Difference; Chris Voss, Tahl Raz; Random House Business</li>
+<li>Digital Minimalism; Cal Newport; Portofolio Penguin</li>
+<li>The Power of Now; Eckhard Tolle; Yellow Kite</li>
+<li>Ultralearning; Scott Young; Thorsons</li>
+<li>Stop starting, start finishing; Arne Roock; Lean-Kanban University  </li>
 <li>Search Inside Yourself - The Unexpected path to Achieving Success, Happiness (and World Peace); Chade-Meng Tan, Daniel Goleman, Jon Kabat-Zinn; HarperOne</li>
-<li>Coders at Work - Reflections on the craft of programming, Peter Seibel and Mitchell Dorian et al., Audiobook</li>
 <li>The Complete Software Developer&#39;s Career Guide; John Sonmez; Unabridged Audiobook</li>
-<li>Digital Minimalism; Cal Newport; Portofolio Penguin</li>
+<li>Deep Work; Cal Newport; Piatkus</li>
+<li>Coders at Work - Reflections on the craft of programming, Peter Seibel and Mitchell Dorian et al., Audiobook</li>
+<li>Eat That Frog; Brian Tracy</li>
+<li>Ultralearning; Anna Laurent; Self-published via Amazon</li>
 <li>Buddah and Einstein walk into a Bar; Guy Joseph Ale, Claire Bloom; Blackstone Publishing</li>
-<li>Meditation for Mortals, Oliver Burkeman, Audiobook</li>
-<li>The Bullet Journal Method; Ryder Carroll; Fourth Estate</li>
-<li>Getting Things Done; David Allen</li>
-<li>Psycho-Cybernetics; Maxwell Maltz; Perigee Books</li>
-<li>The Power of Now; Eckhard Tolle; Yellow Kite</li>
-<li>Consciousness: A Very Short Introduction; Susan Blackmore; Oxford Uiversity Press</li>
-<li>The Obstacle Is The Way; Ryan Holiday; Profile Books Ltd</li>
-<li>Slow Productivity; Cal Newport; Penguin Random House</li>
-<li>The Joy of Missing Out; Christina Crook; New Society Publishers</li>
-<li>Staff Engineer: Leadership beyond the management track; Will Larson; Audiobook</li>
-<li>The 7 Habits Of Highly Effective People; Stephen R. Covey; Simon &amp; Schuster UK</li>
+<li>The Good Enough Job; Simone Stolzoff; Ebury Edge</li>
 <li>Time Management for System Administrators; Thomas A. Limoncelli; O&#39;Reilly</li>
-<li>Ultralearning; Anna Laurent; Self-published via Amazon</li>
-<li>Influence without Authority; A. Cohen, D. Bradford; Wiley</li>
-<li>Soft Skills; John Sommez; Manning Publications</li>
-<li>Eat That Frog!; Brian Tracy; Hodder Paperbacks</li>
 <li>Who Moved My Cheese?; Dr. Spencer Johnson; Vermilion</li>
-<li>So Good They Can&#39;t Ignore You; Cal Newport; Business Plus</li>
-<li>101 Essays that change the way you think; Brianna Wiest; Audiobook</li>
+<li>Psycho-Cybernetics; Maxwell Maltz; Perigee Books</li>
+<li>Soft Skills; John Sommez; Manning Publications</li>
 </ul><br />
 <a class='textlink' href='../notes/index.html'>Here are notes of mine for some of the books</a><br />
 <br />
@@ -159,30 +159,30 @@
 <span>Some of these were in-person with exams; others were online learning lectures only. In random order:</span><br />
 <br />
 <ul>
-<li>Red Hat Certified System Administrator; Course + certification (Although I had the option, I decided not to take the next course as it is more effective to self learn what I need)</li>
-<li>F5 Loadbalancers Training; 2-day on-site training; F5, Inc. </li>
+<li>The Well-Grounded Rubyist Video Edition; David. A. Black; O&#39;Reilly Online</li>
 <li>The Ultimate Kubernetes Bootcamp; School of Devops; O&#39;Reilly Online</li>
-<li>Developing IaC with Terraform (with Live Lessons); O&#39;Reilly Online</li>
-<li>Protocol buffers; O&#39;Reilly Online</li>
+<li>AWS Immersion Day; Amazon; 1-day interactive online training </li>
+<li>Linux Security and Isolation APIs Training; Michael Kerrisk; 3-day on-site training</li>
+<li>Cloud Operations on AWS - Learn how to configure, deploy, maintain, and troubleshoot your AWS environments; 3-day online live training with labs; Amazon</li>
+<li>Red Hat Certified System Administrator; Course + certification (Although I had the option, I decided not to take the next course as it is more effective to self learn what I need)</li>
 <li>Structure and Interpretation of Computer Programs; Harold Abelson and more...; </li>
-<li>The Well-Grounded Rubyist Video Edition; David. A. Black; O&#39;Reilly Online</li>
-<li>Algorithms Video Lectures; Robert Sedgewick; O&#39;Reilly Online</li>
 <li>Apache Tomcat Best Practises; 3-day on-site training</li>
-<li>Functional programming lecture; Remote University of Hagen</li>
-<li>Linux Security and Isolation APIs Training; Michael Kerrisk; 3-day on-site training</li>
-<li>AWS Immersion Day; Amazon; 1-day interactive online training </li>
+<li>Algorithms Video Lectures; Robert Sedgewick; O&#39;Reilly Online</li>
 <li>Scripting Vim; Damian Conway; O&#39;Reilly Online</li>
-<li>Cloud Operations on AWS - Learn how to configure, deploy, maintain, and troubleshoot your AWS environments; 3-day online live training with labs; Amazon</li>
-<li>MySQL Deep Dive Workshop; 2-day on-site training</li>
 <li>Ultimate Go Programming; Bill Kennedy; O&#39;Reilly Online</li>
+<li>Functional programming lecture; Remote University of Hagen</li>
+<li>F5 Loadbalancers Training; 2-day on-site training; F5, Inc. </li>
+<li>MySQL Deep Dive Workshop; 2-day on-site training</li>
+<li>Protocol buffers; O&#39;Reilly Online</li>
+<li>Developing IaC with Terraform (with Live Lessons); O&#39;Reilly Online</li>
 </ul><br />
 <h2 style='display: inline' id='technical-guides'>Technical guides</h2><br />
 <br />
 <span>These are not whole books, but guides (smaller or larger) which I found very useful. in random order:</span><br />
 <br />
 <ul>
-<li>Raku Guide at https://raku.guide  </li>
 <li>How CPUs work at https://cpu.land</li>
+<li>Raku Guide at https://raku.guide  </li>
 <li>Advanced Bash-Scripting Guide </li>
 </ul><br />
 <h2 style='display: inline' id='podcasts'>Podcasts</h2><br />
@@ -192,48 +192,48 @@
 <span>In random order:</span><br />
 <br />
 <ul>
-<li>The ProdCast (Google SRE Podcast)</li>
-<li>Maintainable</li>
-<li>The Pragmatic Engineer Podcast</li>
-<li>Hidden Brain</li>
-<li>Dev Interrupted</li>
 <li>Cup o&#39; Go [Golang]</li>
-<li>The Changelog Podcast(s)</li>
 <li>Fork Around And Find Out</li>
+<li>Hidden Brain</li>
+<li>Fallthrough [Golang]</li>
 <li>BSD Now [BSD]</li>
+<li>The Changelog Podcast(s)</li>
+<li>Dev Interrupted</li>
+<li>The Pragmatic Engineer Podcast</li>
+<li>Maintainable</li>
+<li>Modern Mentor</li>
 <li>Backend Banter</li>
 <li>Deep Questions with Cal Newport</li>
-<li>Fallthrough [Golang]</li>
-<li>Modern Mentor</li>
+<li>The ProdCast (Google SRE Podcast)</li>
 </ul><br />
 <h3 style='display: inline' id='podcasts-i-liked'>Podcasts I liked</h3><br />
 <br />
 <span>I liked them but am not listening to them anymore. The podcasts have either "finished" (no more episodes) or I stopped listening to them due to time constraints or a shift in my interests.</span><br />
 <br />
 <ul>
-<li>Ship It (predecessor of Fork Around And Find Out)</li>
+<li>FLOSS weekly</li>
 <li>CRE: Chaosradio Express [german]</li>
 <li>Java Pub House</li>
-<li>FLOSS weekly</li>
 <li>Go Time (predecessor of fallthrough)</li>
 <li>Modern Mentor</li>
+<li>Ship It (predecessor of Fork Around And Find Out)</li>
 </ul><br />
 <h2 style='display: inline' id='newsletters-i-like'>Newsletters I like</h2><br />
 <br />
 <span>This is a mix of tech and non-tech newsletters I am subscribed to. In random order:</span><br />
 <br />
 <ul>
-<li>The Pragmatic Engineer</li>
-<li>Andreas Brandhorst Newsletter (Sci-Fi author)</li>
-<li>Register Spill</li>
-<li>VK Newsletter</li>
 <li>Golang Weekly</li>
-<li>byteSizeGo</li>
-<li>Ruby Weekly</li>
-<li>The Imperfectionist</li>
 <li>The Valuable Dev</li>
+<li>VK Newsletter</li>
+<li>Ruby Weekly</li>
 <li>Changelog News</li>
+<li>Register Spill</li>
+<li>The Pragmatic Engineer</li>
 <li>Monospace Mentor</li>
+<li>byteSizeGo</li>
+<li>The Imperfectionist</li>
+<li>Andreas Brandhorst Newsletter (Sci-Fi author)</li>
 <li>Applied Go Weekly Newsletter</li>
 </ul><br />
 <h2 style='display: inline' id='magazines-i-liked'>Magazines I like(d)</h2><br />
@@ -241,10 +241,10 @@
 <span>This is a mix of tech I like(d). I may not be a current subscriber, but now and then, I buy an issue. In random order:</span><br />
 <br />
 <ul>
-<li>LWN (online only)</li>
-<li>Linux User</li>
 <li>freeX (not published anymore)</li>
 <li>Linux Magazine</li>
+<li>Linux User</li>
+<li>LWN (online only)</li>
 </ul><br />
 <h1 style='display: inline' id='formal-education'>Formal education</h1><br />
 <br />
diff --git a/gemfeed/2025-07-22-task-samurai.html b/gemfeed/2025-07-22-task-samurai.html
new file mode 100644
index 00000000..8ea20ccb
--- /dev/null
+++ b/gemfeed/2025-07-22-task-samurai.html
@@ -0,0 +1,141 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<title>Task Samurai</title>
+<link rel="shortcut icon" type="image/gif" href="/favicon.ico" />
+<link rel="stylesheet" href="../style.css" />
+<link rel="stylesheet" href="style-override.css" />
+</head>
+<body>
+<p class="header">
+<a href="https://foo.zone">Home</a> | <a href="https://codeberg.org/snonux/foo.zone/src/branch/content-md/gemfeed/2025-07-22-task-samurai.md">Markdown</a> | <a href="gemini://foo.zone/gemfeed/2025-07-22-task-samurai.gmi">Gemini</a>
+</p>
+<h1 style='display: inline' id='task-samurai'>Task Samurai</h1><br />
+<br />
+<span class='quote'>Published at 2025-06-22T18:49:11+03:00</span><br />
+<br />
+<a href='./task-samurai/logo.png'><img alt='Task Samurai Logo' title='Task Samurai Logo' src='./task-samurai/logo.png' /></a><br />
+<br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
+<br />
+<ul>
+<li><a href='#task-samurai'>Task Samurai</a></li>
+<li>⇢ <a href='#introduction'>Introduction</a></li>
+<li>⇢ ⇢ <a href='#why-does-this-exist'>Why does this exist?</a></li>
+<li>⇢ ⇢ <a href='#how-it-works'>How it works</a></li>
+<li>⇢ <a href='#lessons-learned-from-building-task-samurai-with-agentic-coding'>Lessons Learned from Building Task Samurai with Agentic Coding</a></li>
+<li>⇢ ⇢ <a href='#how-it-went-down'>How It Went Down</a></li>
+<li>⇢ ⇢ <a href='#what-went-wrong'>What Went Wrong</a></li>
+<li>⇢ ⇢ <a href='#patterns-that-helped'>Patterns That Helped</a></li>
+<li>⇢ ⇢ <a href='#what-i-learned-using-agentic-coding'>What I Learned Using Agentic Coding</a></li>
+<li>⇢ ⇢ <a href='#how-much-time-did-i-save'>How Much Time Did I Save?</a></li>
+<li>⇢ <a href='#where-and-how-to-get-it'>Where and how to get it</a></li>
+<li>⇢ <a href='#wrapping-up'>Wrapping Up</a></li>
+</ul><br />
+<h2 style='display: inline' id='introduction'>Introduction</h2><br />
+<br />
+<span>Task Samurai is a fast terminal interface for Taskwarrior written in Go using the Bubble Tea framework. It displays your tasks in a table and allows you to manage them without leaving your keyboard.</span><br />
+<br />
+<a class='textlink' href='https://taskwarrior.org'>https://taskwarrior.org</a><br />
+<a class='textlink' href='https://github.com/charmbracelet/bubbletea'>https://github.com/charmbracelet/bubbletea</a><br />
+<br />
+<h3 style='display: inline' id='why-does-this-exist'>Why does this exist?</h3><br />
+<br />
+<ul>
+<li>I wanted to tinker with agentic coding. This project was entirely implemented using OpenAI Codex.</li>
+<li>I wanted a faster UI for Taskwarrior than other options, like Vit, which is Python-based.</li>
+<li>I wanted something built with Bubble Tea, but I never had time to dive deep into it.</li>
+<li>I wanted to build a toy project (like Task Samurai) first, before tackling the big ones, to get started with agentic coding.</li>
+</ul><br />
+<span>Given the current industry trend and the rapid advancements in technology, it has become clear that experimenting with AI-assisted coding tools is almost a necessity to stay relevant. Embracing these new developments doesn&#39;t mean abandoning traditional coding; instead, it means integrating new capabilities into your workflow to stay ahead in a fast-evolving field.</span><br />
+<br />
+<h3 style='display: inline' id='how-it-works'>How it works</h3><br />
+<br />
+<span>Task Samurai invokes the <span class='inlinecode'>task</span> command to read and modify tasks. The tasks are displayed in a Bubble Tea table, where each row represents a task. Hotkeys trigger Taskwarrior commands such as starting, completing or annotating tasks. The UI refreshes automatically after each action, so the table is always up to date.</span><br />
+<br />
+<a href='./task-samurai/screenshot.png'><img alt='Task Samurai Screenshot' title='Task Samurai Screenshot' src='./task-samurai/screenshot.png' /></a><br />
+<br />
+<h2 style='display: inline' id='lessons-learned-from-building-task-samurai-with-agentic-coding'>Lessons Learned from Building Task Samurai with Agentic Coding</h2><br />
+<br />
+<span>If you&#39;ve ever wanted to supercharge your dev speed—or just throw a fireworks display in your terminal—here&#39;s a peek behind the scenes of building Task Samurai. This terminal interface for Taskwarrior was developed entirely through agentic coding by me, leveraging OpenAI Codex to do all the heavy lifting (and sometimes some cleanup afterwards). The project name might be snappy, but it was the iterative, semi-automated workflow that made the impact.</span><br />
+<br />
+<span>As a side note, I was trying out OpenAI Codex because I regularly run out of Claude Code CLI (another agentic coding tool I am trying out currently) credits (it still happens!), but Codex was still available to me. So, I seized the opportunity to push agentic coding a bit more.</span><br />
+<br />
+<h3 style='display: inline' id='how-it-went-down'>How It Went Down</h3><br />
+<br />
+<span>Task Samurai&#39;s codebase came together quickly: the entire Git history spans from June 19 to 22, 2025, culminating in 179 commits. Here are the broad strokes:</span><br />
+<br />
+<ul>
+<li>June 19: Scaffolded the Go boilerplate, set up tests, integrated the Bubble Tea UI framework, and got the first table views showing up.</li>
+<li>June 20: (The big one—120 commits!) Added hotkeys, colourized tasks, annotation support, undo/redo, and, for fun, fireworks on quit (which never worked and got removed at a later point). This is where most of the bugs, merges, and fast-paced changes happen.</li>
+<li>June 21: Refined searching, theming, and column sizing and documented all those hotkeys. Numerous tweaks to make the UI cleaner and more user-friendly.</li>
+<li>June 22: Final touches—added screenshots, polished the logo, fixed module paths… and then it was a wrap.</li>
+</ul><br />
+<span>Most big breakthroughs (and bug introductions) came during that middle day of intense iteration. The latter stages were all about smoothing out the rough edges.</span><br />
+<br />
+<h3 style='display: inline' id='what-went-wrong'>What Went Wrong</h3><br />
+<br />
+<span>Going agentic isn&#39;t all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons:</span><br />
+<br />
+<ul>
+<li>Merge Floods: Every minor feature or fix existed on its branch, so merging was a constant process. It kept progress flowing but also drowned the committed history in noise and the occasional conflict.</li>
+<li>Fixes on Fixes: Features like "fireworks on exit" had chains of "fix exit," "fix cell selection," etc. Sometimes, new additions introduced bugs that needed rapid patching.</li>
+</ul><br />
+<h3 style='display: inline' id='patterns-that-helped'>Patterns That Helped</h3><br />
+<br />
+<span>Despite the chaos, a few strategies kept things moving:</span><br />
+<br />
+<ul>
+<li>Scaffolding First: I started with the basic table UI and command wrappers, then layered on features—never the other way around.</li>
+<li>Tiny PRs: Small, atomic merges meant feedback came fast (and so did fixes).</li>
+<li>Tests Matter: A solid base of unit tests for task manipulations kept things from breaking entirely when experimenting.</li>
+<li>Live Documentation: Documentation, such as the README, is updated regularly to reflect all the hotkey and feature changes.</li>
+</ul><br />
+<h3 style='display: inline' id='what-i-learned-using-agentic-coding'>What I Learned Using Agentic Coding</h3><br />
+<br />
+<span>Stepping into agentic coding with Codex as my "pair programmer" was a genuine shift. I learned a ton—not just about automating code generation, but also about how you have to tightly steer, guide, and audit every line as things move at breakneck speed. I must admit, I sometimes lost track of what all the generated code was actually doing. But as the features seemed to work after a few iterations, I was satisfied.</span><br />
+<br />
+<span>Discussing requirements with Codex forced me to clarify features and spot logical pitfalls earlier. All those fast iterations meant I was constantly coaxing more helpful, less ambiguous code out of the model—making me rethink how to break features into clear, testable steps. I now see agentic coding not just as a productivity tool but also as a learning accelerator.</span><br />
+<br />
+<h3 style='display: inline' id='how-much-time-did-i-save'>How Much Time Did I Save?</h3><br />
+<br />
+<span>Here&#39;s the million-dollar (or many hours saved) question: Did it buy me speed?</span><br />
+<br />
+<span>Let&#39;s do some back-of-the-envelope math:</span><br />
+<br />
+<ul>
+<li>Say each commit takes Codex 5 minutes to generate, and you need to review/guide 179 commits = about *6 hours of active development*.</li>
+<li>If you coded it all yourself, including all the bug fixes, features, design, and documentation, you might spend *10–20 hours*.</li>
+<li>That&#39;s a potential savings, so what&#39;s usually weeks of work got compressed into just a few frantic days.</li>
+</ul><br />
+<h2 style='display: inline' id='where-and-how-to-get-it'>Where and how to get it</h2><br />
+<br />
+<span>Go to:</span><br />
+<br />
+<a class='textlink' href='https://codeberg.org/snonux/tasksamurai'>https://codeberg.org/snonux/tasksamurai</a><br />
+<br />
+<span>And follow the <span class='inlinecode'>README.md</span>!</span><br />
+<br />
+<h2 style='display: inline' id='wrapping-up'>Wrapping Up</h2><br />
+<br />
+<span>Building Task Samurai with agentic coding was a wild ride—rapid feature growth, plenty of churns, countless fast fixes, and more merge commits I&#39;d expected. The big lessons? Keep the iterations short, keep tests and documentation concise, and review and refine for final polish at the end. Even with the bumps along the way, shipping a polished terminal UI in days instead of weeks is a testament to the raw power (and some hazards) of agentic development.</span><br />
+<br />
+<span>While working on Task Samuray, there were times I genuinely missed manual coding and the satisfaction that comes from writing every line yourself, debugging issues through sheer logic, and crafting solutions from scratch. However, this is the direction in which the industry seems to be shifting, unfortunately. If applied correctly, AI will boost performance, and if you don&#39;t use AI, your next performance review may be awkward.</span><br />
+<br />
+<span>If you&#39;re considering going agentic, be prepared for a sprint, keep your toolkit sharp, and be ready to learn a lot along the way.</span><br />
+<br />
+<span>Personally, I am not sure whether I like where the industry is going with agentic coding. I love "traditional" coding, and with agentic coding you operate at a higher level and don&#39;t interact directly with code as often, which I would miss. I think that in the future, designing, reviewing, and being able to read and understand code will be more important than writing code by hand.</span><br />
+<br />
+<span>Do you have any thoughts on that? I hope, I am partially wrong at least.</span><br />
+<br />
+<span>E-Mail your comments to <span class='inlinecode'>paul@nospam.buetow.org</span> :-)</span><br />
+<br />
+<a class='textlink' href='../'>Back to the main site</a><br />
+<p class="footer">
+Generated with <a href="https://codeberg.org/snonux/gemtexter">Gemtexter 3.0.1-develop</a> |
+served by <a href="https://www.OpenBSD.org">OpenBSD</a>/<a href="https://man.openbsd.org/relayd.8">relayd(8)</a>+<a href="https://man.openbsd.org/httpd.8">httpd(8)</a> |
+<a href="https://foo.zone/site-mirrors.html">Site Mirrors</a>
+</p>
+</body>
+</html>
diff --git a/gemfeed/DRAFT-distributed-systems-simulator.html b/gemfeed/DRAFT-distributed-systems-simulator.html
new file mode 100644
index 00000000..d5327355
--- /dev/null
+++ b/gemfeed/DRAFT-distributed-systems-simulator.html
@@ -0,0 +1,320 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<title>Distributed Systems Simulator</title>
+<link rel="shortcut icon" type="image/gif" href="/favicon.ico" />
+<link rel="stylesheet" href="../style.css" />
+<link rel="stylesheet" href="style-override.css" />
+</head>
+<body>
+<p class="header">
+<a href="https://foo.zone">Home</a> | <a href="https://codeberg.org/snonux/foo.zone/src/branch/content-md/gemfeed/DRAFT-distributed-systems-simulator.md">Markdown</a> | <a href="gemini://foo.zone/gemfeed/DRAFT-distributed-systems-simulator.gmi">Gemini</a>
+</p>
+<h1 style='display: inline' id='distributed-systems-simulator'>Distributed Systems Simulator</h1><br />
+<br />
+<span>This blog explores the Java-based Distributed Simulator program I&#39;ve created specifically for simulating distributed systems protocols, offering both built-in implementations of common algorithms and an extensible framework that allows researchers and practitioners to implement and test their own custom protocols within the simulation environment.</span><br />
+<br />
+<h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
+<br />
+<ul>
+<li><a href='#distributed-systems-simulator'>Distributed Systems Simulator</a></li>
+<li>⇢ <a href='#motivation'>Motivation</a></li>
+<li>⇢ <a href='#fundamentals'>Fundamentals</a></li>
+<li>⇢ ⇢ <a href='#clientserver-model'>Client/Server Model</a></li>
+<li>⇢ ⇢ <a href='#processes-and-their-roles'>Processes and Their Roles</a></li>
+<li>⇢ ⇢ <a href='#messages'>Messages</a></li>
+<li>⇢ ⇢ <a href='#local-and-global-clocks'>Local and Global Clocks</a></li>
+<li>⇢ ⇢ <a href='#events'>Events</a></li>
+<li>⇢ ⇢ <a href='#protocols'>Protocols</a></li>
+<li><a href='#graphical-user-interface-gui'>Graphical User Interface (GUI)</a></li>
+<li>⇢ <a href='#simple-mode'>Simple Mode</a></li>
+<li>⇢ ⇢ <a href='#the-menu-bar'>The Menu Bar</a></li>
+<li>⇢ ⇢ <a href='#the-toolbar'>The Toolbar</a></li>
+<li>⇢ ⇢ <a href='#the-visualization'>The Visualization</a></li>
+<li>⇢ ⇢ <a href='#color-differentiation'>Color Differentiation</a></li>
+<li>⇢ ⇢ <a href='#the-sidebar'>The Sidebar</a></li>
+<li>⇢ ⇢ <a href='#the-log-window'>The Log Window</a></li>
+<li>⇢ <a href='#expert-mode'>Expert Mode</a></li>
+<li>⇢ ⇢ <a href='#new-functions-in-the-sidebar'>New Functions in the Sidebar</a></li>
+<li>⇢ ⇢ <a href='#lamport-time-vector-time-and-anti-aliasing-switches'>Lamport Time, Vector Time, and Anti-Aliasing Switches</a></li>
+<li>⇢ ⇢ <a href='#the-log-filter'>The Log Filter</a></li>
+<li>⇢ <a href='#events'>Events</a></li>
+<li>⇢ ⇢ <a href='#key-features-of-events'>Key Features of Events:</a></li>
+<li>⇢ ⇢ <a href='#event-types-available'>Event Types Available:</a></li>
+<li>⇢ <a href='#summary'>Summary</a></li>
+</ul><br />
+<h2 style='display: inline' id='motivation'>Motivation</h2><br />
+<br />
+<span>Distributed systems are notoriously complex, with intricate interactions between multiple nodes, network partitions, and failure scenarios that can be difficult to understand and debug in production environments. A distributed systems simulator provides an invaluable learning tool that allows developers and students to experiment with different architectures, observe how systems behave under various failure conditions, and gain hands-on experience with concepts like consensus algorithms, replication strategies, and fault tolerance—all within a controlled, repeatable environment. By abstracting away the operational overhead of managing real distributed infrastructure, simulators enable focused exploration of system design principles and help bridge the gap between theoretical knowledge and practical understanding of how distributed systems actually work in the real world.</span><br />
+<br />
+<span>In the literature, one can find many different definitions of a distributed system. Many of these definitions differ from each other, making it difficult to find a single definition that stands alone as the correct one. Andrew Tanenbaum and Maarten van Steen chose the following loose characterization for describing a distributed system:</span><br />
+<br />
+<span class='quote'>"A distributed system is a collection of independent computers that appears to its users as a single coherent system" - Andrew Tanenbaum</span><br />
+<br />
+<span>The user only needs to interact with the local computer in front of them, while the software of the local computer ensures smooth communication with the other participating computers in the distributed system.</span><br />
+<br />
+<span>This thesis aims to make it easier for users to view distributed systems from a different perspective. Here, the viewpoint of an end user is not adopted; instead, the functional methods of protocols and their processes in distributed systems should be made comprehensible, while simultaneously making all relevant events of a distributed system transparent.</span><br />
+<br />
+<span>To achieve this goal, a simulator was developed, particularly for teaching and learning purposes at the University of Applied Sciences Aachen. With the simulator, protocols from distributed systems with their most important influencing factors can be replicated through simulations. At the same time, there is ample room for personal experiments, with no restriction to a fixed number of protocols. It is therefore important that users are enabled to design their own protocols.</span><br />
+<br />
+<h2 style='display: inline' id='fundamentals'>Fundamentals</h2><br />
+<br />
+<span>For basic understanding, some fundamentals are explained below. A deeper exploration will follow in later chapters.</span><br />
+<br />
+<h3 style='display: inline' id='clientserver-model'>Client/Server Model</h3><br />
+<br />
+<pre>
+┌─────────────────────────────────────────────┐
+│                                             │
+│     ┌────────┐         ┌────────┐           │
+│     │ Client │◄-------►│ Server │           │
+│     └────────┘         └────────┘           │
+│                                             │
+│         Sending of Messages                 │
+│                                             │
+└─────────────────────────────────────────────┘
+
+Figure 1.1: Client/Server Model
+</pre>
+<br />
+<span>The simulator is based on the client/server principle. Each simulation typically consists of a participating client and a server that communicate with each other via mes