From 925a1fd8f6b62df7c074f8861a20c4d5642ed1b8 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 22 Jun 2025 21:26:45 +0300 Subject: Update content for html --- about/resources.html | 194 +++++++++++++++++------------------ gemfeed/2025-06-22-task-samurai.html | 6 +- gemfeed/atom.xml | 8 +- index.html | 2 +- uptime-stats.html | 22 ++-- 5 files changed, 120 insertions(+), 112 deletions(-) diff --git a/about/resources.html b/about/resources.html index 107f9427..2cf02c6e 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,31 +159,31 @@ Some of these were in-person with exams; others were online learning lectures only. In random order:


Technical guides



These are not whole books, but guides (smaller or larger) which I found very useful. in random order:


Podcasts



@@ -192,30 +192,30 @@ In random order:


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


@@ -223,18 +223,18 @@ This is a mix of tech and non-tech newsletters I am subscribed to. In random order:


Magazines I like(d)



@@ -242,9 +242,9 @@

Formal education



diff --git a/gemfeed/2025-06-22-task-samurai.html b/gemfeed/2025-06-22-task-samurai.html index c83e8136..47b67edc 100644 --- a/gemfeed/2025-06-22-task-samurai.html +++ b/gemfeed/2025-06-22-task-samurai.html @@ -48,6 +48,8 @@
  • I wanted something built with Bubble Tea, but I never had time to dive deep into it.
  • I wanted to build a toy project (like Task Samurai) first, before tackling the big ones, to get started with agentic coding.

    • +https://openai.com/codex/
    +
    Given the current industry trend and the rapid advancements in technology, it has become clear that experimenting with AI-assisted coding tools is almost a necessity to stay relevant. Embracing these new developments doesn't mean abandoning traditional coding; instead, it means integrating new capabilities into your workflow to stay ahead in a fast-evolving field.

    How it works


    @@ -72,7 +74,9 @@
    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.
    +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. What I found inconvenient is that for every additional change, there's an overhead because Codex has to spin up a container again, which adds extra delay. That could be eliminated by setting up predefined custom containers, but that feature still seems to be somewhat limited.
    +
    +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



    diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 91bad51c..8c28a320 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2025-06-22T20:25:46+03:00 + 2025-06-22T21:25:58+03:00 foo.zone feed To be in the .zone! @@ -55,6 +55,8 @@
  • I wanted something built with Bubble Tea, but I never had time to dive deep into it.
  • I wanted to build a toy project (like Task Samurai) first, before tackling the big ones, to get started with agentic coding.

    • +https://openai.com/codex/
    +
    Given the current industry trend and the rapid advancements in technology, it has become clear that experimenting with AI-assisted coding tools is almost a necessity to stay relevant. Embracing these new developments doesn't mean abandoning traditional coding; instead, it means integrating new capabilities into your workflow to stay ahead in a fast-evolving field.

    How it works


    @@ -79,7 +81,9 @@
    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.
    +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. What I found inconvenient is that for every additional change, there's an overhead because Codex has to spin up a container again, which adds extra delay. That could be eliminated by setting up predefined custom containers, but that feature still seems to be somewhat limited.
    +
    +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



    diff --git a/index.html b/index.html index 1118dd1f..efb37402 100644 --- a/index.html +++ b/index.html @@ -13,7 +13,7 @@

    Hello!



    -This site was generated at 2025-06-22T20:25:46+03:00 by Gemtexter
    +This site was generated at 2025-06-22T21:25:58+03:00 by Gemtexter

    Welcome to the ...

    diff --git a/uptime-stats.html b/uptime-stats.html index 2b8461d4..e01629ac 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-22T20:25:46+03:00
    +This site was last updated at 2025-06-22T21:25: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.

    @@ -45,15 +45,15 @@ | 9. | pluto | 51 | Linux 3.2.0-4-amd64 | | 10. | mega15289 | 50 | Darwin 23.4.0 | | 11. | *mega-m3-pro | 49 | Darwin 24.5.0 | -| 12. | *fishfinger | 43 | OpenBSD 7.6 | -| 13. | *t450 | 43 | FreeBSD 14.2-RELEASE | -| 14. | phobos | 40 | Linux 3.4.0-CM-g1dd7cdf | -| 15. | mega8477 | 40 | Darwin 13.4.0 | +| 12. | *t450 | 43 | FreeBSD 14.2-RELEASE | +| 13. | *fishfinger | 43 | OpenBSD 7.6 | +| 14. | mega8477 | 40 | Darwin 13.4.0 | +| 15. | phobos | 40 | Linux 3.4.0-CM-g1dd7cdf | | 16. | *blowfish | 38 | OpenBSD 7.6 | | 17. | sun | 33 | FreeBSD 10.3-RELEASE-p24 | | 18. | *f2 | 25 | FreeBSD 14.2-RELEASE-p1 | -| 19. | *f1 | 20 | FreeBSD 14.2-RELEASE-p1 | -| 20. | moon | 20 | FreeBSD 14.0-RELEASE-p3 | +| 19. | moon | 20 | FreeBSD 14.0-RELEASE-p3 | +| 20. | *f1 | 20 | FreeBSD 14.2-RELEASE-p1 | +-----+----------------+-------+------------------------------+
    @@ -68,7 +68,7 @@ | 1. | vulcan | 4 years, 5 months, 6 days | Linux 3.10.0-1160.81.1.el7.x86_64 | | 2. | sun | 3 years, 9 months, 26 days | FreeBSD 10.3-RELEASE-p24 | | 3. | *uranus | 3 years, 9 months, 5 days | NetBSD 10.1 | -| 4. | *earth | 3 years, 6 months, 10 days | Linux 6.14.6-300.fc42.x86_64 | +| 4. | *earth | 3 years, 6 months, 11 days | Linux 6.14.6-300.fc42.x86_64 | | 5. | *blowfish | 3 years, 5 months, 16 days | OpenBSD 7.6 | | 6. | uugrn | 3 years, 5 months, 5 days | FreeBSD 11.2-RELEASE-p4 | | 7. | deltavega | 3 years, 1 months, 21 days | Linux 3.10.0-1160.11.1.el7.x86_64 | @@ -208,7 +208,7 @@ | 17. | Darwin 22... | 12 | | 18. | Darwin 18... | 11 | | 19. | FreeBSD 7... | 10 | -| 20. | FreeBSD 6... | 10 | +| 20. | OpenBSD 4... | 10 | +-----+----------------+-------+
    @@ -269,8 +269,8 @@ | 16. | Darwin 22... | 30 | | 17. | Darwin 15... | 29 | | 18. | *Darwin 24... | 28 | -| 19. | FreeBSD 13... | 25 | -| 20. | FreeBSD 5... | 25 | +| 19. | FreeBSD 5... | 25 | +| 20. | FreeBSD 13... | 25 | +-----+----------------+-------+
    -- cgit v1.2.3