From b4151488cc973e8ed3f507cb850ece7f0d9d40cd Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 23 Jun 2025 01:01:47 +0300 Subject: Update content for html --- about/resources.html | 200 +++++++++++++++++------------------ gemfeed/2025-06-22-task-samurai.html | 5 +- gemfeed/atom.xml | 7 +- index.html | 2 +- uptime-stats.html | 2 +- 5 files changed, 109 insertions(+), 107 deletions(-) diff --git a/about/resources.html b/about/resources.html index 13ae3ef5..1bf043fa 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,58 +192,58 @@ 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



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-06-22-task-samurai.html b/gemfeed/2025-06-22-task-samurai.html index 425468b2..b775f3b1 100644 --- a/gemfeed/2025-06-22-task-samurai.html +++ b/gemfeed/2025-06-22-task-samurai.html @@ -31,7 +31,7 @@
  • ⇢ ⇢ What went wrong
  • ⇢ ⇢ Patterns that helped
  • ⇢ ⇢ What I learned using agentic coding
    • -
  • ⇢ ⇢ How much time did I save?
    • +
  • ⇢ ⇢ how much time did I save?
  • ⇢ Conclusion

    • Introduction


    @@ -117,7 +117,8 @@ 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:

    diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index ed13710a..b3a598aa 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2025-06-23T00:56:54+03:00 + 2025-06-23T01:00:42+03:00 foo.zone feed To be in the .zone! @@ -38,7 +38,7 @@
  • ⇢ ⇢ What went wrong
  • ⇢ ⇢ Patterns that helped
  • ⇢ ⇢ What I learned using agentic coding
    • -
  • ⇢ ⇢ How much time did I save?
    • +
  • ⇢ ⇢ how much time did I save?
  • ⇢ Conclusion

    • Introduction


    @@ -124,7 +124,8 @@ 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:

    diff --git a/index.html b/index.html index 42ebabe6..f7d45c4d 100644 --- a/index.html +++ b/index.html @@ -13,7 +13,7 @@

    Hello!



    -This site was generated at 2025-06-23T00:56:54+03:00 by Gemtexter
    +This site was generated at 2025-06-23T01:00:42+03:00 by Gemtexter

    Welcome to the ...

    diff --git a/uptime-stats.html b/uptime-stats.html index 63476750..ccb62653 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-23T00:56:54+03:00
    +This site was last updated at 2025-06-23T01:00:42+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