From b4151488cc973e8ed3f507cb850ece7f0d9d40cd Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 23 Jun 2025 01:01:47 +0300 Subject: Update content for html --- gemfeed/2025-06-22-task-samurai.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'gemfeed/2025-06-22-task-samurai.html') diff --git a/gemfeed/2025-06-22-task-samurai.html b/gemfeed/2025-06-22-task-samurai.html index 425468b2..b775f3b1 100644 --- a/gemfeed/2025-06-22-task-samurai.html +++ b/gemfeed/2025-06-22-task-samurai.html @@ -31,7 +31,7 @@
  • ⇢ ⇢ What went wrong
  • ⇢ ⇢ Patterns that helped
  • ⇢ ⇢ What I learned using agentic coding
    • -
  • ⇢ ⇢ How much time did I save?
    • +
  • ⇢ ⇢ how much time did I save?
  • ⇢ Conclusion

    • Introduction


    @@ -117,7 +117,8 @@ Stepping into agentic coding with Codex as my "pair programmer" was a genuine shift. I learned a lot—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—which is a bit concerning. Imagine if I approved a PR for a production-grade deployment without fully understanding what it was doing (and not a toy project like in this post).

    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.
    -

    How much time did I save?


    +
    +

    how much time did I save?



    Did it buy me speed? Let's do some back-of-the-envelope math:

    -- cgit v1.2.3