summaryrefslogtreecommitdiff
path: root/gemfeed
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2025-06-22 19:54:23 +0300
committerPaul Buetow <paul@buetow.org>2025-06-22 19:54:23 +0300
commit85cb5bff255d986a4f9193c1f48722f47aecbf4b (patch)
treefa42e9520ed151cbd1c80703941514271eed447a /gemfeed
parentbd38db86033dce096c9cf5bc840e6da793515c8b (diff)
Update content for md
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/2025-07-22-task-samurai.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/gemfeed/2025-07-22-task-samurai.md b/gemfeed/2025-07-22-task-samurai.md
index 83c29f63..21c526ce 100644
--- a/gemfeed/2025-07-22-task-samurai.md
+++ b/gemfeed/2025-07-22-task-samurai.md
@@ -101,8 +101,8 @@ Here's the million-dollar (or many hours saved) question: Did it buy me speed?
Let's do some back-of-the-envelope math:
-* Say each commit takes Codex 5 minutes to generate, and you need to review/guide 179 commits = about *6 hours of active development*.
-* If you coded it all yourself, including all the bug fixes, features, design, and documentation, you might spend *10–20 hours*.
+* Say each commit takes Codex 5 minutes to generate, and you need to review/guide 179 commits = about _6 hours of active development_.
+* If you coded it all yourself, including all the bug fixes, features, design, and documentation, you might spend _10–20 hours_.
* That's a couple of days potential savings.
## Conclusion