summaryrefslogtreecommitdiff
path: root/gemfeed
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2025-06-23 01:01:48 +0300
committerPaul Buetow <paul@buetow.org>2025-06-23 01:01:48 +0300
commit8d055d8cdc50196c1a4606ce3570dd9cf6d7edec (patch)
treeabbdc579da862fe839f7cef3a7164f526af100e4 /gemfeed
parent1ba14abeab2cc4d1f411caddc92aa9a6c2d89bf1 (diff)
Update content for md
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/2025-06-22-task-samurai.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/gemfeed/2025-06-22-task-samurai.md b/gemfeed/2025-06-22-task-samurai.md
index e7833537..a647ef81 100644
--- a/gemfeed/2025-06-22-task-samurai.md
+++ b/gemfeed/2025-06-22-task-samurai.md
@@ -17,7 +17,7 @@
* [⇢ ⇢ ⇢ What went wrong](#what-went-wrong)
* [⇢ ⇢ ⇢ Patterns that helped](#patterns-that-helped)
* [⇢ ⇢ ⇢ What I learned using agentic coding](#what-i-learned-using-agentic-coding)
-* [⇢ ⇢ ⇢ How much time did I save?](#how-much-time-did-i-save)
+* [⇢ ⇢ ⇢ how much time did I save?](#how-much-time-did-i-save)
* [⇢ ⇢ Conclusion](#conclusion)
## Introduction
@@ -99,7 +99,8 @@ Maybe a better approach would have been to design the whole application from scr
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: