From 412f6320133f0548bfadd84d65417757ede1d804 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 22 Jun 2025 19:42:49 +0300 Subject: Update content for html --- gemfeed/2025-07-22-task-samurai.html | 6 ++++-- gemfeed/atom.xml | 8 +++++--- 2 files changed, 9 insertions(+), 5 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-07-22-task-samurai.html b/gemfeed/2025-07-22-task-samurai.html index 8b385eb3..34331fe8 100644 --- a/gemfeed/2025-07-22-task-samurai.html +++ b/gemfeed/2025-07-22-task-samurai.html @@ -28,7 +28,7 @@
  • ⇢ Lessons Learned from Building Task Samurai with Agentic Coding
  • ⇢ ⇢ How it went down
  • ⇢ ⇢ What went wrong
    • -
  • ⇢ ⇢ Patterns hhat helped
    • +
  • ⇢ ⇢ Patterns that helped
  • ⇢ ⇢ What I learned using agentic coding
  • ⇢ ⇢ How much time did I save?
  • ⇢ Conclusion
    • @@ -82,6 +82,8 @@
    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.

    +It's worth noting that I worked on it in the evenings when I had some free time, as I also had to fit in my regular work and family commitments during the day. So, I didn't spend full working days on this project.
    +

    What went wrong



    Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons:
    @@ -90,7 +92,7 @@
  • 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 hhat helped


    +

    Patterns that helped



    Despite the chaos, a few strategies kept things moving:

    diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index a3b9d2bd..6d5bc86c 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2025-06-22T19:29:25+03:00 + 2025-06-22T19:42:04+03:00 foo.zone feed To be in the .zone! @@ -35,7 +35,7 @@
  • ⇢ Lessons Learned from Building Task Samurai with Agentic Coding
  • ⇢ ⇢ How it went down
  • ⇢ ⇢ What went wrong
    • -
  • ⇢ ⇢ Patterns hhat helped
    • +
  • ⇢ ⇢ Patterns that helped
  • ⇢ ⇢ What I learned using agentic coding
  • ⇢ ⇢ How much time did I save?
  • ⇢ Conclusion
    • @@ -89,6 +89,8 @@
    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.

    +It's worth noting that I worked on it in the evenings when I had some free time, as I also had to fit in my regular work and family commitments during the day. So, I didn't spend full working days on this project.
    +

    What went wrong



    Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons:
    @@ -97,7 +99,7 @@
  • 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 hhat helped


    +

    Patterns that helped



    Despite the chaos, a few strategies kept things moving:

    -- cgit v1.2.3