diff options
Diffstat (limited to 'gemfeed')
| -rw-r--r-- | gemfeed/2025-07-22-task-samurai.gmi | 6 | ||||
| -rw-r--r-- | gemfeed/2025-07-22-task-samurai.gmi.tpl | 4 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 8 |
3 files changed, 12 insertions, 6 deletions
diff --git a/gemfeed/2025-07-22-task-samurai.gmi b/gemfeed/2025-07-22-task-samurai.gmi index d3cff2ac..bc827384 100644 --- a/gemfeed/2025-07-22-task-samurai.gmi +++ b/gemfeed/2025-07-22-task-samurai.gmi @@ -14,7 +14,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 @@ -66,6 +66,8 @@ Task Samurai's codebase came together quickly: the entire Git history spans from 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: @@ -73,7 +75,7 @@ Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a * 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/2025-07-22-task-samurai.gmi.tpl b/gemfeed/2025-07-22-task-samurai.gmi.tpl index 4be53071..639bbf17 100644 --- a/gemfeed/2025-07-22-task-samurai.gmi.tpl +++ b/gemfeed/2025-07-22-task-samurai.gmi.tpl @@ -53,6 +53,8 @@ Task Samurai's codebase came together quickly: the entire Git history spans from 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: @@ -60,7 +62,7 @@ Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a * 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 807409e3..e4d02707 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> - <updated>2025-06-22T19:29:25+03:00</updated> + <updated>2025-06-22T19:42:04+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" /> @@ -35,7 +35,7 @@ <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-hhat-helped'>Patterns hhat helped</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='#conclusion'>Conclusion</a></li> @@ -89,6 +89,8 @@ </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 /> +<span>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.</span><br /> +<br /> <h3 style='display: inline' id='what-went-wrong'>What went wrong</h3><br /> <br /> <span>Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons:</span><br /> @@ -97,7 +99,7 @@ <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-hhat-helped'>Patterns hhat helped</h3><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 /> |