diff options
| -rw-r--r-- | about/resources.gmi | 194 | ||||
| -rw-r--r-- | gemfeed/2025-07-22-task-samurai.gmi | 25 | ||||
| -rw-r--r-- | gemfeed/2025-07-22-task-samurai.gmi.tpl | 23 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 29 | ||||
| -rw-r--r-- | gemfeed/index.gmi | 2 | ||||
| -rw-r--r-- | index.gmi | 4 | ||||
| -rw-r--r-- | uptime-stats.gmi | 2 |
7 files changed, 141 insertions, 138 deletions
diff --git a/about/resources.gmi b/about/resources.gmi index b4423405..38b01a85 100644 --- a/about/resources.gmi +++ b/about/resources.gmi @@ -35,105 +35,105 @@ You won't find any links on this site because, over time, the links will break. In random order: -* Funktionale Programmierung; Peter Pepper; Springer -* Tmux 2: Productive Mouse-free Development; Brain P. Hogan; The Pragmatic Programmers +* Polished Ruby Programming; Jeremy Evans; Packt Publishing +* Data Science at the Command Line; Jeroen Janssens; O'Reilly +* The Go Programming Language; Alan A. A. Donovan; Addison-Wesley Professional +* The KCNA (Kubernetes and Cloud Native Associate) Book; Nigel Poulton +* 21st Century C: C Tips from the New School; Ben Klemens; O'Reilly * Clusterbau mit Linux-HA; Michael Schwartzkopff; O'Reilly -* Programming Ruby 3.3 (5th Edition); Noel Rappin, with Dave Thomas; The Pragmatic Bookshelf -* 100 Go Mistakes and How to Avoid Them; Teiva Harsanyi; Manning Publications -* Raku Fundamentals; Moritz Lenz; Apress -* Developing Games in Java; David Brackeen and others...; New Riders -* Raku Recipes; J.J. Merelo; Apress +* C++ Programming Language; Bjarne Stroustrup; +* Leanring eBPF; Liz Rice; O'Reilly +* DNS and BIND; Cricket Liu; O'Reilly * DevOps And Site Reliability Engineering Handbook; Stephen Fleming; Audible -* Amazon Web Services in Action; Michael Wittig and Andreas Wittig; Manning Publications -* Distributed Systems: Principles and Paradigms; Andrew S. Tanenbaum; Pearson -* Hands-on Infrastructure Monitoring with Prometheus; Joel Bastos, Pedro Araujo; Packt -* Systems Performance Tuning; Gian-Paolo D. Musumeci and others...; O'Reilly -* The KCNA (Kubernetes and Cloud Native Associate) Book; Nigel Poulton +* Java ist auch eine Insel; Christian Ullenboom; +* The Docker Book; James Turnbull; Kindle +* Perl New Features; Joshua McAdams, brian d foy; Perl School +* Raku Recipes; J.J. Merelo; Apress +* Pro Puppet; James Turnbull, Jeffrey McCune; Apress +* Tmux 2: Productive Mouse-free Development; Brain P. Hogan; The Pragmatic Programmers +* 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 +* Learn You Some Erlang for Great Good; Fred Herbert; No Starch Press +* Higher Order Perl; Mark Dominus; Morgan Kaufmann +* 100 Go Mistakes and How to Avoid Them; Teiva Harsanyi; Manning Publications * Ultimate Go Notebook; Bill Kennedy +* The Pragmatic Programmer; David Thomas; Addison-Wesley +* 97 things every SRE should know; Emil Stolarsky, Jaime Woo; O'Reilly +* Site Reliability Engineering; How Google runs production systems; O'Reilly +* Systems Performance Tuning; Gian-Paolo D. Musumeci and others...; O'Reilly +* Programming Ruby 3.3 (5th Edition); Noel Rappin, with Dave Thomas; The Pragmatic Bookshelf * Effective Java; Joshua Bloch; Addison-Wesley Professional -* Modern Perl; Chromatic ; Onyx Neon Press -* Learn You Some Erlang for Great Good; Fred Herbert; No Starch Press -* Systemprogrammierung in Go; Frank Müller; dpunkt -* Terraform Cookbook; Mikael Krief; Packt Publishing * Learn You a Haskell for Great Good!; Miran Lipovaca; No Starch Press -* Polished Ruby Programming; Jeremy Evans; Packt Publishing -* 21st Century C: C Tips from the New School; Ben Klemens; O'Reilly -* Data Science at the Command Line; Jeroen Janssens; O'Reilly * Effective awk programming; Arnold Robbins; O'Reilly -* C++ Programming Language; Bjarne Stroustrup; -* The DevOps Handbook; Gene Kim, Jez Humble, Patrick Debois, John Willis; Audible -* Object-Oriented Programming with ANSI-C; Axel-Tobias Schreiner -* Concurrency in Go; Katherine Cox-Buday; O'Reilly -* Kubernetes Cookbook; Sameer Naik, Sébastien Goasguen, Jonathan Michaux; O'Reilly -* Perl New Features; Joshua McAdams, brian d foy; Perl School -* Site Reliability Engineering; How Google runs production systems; O'Reilly +* Distributed Systems: Principles and Paradigms; Andrew S. Tanenbaum; Pearson +* Terraform Cookbook; Mikael Krief; Packt Publishing +* Hands-on Infrastructure Monitoring with Prometheus; Joel Bastos, Pedro Araujo; Packt +* Programming Perl aka "The Camel Book"; Tom Christiansen, brian d foy, Larry Wall & Jon Orwant; O'Reilly +* Systemprogrammierung in Go; Frank Müller; dpunkt * Think Raku (aka Think Perl 6); Laurent Rosenfeld, Allen B. Downey; O'Reilly +* Kubernetes Cookbook; Sameer Naik, Sébastien Goasguen, Jonathan Michaux; O'Reilly +* Raku Fundamentals; Moritz Lenz; Apress +* Amazon Web Services in Action; Michael Wittig and Andreas Wittig; Manning Publications +* Funktionale Programmierung; Peter Pepper; Springer +* Modern Perl; Chromatic ; Onyx Neon Press +* Developing Games in Java; David Brackeen and others...; New Riders +* Object-Oriented Programming with ANSI-C; Axel-Tobias Schreiner * Go Brain Teasers - Exercise Your Mind; Miki Tebeka; The Pragmatic Programmers -* Leanring eBPF; Liz Rice; O'Reilly -* 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 -* Java ist auch eine Insel; Christian Ullenboom; -* The Go Programming Language; Alan A. A. Donovan; Addison-Wesley Professional -* DNS and BIND; Cricket Liu; O'Reilly -* 97 things every SRE should know; Emil Stolarsky, Jaime Woo; O'Reilly * The Kubernetes Book; Nigel Poulton; Unabridged Audiobook -* The Docker Book; James Turnbull; Kindle -* Programming Perl aka "The Camel Book"; Tom Christiansen, brian d foy, Larry Wall & Jon Orwant; O'Reilly -* Higher Order Perl; Mark Dominus; Morgan Kaufmann -* The Pragmatic Programmer; David Thomas; Addison-Wesley -* Pro Puppet; James Turnbull, Jeffrey McCune; Apress +* Concurrency in Go; Katherine Cox-Buday; O'Reilly +* The DevOps Handbook; Gene Kim, Jez Humble, Patrick Debois, John Willis; Audible ## Technical references I didn't read them from the beginning to the end, but I am using them to look up things. The books are in random order: +* BPF Performance Tools - Linux System and Application Observability, Brendan Gregg; Addison Wesley +* Groovy Kurz & Gut; Joerg Staudemeier; O'Reilly * The Linux Programming Interface; Michael Kerrisk; No Starch Press * Go: Design Patterns for Real-World Projects; Mat Ryer; Packt * Algorithms; Robert Sedgewick, Kevin Wayne; Addison Wesley -* Groovy Kurz & Gut; Joerg Staudemeier; O'Reilly * Understanding the Linux Kernel; Daniel P. Bovet, Marco Cesati; O'Reilly * Implementing Service Level Objectives; Alex Hidalgo; O'Reilly * Relayd and Httpd Mastery; Michael W Lucas -* BPF Performance Tools - Linux System and Application Observability, Brendan Gregg; Addison Wesley ## Self-development and soft-skills books In random order: -* Getting Things Done; David Allen -* Slow Productivity; Cal Newport; Penguin Random House -* The Phoenix Project - A Novel About IT, DevOps, and Helping your Business Win; Gene Kim and Kevin Behr; Trade Select -* Meditation for Mortals, Oliver Burkeman, Audiobook -* Atomic Habits; James Clear; Random House Business -* Influence without Authority; A. Cohen, D. Bradford; Wiley -* The 7 Habits Of Highly Effective People; Stephen R. Covey; Simon & Schuster UK -* So Good They Can't Ignore You; Cal Newport; Business Plus -* The Bullet Journal Method; Ryder Carroll; Fourth Estate -* Staff Engineer: Leadership beyond the management track; Will Larson; Audiobook -* Solve for Happy; Mo Gawdat (RE-READ 1ST TIME) -* Eat That Frog!; Brian Tracy; Hodder Paperbacks -* The Obstacle Is The Way; Ryan Holiday; Profile Books Ltd +* Coders at Work - Reflections on the craft of programming, Peter Seibel and Mitchell Dorian et al., Audiobook +* Ultralearning; Anna Laurent; Self-published via Amazon * 101 Essays that change the way you think; Brianna Wiest; Audiobook -* The Off Switch; Mark Cropley; Virgin Books (RE-READ 1ST TIME) -* The Daily Stoic; Ryan Holiday, Stephen Hanselman; Profile Books -* The Joy of Missing Out; Christina Crook; New Society Publishers -* Consciousness: A Very Short Introduction; Susan Blackmore; Oxford Uiversity Press +* Psycho-Cybernetics; Maxwell Maltz; Perigee Books * Never Split the Difference; Chris Voss, Tahl Raz; Random House Business -* Digital Minimalism; Cal Newport; Portofolio Penguin -* The Power of Now; Eckhard Tolle; Yellow Kite -* Ultralearning; Scott Young; Thorsons * Stop starting, start finishing; Arne Roock; Lean-Kanban University -* Search Inside Yourself - The Unexpected path to Achieving Success, Happiness (and World Peace); Chade-Meng Tan, Daniel Goleman, Jon Kabat-Zinn; HarperOne +* The Joy of Missing Out; Christina Crook; New Society Publishers +* Soft Skills; John Sommez; Manning Publications +* Digital Minimalism; Cal Newport; Portofolio Penguin +* So Good They Can't Ignore You; Cal Newport; Business Plus * The Complete Software Developer's Career Guide; John Sonmez; Unabridged Audiobook * Deep Work; Cal Newport; Piatkus -* Coders at Work - Reflections on the craft of programming, Peter Seibel and Mitchell Dorian et al., Audiobook -* Eat That Frog; Brian Tracy -* Ultralearning; Anna Laurent; Self-published via Amazon +* The 7 Habits Of Highly Effective People; Stephen R. Covey; Simon & Schuster UK +* The Obstacle Is The Way; Ryan Holiday; Profile Books Ltd +* Eat That Frog!; Brian Tracy; Hodder Paperbacks +* Search Inside Yourself - The Unexpected path to Achieving Success, Happiness (and World Peace); Chade-Meng Tan, Daniel Goleman, Jon Kabat-Zinn; HarperOne * Buddah and Einstein walk into a Bar; Guy Joseph Ale, Claire Bloom; Blackstone Publishing -* The Good Enough Job; Simone Stolzoff; Ebury Edge +* The Power of Now; Eckhard Tolle; Yellow Kite +* Eat That Frog; Brian Tracy +* Ultralearning; Scott Young; Thorsons +* Solve for Happy; Mo Gawdat (RE-READ 1ST TIME) +* Atomic Habits; James Clear; Random House Business +* Consciousness: A Very Short Introduction; Susan Blackmore; Oxford Uiversity Press +* The Phoenix Project - A Novel About IT, DevOps, and Helping your Business Win; Gene Kim and Kevin Behr; Trade Select * Time Management for System Administrators; Thomas A. Limoncelli; O'Reilly +* The Good Enough Job; Simone Stolzoff; Ebury Edge +* The Bullet Journal Method; Ryder Carroll; Fourth Estate +* Slow Productivity; Cal Newport; Penguin Random House +* The Daily Stoic; Ryan Holiday, Stephen Hanselman; Profile Books +* Getting Things Done; David Allen +* Staff Engineer: Leadership beyond the management track; Will Larson; Audiobook * Who Moved My Cheese?; Dr. Spencer Johnson; Vermilion -* Psycho-Cybernetics; Maxwell Maltz; Perigee Books -* Soft Skills; John Sommez; Manning Publications +* The Off Switch; Mark Cropley; Virgin Books (RE-READ 1ST TIME) +* Meditation for Mortals, Oliver Burkeman, Audiobook +* Influence without Authority; A. Cohen, D. Bradford; Wiley => ../notes/index.gmi Here are notes of mine for some of the books @@ -141,30 +141,30 @@ In random order: Some of these were in-person with exams; others were online learning lectures only. In random order: +* Developing IaC with Terraform (with Live Lessons); O'Reilly Online +* Apache Tomcat Best Practises; 3-day on-site training * The Well-Grounded Rubyist Video Edition; David. A. Black; O'Reilly Online -* The Ultimate Kubernetes Bootcamp; School of Devops; O'Reilly Online -* AWS Immersion Day; Amazon; 1-day interactive online training * Linux Security and Isolation APIs Training; Michael Kerrisk; 3-day on-site training +* AWS Immersion Day; Amazon; 1-day interactive online training +* Algorithms Video Lectures; Robert Sedgewick; O'Reilly Online * Cloud Operations on AWS - Learn how to configure, deploy, maintain, and troubleshoot your AWS environments; 3-day online live training with labs; Amazon * 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) * Structure and Interpretation of Computer Programs; Harold Abelson and more...; -* Apache Tomcat Best Practises; 3-day on-site training -* Algorithms Video Lectures; Robert Sedgewick; O'Reilly Online -* Scripting Vim; Damian Conway; O'Reilly Online -* Ultimate Go Programming; Bill Kennedy; O'Reilly Online * Functional programming lecture; Remote University of Hagen -* F5 Loadbalancers Training; 2-day on-site training; F5, Inc. * MySQL Deep Dive Workshop; 2-day on-site training +* The Ultimate Kubernetes Bootcamp; School of Devops; O'Reilly Online * Protocol buffers; O'Reilly Online -* Developing IaC with Terraform (with Live Lessons); O'Reilly Online +* Ultimate Go Programming; Bill Kennedy; O'Reilly Online +* F5 Loadbalancers Training; 2-day on-site training; F5, Inc. +* Scripting Vim; Damian Conway; O'Reilly Online ## Technical guides These are not whole books, but guides (smaller or larger) which I found very useful. in random order: -* How CPUs work at https://cpu.land -* Raku Guide at https://raku.guide * Advanced Bash-Scripting Guide +* Raku Guide at https://raku.guide +* How CPUs work at https://cpu.land ## Podcasts @@ -172,56 +172,56 @@ These are not whole books, but guides (smaller or larger) which I found very use In random order: -* Cup o' Go [Golang] -* Fork Around And Find Out +* Deep Questions with Cal Newport +* The ProdCast (Google SRE Podcast) * Hidden Brain +* Maintainable * Fallthrough [Golang] * BSD Now [BSD] +* Backend Banter +* Modern Mentor +* The Pragmatic Engineer Podcast +* Cup o' Go [Golang] +* Fork Around And Find Out * The Changelog Podcast(s) * Dev Interrupted -* The Pragmatic Engineer Podcast -* Maintainable -* Modern Mentor -* Backend Banter -* Deep Questions with Cal Newport -* The ProdCast (Google SRE Podcast) ### Podcasts I liked 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. +* Ship It (predecessor of Fork Around And Find Out) * FLOSS weekly -* CRE: Chaosradio Express [german] -* Java Pub House * Go Time (predecessor of fallthrough) +* CRE: Chaosradio Express [german] * Modern Mentor -* Ship It (predecessor of Fork Around And Find Out) +* Java Pub House ## Newsletters I like This is a mix of tech and non-tech newsletters I am subscribed to. In random order: -* Golang Weekly +* The Imperfectionist * The Valuable Dev -* VK Newsletter -* Ruby Weekly -* Changelog News -* Register Spill * The Pragmatic Engineer +* Register Spill * Monospace Mentor -* byteSizeGo -* The Imperfectionist -* Andreas Brandhorst Newsletter (Sci-Fi author) * Applied Go Weekly Newsletter +* Golang Weekly +* Changelog News +* VK Newsletter +* Andreas Brandhorst Newsletter (Sci-Fi author) +* Ruby Weekly +* byteSizeGo ## Magazines I like(d) 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: -* freeX (not published anymore) * Linux Magazine -* Linux User * LWN (online only) +* Linux User +* freeX (not published anymore) # Formal education diff --git a/gemfeed/2025-07-22-task-samurai.gmi b/gemfeed/2025-07-22-task-samurai.gmi index 1945c34d..5b687058 100644 --- a/gemfeed/2025-07-22-task-samurai.gmi +++ b/gemfeed/2025-07-22-task-samurai.gmi @@ -1,4 +1,4 @@ -# Task Samurai +# Task Samurai: An agentic coding learning experiment > Published at 2025-06-22T18:49:11+03:00 @@ -6,17 +6,17 @@ ## Table of Contents -* ⇢ Task Samurai +* ⇢ Task Samurai: An agentic coding learning experiment * ⇢ ⇢ Introduction * ⇢ ⇢ ⇢ Why does this exist? * ⇢ ⇢ ⇢ How it works +* ⇢ ⇢ Where and how to get it * ⇢ ⇢ Lessons Learned from Building Task Samurai with Agentic Coding * ⇢ ⇢ ⇢ How It Went Down * ⇢ ⇢ ⇢ What Went Wrong * ⇢ ⇢ ⇢ Patterns That Helped * ⇢ ⇢ ⇢ What I Learned Using Agentic Coding * ⇢ ⇢ ⇢ How Much Time Did I Save? -* ⇢ ⇢ Where and how to get it * ⇢ ⇢ Wrapping Up ## Introduction @@ -41,6 +41,14 @@ Task Samurai invokes the `task` command to read and modify tasks. The tasks are => ./task-samurai/screenshot.png Task Samurai Screenshot +## Where and how to get it + +Go to: + +=> https://codeberg.org/snonux/tasksamurai + +And follow the `README.md`! + ## Lessons Learned from Building Task Samurai with Agentic Coding If you've ever wanted to supercharge your dev speed—or just throw a fireworks display in your terminal—here'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. @@ -62,7 +70,7 @@ Most big breakthroughs (and bug introductions) came during that middle day of in Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons: -* 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. +* 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. I found this to be an issue with OpenAI's Codex in particular. Not so much with other agentic coding tools like Claude Code CLI (not covered in this blog post.) * 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. ### Patterns That Helped @@ -73,6 +81,7 @@ Despite the chaos, a few strategies kept things moving: * Tiny PRs: Small, atomic merges meant feedback came fast (and so did fixes). * Tests Matter: A solid base of unit tests for task manipulations kept things from breaking entirely when experimenting. * Live Documentation: Documentation, such as the README, is updated regularly to reflect all the hotkey and feature changes. +Maybe a better approach would have been to design the whole application from scratch before letting Codix do any of the coding. I will try that with my next toy project. ### What I Learned Using Agentic Coding @@ -90,14 +99,6 @@ Let's do some back-of-the-envelope math: * If you coded it all yourself, including all the bug fixes, features, design, and documentation, you might spend *10–20 hours*. * That's a potential savings, so what's usually weeks of work got compressed into just a few frantic days. -## Where and how to get it - -Go to: - -=> https://codeberg.org/snonux/tasksamurai - -And follow the `README.md`! - ## Wrapping Up Building Task Samurai with agentic coding was a wild ride—rapid feature growth, plenty of churns, countless fast fixes, and more merge commits I'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. diff --git a/gemfeed/2025-07-22-task-samurai.gmi.tpl b/gemfeed/2025-07-22-task-samurai.gmi.tpl index 4d26aa78..95f64f40 100644 --- a/gemfeed/2025-07-22-task-samurai.gmi.tpl +++ b/gemfeed/2025-07-22-task-samurai.gmi.tpl @@ -1,4 +1,4 @@ -# Task Samurai +# Task Samurai: An agentic coding learning experiment > Published at 2025-06-22T18:49:11+03:00 @@ -28,6 +28,14 @@ Task Samurai invokes the `task` command to read and modify tasks. The tasks are => ./task-samurai/screenshot.png Task Samurai Screenshot +## Where and how to get it + +Go to: + +=> https://codeberg.org/snonux/tasksamurai + +And follow the `README.md`! + ## Lessons Learned from Building Task Samurai with Agentic Coding If you've ever wanted to supercharge your dev speed—or just throw a fireworks display in your terminal—here'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. @@ -49,7 +57,7 @@ Most big breakthroughs (and bug introductions) came during that middle day of in Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons: -* 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. +* 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. I found this to be an issue with OpenAI's Codex in particular. Not so much with other agentic coding tools like Claude Code CLI (not covered in this blog post.) * 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. ### Patterns That Helped @@ -60,10 +68,11 @@ Despite the chaos, a few strategies kept things moving: * Tiny PRs: Small, atomic merges meant feedback came fast (and so did fixes). * Tests Matter: A solid base of unit tests for task manipulations kept things from breaking entirely when experimenting. * Live Documentation: Documentation, such as the README, is updated regularly to reflect all the hotkey and feature changes. +Maybe a better approach would have been to design the whole application from scratch before letting Codix do any of the coding. I will try that with my next toy project. ### What I Learned Using Agentic Coding -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. +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. 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. @@ -77,14 +86,6 @@ Let's do some back-of-the-envelope math: * If you coded it all yourself, including all the bug fixes, features, design, and documentation, you might spend *10–20 hours*. * That's a potential savings, so what's usually weeks of work got compressed into just a few frantic days. -## Where and how to get it - -Go to: - -=> https://codeberg.org/snonux/tasksamurai - -And follow the `README.md`! - ## Wrapping Up Building Task Samurai with agentic coding was a wild ride—rapid feature growth, plenty of churns, countless fast fixes, and more merge commits I'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. diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index e67c9c17..f7a82144 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,13 +1,13 @@ <?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> - <updated>2025-06-22T18:57:24+03:00</updated> + <updated>2025-06-22T19:03:15+03:00</updated> <title>foo.zone feed</title> <subtitle>To be in the .zone!</subtitle> <link href="gemini://foo.zone/gemfeed/atom.xml" rel="self" /> <link href="gemini://foo.zone/" /> <id>gemini://foo.zone/</id> <entry> - <title>Task Samurai</title> + <title>Task Samurai: An agentic coding learning experiment</title> <link href="gemini://foo.zone/gemfeed/2025-07-22-task-samurai.gmi" /> <id>gemini://foo.zone/gemfeed/2025-07-22-task-samurai.gmi</id> <updated>2025-06-22T18:49:11+03:00</updated> @@ -18,7 +18,7 @@ <summary>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.</summary> <content type="xhtml"> <div xmlns="http://www.w3.org/1999/xhtml"> - <h1 style='display: inline' id='task-samurai'>Task Samurai</h1><br /> + <h1 style='display: inline' id='task-samurai-an-agentic-coding-learning-experiment'>Task Samurai: An agentic coding learning experiment</h1><br /> <br /> <span class='quote'>Published at 2025-06-22T18:49:11+03:00</span><br /> <br /> @@ -27,17 +27,17 @@ <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='#task-samurai-an-agentic-coding-learning-experiment'>Task Samurai: An agentic coding learning experiment</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='#where-and-how-to-get-it'>Where and how to get it</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 /> @@ -63,6 +63,14 @@ <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='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='lessons-learned-from-building-task-samurai-with-agentic-coding'>Lessons Learned from Building Task Samurai with Agentic Coding</h2><br /> <br /> <span>If you've ever wanted to supercharge your dev speed—or just throw a fireworks display in your terminal—here'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 /> @@ -86,7 +94,7 @@ <span>Going agentic isn'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>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. I found this to be an issue with OpenAI's Codex in particular. Not so much with other agentic coding tools like Claude Code CLI (not covered in this blog post.)</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 /> @@ -99,6 +107,7 @@ <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 /> +<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 /> @@ -116,14 +125,6 @@ <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's a potential savings, so what'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'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 /> diff --git a/gemfeed/index.gmi b/gemfeed/index.gmi index 71327620..6d6dea78 100644 --- a/gemfeed/index.gmi +++ b/gemfeed/index.gmi @@ -2,7 +2,7 @@ ## To be in the .zone! -=> ./2025-07-22-task-samurai.gmi 2025-07-22 - Task Samurai +=> ./2025-07-22-task-samurai.gmi 2025-07-22 - Task Samurai: An agentic coding learning experiment => ./2025-06-07-a-monks-guide-to-happiness-book-notes.gmi 2025-06-07 - 'A Monk's Guide to Happiness' book notes => ./2025-05-11-f3s-kubernetes-with-freebsd-part-5.gmi 2025-05-11 - f3s: Kubernetes with FreeBSD - Part 5: WireGuard mesh network => ./2025-05-02-terminal-multiplexing-with-tmux-fish-edition.gmi 2025-05-02 - Terminal multiplexing with `tmux` - Fish edition @@ -1,6 +1,6 @@ # Hello! -> This site was generated at 2025-06-22T18:57:24+03:00 by `Gemtexter` +> This site was generated at 2025-06-22T19:03:14+03:00 by `Gemtexter` Welcome to the ... @@ -38,7 +38,7 @@ Everything you read on this site is my personal opinion and experience. You can ### Posts -=> ./gemfeed/2025-07-22-task-samurai.gmi 2025-07-22 - Task Samurai +=> ./gemfeed/2025-07-22-task-samurai.gmi 2025-07-22 - Task Samurai: An agentic coding learning experiment => ./gemfeed/2025-06-07-a-monks-guide-to-happiness-book-notes.gmi 2025-06-07 - 'A Monk's Guide to Happiness' book notes => ./gemfeed/2025-05-11-f3s-kubernetes-with-freebsd-part-5.gmi 2025-05-11 - f3s: Kubernetes with FreeBSD - Part 5: WireGuard mesh network => ./gemfeed/2025-05-02-terminal-multiplexing-with-tmux-fish-edition.gmi 2025-05-02 - Terminal multiplexing with `tmux` - Fish edition diff --git a/uptime-stats.gmi b/uptime-stats.gmi index 188ff221..7721c647 100644 --- a/uptime-stats.gmi +++ b/uptime-stats.gmi @@ -1,6 +1,6 @@ # My machine uptime stats -> This site was last updated at 2025-06-22T18:57:24+03:00 +> This site was last updated at 2025-06-22T19:03:14+03:00 The following stats were collected via `uptimed` on all of my personal computers over many years and the output was generated by `guprecords`, the global uptime records stats analyser of mine. |