From cd93bc8c59f8dbc74bd94949aed04c307b9d0dbd Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 22 Jun 2025 19:48:41 +0300 Subject: Update content for html --- about/resources.html | 186 +++++++++++++++++------------------ gemfeed/2025-07-22-task-samurai.html | 4 + gemfeed/atom.xml | 6 +- index.html | 2 +- uptime-stats.html | 2 +- 5 files changed, 104 insertions(+), 96 deletions(-) diff --git a/about/resources.html b/about/resources.html index 5d9a1ec9..382900e8 100644 --- a/about/resources.html +++ b/about/resources.html @@ -50,107 +50,107 @@ In random order:


Technical references



I didn't read them from the beginning to the end, but I am using them to look up things. The books are in random order:


Self-development and soft-skills books



In random order:


Here are notes of mine for some of the books

@@ -159,22 +159,22 @@ Some of these were in-person with exams; others were online learning lectures only. In random order:


Technical guides



@@ -193,57 +193,57 @@

Podcasts I liked



I liked them but am not listening to them anymore. The podcasts have either "finished" (no more episodes) or I stopped listening to them due to time constraints or a shift in my interests.


Newsletters I like



This is a mix of tech and non-tech newsletters I am subscribed to. In random order:


Magazines I like(d)



This is a mix of tech I like(d). I may not be a current subscriber, but now and then, I buy an issue. In random order:


Formal education


diff --git a/gemfeed/2025-07-22-task-samurai.html b/gemfeed/2025-07-22-task-samurai.html index 34331fe8..5add6795 100644 --- a/gemfeed/2025-07-22-task-samurai.html +++ b/gemfeed/2025-07-22-task-samurai.html @@ -70,6 +70,10 @@
As a side note, I was trying out OpenAI Codex because I regularly run out of Claude Code CLI (another agentic coding tool I am trying out currently) credits (it still happens!), but Codex was still available to me. So, I seized the opportunity to push agentic coding a bit more.

+I didn't really love the web UI you have to use for Codex, as I usually live in the terminal. But this is all I have for Codex for now, and I thought I'd give it a try regardless. The web UI is simple and pretty straightforward. There's also a Codex CLI one could use directly in the terminal, but I didn't get it working. I will try again soon.
+
+For every task given to Codex, it spins up its own container. From there, you can drill down and watch what it is doing. At the end, the result (in the form of a code diff) will be presented. From there, you can make suggestions about what else to change in the codebase. Once satisfied, you can ask Codex to create a GitHub PR; from there, you can merge it and then pull it to your local laptop or workstation to test the changes again. I found myself looping a lot around the Codex UI, GitHub PRs, and local checkouts.
+

How it went down



Task Samurai's codebase came together quickly: the entire Git history spans from June 19 to 22, 2025, culminating in 179 commits. Here are the broad strokes:
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 6d5bc86c..07a31c25 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2025-06-22T19:42:04+03:00 + 2025-06-22T19:47:58+03:00 foo.zone feed To be in the .zone! @@ -77,6 +77,10 @@
As a side note, I was trying out OpenAI Codex because I regularly run out of Claude Code CLI (another agentic coding tool I am trying out currently) credits (it still happens!), but Codex was still available to me. So, I seized the opportunity to push agentic coding a bit more.

+I didn't really love the web UI you have to use for Codex, as I usually live in the terminal. But this is all I have for Codex for now, and I thought I'd give it a try regardless. The web UI is simple and pretty straightforward. There's also a Codex CLI one could use directly in the terminal, but I didn't get it working. I will try again soon.
+
+For every task given to Codex, it spins up its own container. From there, you can drill down and watch what it is doing. At the end, the result (in the form of a code diff) will be presented. From there, you can make suggestions about what else to change in the codebase. Once satisfied, you can ask Codex to create a GitHub PR; from there, you can merge it and then pull it to your local laptop or workstation to test the changes again. I found myself looping a lot around the Codex UI, GitHub PRs, and local checkouts.
+

How it went down



Task Samurai's codebase came together quickly: the entire Git history spans from June 19 to 22, 2025, culminating in 179 commits. Here are the broad strokes:
diff --git a/index.html b/index.html index 694a6b83..c7ef2ab7 100644 --- a/index.html +++ b/index.html @@ -13,7 +13,7 @@

Hello!



-This site was generated at 2025-06-22T19:42:04+03:00 by Gemtexter
+This site was generated at 2025-06-22T19:47:58+03:00 by Gemtexter

Welcome to the ...

diff --git a/uptime-stats.html b/uptime-stats.html index 32f34352..72da9491 100644 --- a/uptime-stats.html +++ b/uptime-stats.html @@ -13,7 +13,7 @@

My machine uptime stats



-This site was last updated at 2025-06-22T19:42:04+03:00
+This site was last updated at 2025-06-22T19:47:58+03:00

The following stats were collected via uptimed on all of my personal computers over many years and the output was generated by guprecords, the global uptime records stats analyser of mine.

-- cgit v1.2.3