From b8bdbf7b99c6cabbac667744fa987fd8e1c42158 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 22 Jun 2025 19:04:24 +0300 Subject: Update content for html --- gemfeed/2025-07-22-task-samurai.html | 27 ++++++++++++++------------- gemfeed/atom.xml | 29 +++++++++++++++-------------- gemfeed/index.html | 2 +- 3 files changed, 30 insertions(+), 28 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-07-22-task-samurai.html b/gemfeed/2025-07-22-task-samurai.html index 8ea20ccb..49e87f9f 100644 --- a/gemfeed/2025-07-22-task-samurai.html +++ b/gemfeed/2025-07-22-task-samurai.html @@ -2,7 +2,7 @@ -Task Samurai +Task Samurai: An agentic coding learning experiment @@ -11,7 +11,7 @@

Home | Markdown | Gemini

-

Task Samurai


+

Task Samurai: An agentic coding learning experiment



Published at 2025-06-22T18:49:11+03:00

@@ -20,17 +20,17 @@

Table of Contents




Introduction


@@ -56,6 +56,14 @@
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.
@@ -79,7 +87,7 @@ Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons:


Patterns That Helped


@@ -92,6 +100,7 @@
  • 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.

    • +

    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.
    @@ -109,14 +118,6 @@
  • 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 ff9e8df8..afa9027f 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,13 +1,13 @@ - 2025-06-22T18:57:24+03:00 + 2025-06-22T19:03:15+03:00 foo.zone feed To be in the .zone! https://foo.zone/ - Task Samurai + Task Samurai: An agentic coding learning experiment https://foo.zone/gemfeed/2025-07-22-task-samurai.html 2025-06-22T18:49:11+03:00 @@ -18,7 +18,7 @@ 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.
    -

    Task Samurai


    +

    Task Samurai: An agentic coding learning experiment



    Published at 2025-06-22T18:49:11+03:00

    @@ -27,17 +27,17 @@

    Table of Contents




    Introduction


    @@ -63,6 +63,14 @@
    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.
    @@ -86,7 +94,7 @@ 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


    @@ -99,6 +107,7 @@
  • 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.

    • +

    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.
    @@ -116,14 +125,6 @@
  • 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/index.html b/gemfeed/index.html index 2c897a34..ad1fdaef 100644 --- a/gemfeed/index.html +++ b/gemfeed/index.html @@ -15,7 +15,7 @@

    To be in the .zone!



    -2025-07-22 - Task Samurai
    +2025-07-22 - Task Samurai: An agentic coding learning experiment
    2025-06-07 - 'A Monk's Guide to Happiness' book notes
    2025-05-11 - f3s: Kubernetes with FreeBSD - Part 5: WireGuard mesh network
    2025-05-02 - Terminal multiplexing with tmux - Fish edition
    -- cgit v1.2.3