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
commita2f7cdfae19e3ba1293de9b735e2a6a3d2e33350 (patch)
tree497343554a67310d98307754d75400bbf6f8d90a /gemfeed
parente18a42738cf7ad1b6cee6aedb2021df388360db7 (diff)
Update content for gemtext
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/2025-07-22-task-samurai.gmi4
-rw-r--r--gemfeed/2025-07-22-task-samurai.gmi.tpl4
-rw-r--r--gemfeed/atom.xml6
3 files changed, 7 insertions, 7 deletions
diff --git a/gemfeed/2025-07-22-task-samurai.gmi b/gemfeed/2025-07-22-task-samurai.gmi
index 40e23d8e..eedbd2e3 100644
--- a/gemfeed/2025-07-22-task-samurai.gmi
+++ b/gemfeed/2025-07-22-task-samurai.gmi
@@ -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
diff --git a/gemfeed/2025-07-22-task-samurai.gmi.tpl b/gemfeed/2025-07-22-task-samurai.gmi.tpl
index 4223a18b..45c0ed84 100644
--- a/gemfeed/2025-07-22-task-samurai.gmi.tpl
+++ b/gemfeed/2025-07-22-task-samurai.gmi.tpl
@@ -88,8 +88,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
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index 077da43a..b0f1c5f4 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:47:58+03:00</updated>
+ <updated>2025-06-22T19:53:43+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" />
@@ -127,8 +127,8 @@
<span>Let&#39;s do some back-of-the-envelope math:</span><br />
<br />
<ul>
-<li>Say each commit takes Codex 5 minutes to generate, and you need to review/guide 179 commits = about *6 hours of active development*.</li>
-<li>If you coded it all yourself, including all the bug fixes, features, design, and documentation, you might spend *10–20 hours*.</li>
+<li>Say each commit takes Codex 5 minutes to generate, and you need to review/guide 179 commits = about _6 hours of active development_.</li>
+<li>If you coded it all yourself, including all the bug fixes, features, design, and documentation, you might spend _10–20 hours_.</li>
<li>That&#39;s a couple of days potential savings.</li>
</ul><br />
<h2 style='display: inline' id='conclusion'>Conclusion</h2><br />