diff options
| author | Paul Buetow <paul@buetow.org> | 2025-06-22 19:30:08 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2025-06-22 19:30:08 +0300 |
| commit | cf2372b0057fafb64e551f7a4790be86908538c5 (patch) | |
| tree | 28a89a29db250aa80b42e828c872ca6bb309f099 | |
| parent | f5a785df0ec5b30eb776aaba9df6d1dd710ba74d (diff) | |
Update content for html
| -rw-r--r-- | about/resources.html | 190 | ||||
| -rw-r--r-- | gemfeed/2025-07-22-task-samurai.html | 28 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 30 | ||||
| -rw-r--r-- | index.html | 2 | ||||
| -rw-r--r-- | uptime-stats.html | 2 |
5 files changed, 126 insertions, 126 deletions
diff --git a/about/resources.html b/about/resources.html index 9084a758..90aa859f 100644 --- a/about/resources.html +++ b/about/resources.html @@ -50,52 +50,52 @@ <span>In random order:</span><br /> <br /> <ul> -<li>Go Brain Teasers - Exercise Your Mind; Miki Tebeka; The Pragmatic Programmers</li> -<li>Clusterbau mit Linux-HA; Michael Schwartzkopff; O'Reilly</li> -<li>Think Raku (aka Think Perl 6); Laurent Rosenfeld, Allen B. Downey; O'Reilly</li> -<li>Higher Order Perl; Mark Dominus; Morgan Kaufmann</li> -<li>Leanring eBPF; Liz Rice; O'Reilly</li> -<li>21st Century C: C Tips from the New School; Ben Klemens; O'Reilly</li> -<li>97 things every SRE should know; Emil Stolarsky, Jaime Woo; O'Reilly</li> -<li>The Practise of System and Network Administration; Thomas A. Limoncelli, Christina J. Hogan, Strata R. Chalup; Addison-Wesley Professional Pro Git; Scott Chacon, Ben Straub; Apress</li> -<li>The Pragmatic Programmer; David Thomas; Addison-Wesley</li> -<li>Distributed Systems: Principles and Paradigms; Andrew S. Tanenbaum; Pearson</li> -<li>Amazon Web Services in Action; Michael Wittig and Andreas Wittig; Manning Publications</li> -<li>Tmux 2: Productive Mouse-free Development; Brain P. Hogan; The Pragmatic Programmers </li> -<li>Data Science at the Command Line; Jeroen Janssens; O'Reilly</li> -<li>Raku Recipes; J.J. Merelo; Apress</li> -<li>The DevOps Handbook; Gene Kim, Jez Humble, Patrick Debois, John Willis; Audible</li> -<li>Effective awk programming; Arnold Robbins; O'Reilly</li> <li>Site Reliability Engineering; How Google runs production systems; O'Reilly</li> +<li>Funktionale Programmierung; Peter Pepper; Springer</li> +<li>Higher Order Perl; Mark Dominus; Morgan Kaufmann</li> <li>The KCNA (Kubernetes and Cloud Native Associate) Book; Nigel Poulton</li> +<li>Effective Java; Joshua Bloch; Addison-Wesley Professional</li> <li>Ultimate Go Notebook; Bill Kennedy</li> -<li>Funktionale Programmierung; Peter Pepper; Springer</li> -<li>Raku Fundamentals; Moritz Lenz; Apress</li> -<li>Modern Perl; Chromatic ; Onyx Neon Press</li> +<li>Amazon Web Services in Action; Michael Wittig and Andreas Wittig; Manning Publications</li> <li>Pro Puppet; James Turnbull, Jeffrey McCune; Apress</li> -<li>Learn You Some Erlang for Great Good; Fred Herbert; No Starch Press</li> -<li>Developing Games in Java; David Brackeen and others...; New Riders</li> -<li>Systems Performance Tuning; Gian-Paolo D. Musumeci and others...; O'Reilly</li> -<li>The Docker Book; James Turnbull; Kindle</li> -<li>Learn You a Haskell for Great Good!; Miran Lipovaca; No Starch Press</li> +<li>The Pragmatic Programmer; David Thomas; Addison-Wesley</li> +<li>DNS and BIND; Cricket Liu; O'Reilly</li> <li>Programming Ruby 3.3 (5th Edition); Noel Rappin, with Dave Thomas; The Pragmatic Bookshelf</li> +<li>Developing Games in Java; David Brackeen and others...; New Riders</li> <li>Polished Ruby Programming; Jeremy Evans; Packt Publishing</li> -<li>Effective Java; Joshua Bloch; Addison-Wesley Professional</li> -<li>Concurrency in Go; Katherine Cox-Buday; O'Reilly</li> -<li>100 Go Mistakes and How to Avoid Them; Teiva Harsanyi; Manning Publications</li> -<li>DNS and BIND; Cricket Liu; O'Reilly</li> -<li>Hands-on Infrastructure Monitoring with Prometheus; Joel Bastos, Pedro Araujo; Packt </li> -<li>Java ist auch eine Insel; Christian Ullenboom; </li> +<li>Data Science at the Command Line; Jeroen Janssens; O'Reilly</li> +<li>Learn You Some Erlang for Great Good; Fred Herbert; No Starch Press</li> +<li>The Kubernetes Book; Nigel Poulton; Unabridged Audiobook</li> +<li>Systemprogrammierung in Go; Frank Müller; dpunkt</li> <li>DevOps And Site Reliability Engineering Handbook; Stephen Fleming; Audible</li> +<li>Hands-on Infrastructure Monitoring with Prometheus; Joel Bastos, Pedro Araujo; Packt </li> <li>The Go Programming Language; Alan A. A. Donovan; Addison-Wesley Professional</li> -<li>Systemprogrammierung in Go; Frank Müller; dpunkt</li> -<li>Perl New Features; Joshua McAdams, brian d foy; Perl School</li> -<li>Programming Perl aka "The Camel Book"; Tom Christiansen, brian d foy, Larry Wall & Jon Orwant; O'Reilly</li> -<li>Object-Oriented Programming with ANSI-C; Axel-Tobias Schreiner</li> -<li>The Kubernetes Book; Nigel Poulton; Unabridged Audiobook</li> <li>C++ Programming Language; Bjarne Stroustrup;</li> -<li>Terraform Cookbook; Mikael Krief; Packt Publishing</li> +<li>Modern Perl; Chromatic ; Onyx Neon Press</li> +<li>Distributed Systems: Principles and Paradigms; Andrew S. Tanenbaum; Pearson</li> +<li>Learn You a Haskell for Great Good!; Miran Lipovaca; No Starch Press</li> +<li>Go Brain Teasers - Exercise Your Mind; Miki Tebeka; The Pragmatic Programmers</li> +<li>Think Raku (aka Think Perl 6); Laurent Rosenfeld, Allen B. Downey; O'Reilly</li> +<li>Object-Oriented Programming with ANSI-C; Axel-Tobias Schreiner</li> +<li>Clusterbau mit Linux-HA; Michael Schwartzkopff; O'Reilly</li> +<li>Systems Performance Tuning; Gian-Paolo D. Musumeci and others...; O'Reilly</li> <li>Kubernetes Cookbook; Sameer Naik, Sébastien Goasguen, Jonathan Michaux; O'Reilly</li> +<li>97 things every SRE should know; Emil Stolarsky, Jaime Woo; O'Reilly</li> +<li>Programming Perl aka "The Camel Book"; Tom Christiansen, brian d foy, Larry Wall & Jon Orwant; O'Reilly</li> +<li>Concurrency in Go; Katherine Cox-Buday; O'Reilly</li> +<li>Leanring eBPF; Liz Rice; O'Reilly</li> +<li>21st Century C: C Tips from the New School; Ben Klemens; O'Reilly</li> +<li>100 Go Mistakes and How to Avoid Them; Teiva Harsanyi; Manning Publications</li> +<li>Perl New Features; Joshua McAdams, brian d foy; Perl School</li> +<li>Java ist auch eine Insel; Christian Ullenboom; </li> +<li>Effective awk programming; Arnold Robbins; O'Reilly</li> +<li>Raku Recipes; J.J. Merelo; Apress</li> +<li>The DevOps Handbook; Gene Kim, Jez Humble, Patrick Debois, John Willis; Audible</li> +<li>The Docker Book; James Turnbull; Kindle</li> +<li>The Practise of System and Network Administration; Thomas A. Limoncelli, Christina J. Hogan, Strata R. Chalup; Addison-Wesley Professional Pro Git; Scott Chacon, Ben Straub; Apress</li> +<li>Raku Fundamentals; Moritz Lenz; Apress</li> +<li>Terraform Cookbook; Mikael Krief; Packt Publishing</li> +<li>Tmux 2: Productive Mouse-free Development; Brain P. Hogan; The Pragmatic Programmers </li> </ul><br /> <h2 style='display: inline' id='technical-references'>Technical references</h2><br /> <br /> @@ -103,54 +103,54 @@ <br /> <ul> <li>Go: Design Patterns for Real-World Projects; Mat Ryer; Packt</li> -<li>Implementing Service Level Objectives; Alex Hidalgo; O'Reilly</li> -<li>Groovy Kurz & Gut; Joerg Staudemeier; O'Reilly</li> -<li>Relayd and Httpd Mastery; Michael W Lucas</li> <li>Algorithms; Robert Sedgewick, Kevin Wayne; Addison Wesley</li> +<li>Groovy Kurz & Gut; Joerg Staudemeier; O'Reilly</li> <li>Understanding the Linux Kernel; Daniel P. Bovet, Marco Cesati; O'Reilly</li> <li>The Linux Programming Interface; Michael Kerrisk; No Starch Press </li> +<li>Relayd and Httpd Mastery; Michael W Lucas</li> <li>BPF Performance Tools - Linux System and Application Observability, Brendan Gregg; Addison Wesley</li> +<li>Implementing Service Level Objectives; Alex Hidalgo; O'Reilly</li> </ul><br /> <h2 style='display: inline' id='self-development-and-soft-skills-books'>Self-development and soft-skills books</h2><br /> <br /> <span>In random order:</span><br /> <br /> <ul> -<li>Digital Minimalism; Cal Newport; Portofolio Penguin</li> -<li>Staff Engineer: Leadership beyond the management track; Will Larson; Audiobook</li> -<li>Ultralearning; Scott Young; Thorsons</li> -<li>The Joy of Missing Out; Christina Crook; New Society Publishers</li> -<li>The Phoenix Project - A Novel About IT, DevOps, and Helping your Business Win; Gene Kim and Kevin Behr; Trade Select</li> -<li>Coders at Work - Reflections on the craft of programming, Peter Seibel and Mitchell Dorian et al., Audiobook</li> -<li>So Good They Can't Ignore You; Cal Newport; Business Plus</li> -<li>101 Essays that change the way you think; Brianna Wiest; Audiobook</li> <li>Search Inside Yourself - The Unexpected path to Achieving Success, Happiness (and World Peace); Chade-Meng Tan, Daniel Goleman, Jon Kabat-Zinn; HarperOne</li> -<li>The Complete Software Developer's Career Guide; John Sonmez; Unabridged Audiobook</li> +<li>The Power of Now; Eckhard Tolle; Yellow Kite</li> <li>Eat That Frog; Brian Tracy</li> -<li>The Good Enough Job; Simone Stolzoff; Ebury Edge</li> -<li>Deep Work; Cal Newport; Piatkus</li> -<li>The Obstacle Is The Way; Ryan Holiday; Profile Books Ltd</li> -<li>Who Moved My Cheese?; Dr. Spencer Johnson; Vermilion</li> +<li>The Daily Stoic; Ryan Holiday, Stephen Hanselman; Profile Books</li> +<li>Slow Productivity; Cal Newport; Penguin Random House</li> +<li>So Good They Can't Ignore You; Cal Newport; Business Plus</li> +<li>The Joy of Missing Out; Christina Crook; New Society Publishers</li> +<li>The Complete Software Developer's Career Guide; John Sonmez; Unabridged Audiobook</li> +<li>Solve for Happy; Mo Gawdat (RE-READ 1ST TIME)</li> +<li>Staff Engineer: Leadership beyond the management track; Will Larson; Audiobook</li> +<li>Ultralearning; Scott Young; Thorsons</li> +<li>The 7 Habits Of Highly Effective People; Stephen R. Covey; Simon & Schuster UK</li> +<li>Stop starting, start finishing; Arne Roock; Lean-Kanban University </li> <li>The Off Switch; Mark Cropley; Virgin Books (RE-READ 1ST TIME)</li> +<li>Ultralearning; Anna Laurent; Self-published via Amazon</li> +<li>Never Split the Difference; Chris Voss, Tahl Raz; Random House Business</li> +<li>The Phoenix Project - A Novel About IT, DevOps, and Helping your Business Win; Gene Kim and Kevin Behr; Trade Select</li> <li>Consciousness: A Very Short Introduction; Susan Blackmore; Oxford Uiversity Press</li> -<li>Influence without Authority; A. Cohen, D. Bradford; Wiley</li> +<li>Soft Skills; John Sommez; Manning Publications</li> <li>Meditation for Mortals, Oliver Burkeman, Audiobook</li> -<li>Time Management for System Administrators; Thomas A. Limoncelli; O'Reilly</li> -<li>Stop starting, start finishing; Arne Roock; Lean-Kanban University </li> +<li>The Good Enough Job; Simone Stolzoff; Ebury Edge</li> <li>Eat That Frog!; Brian Tracy; Hodder Paperbacks</li> -<li>The 7 Habits Of Highly Effective People; Stephen R. Covey; Simon & Schuster UK</li> -<li>The Daily Stoic; Ryan Holiday, Stephen Hanselman; Profile Books</li> -<li>Never Split the Difference; Chris Voss, Tahl Raz; Random House Business</li> -<li>Getting Things Done; David Allen</li> -<li>Solve for Happy; Mo Gawdat (RE-READ 1ST TIME)</li> -<li>The Power of Now; Eckhard Tolle; Yellow Kite</li> +<li>Coders at Work - Reflections on the craft of programming, Peter Seibel and Mitchell Dorian et al., Audiobook</li> +<li>Time Management for System Administrators; Thomas A. Limoncelli; O'Reilly</li> +<li>Buddah and Einstein walk into a Bar; Guy Joseph Ale, Claire Bloom; Blackstone Publishing</li> +<li>Digital Minimalism; Cal Newport; Portofolio Penguin</li> +<li>The Obstacle Is The Way; Ryan Holiday; Profile Books Ltd</li> <li>Atomic Habits; James Clear; Random House Business</li> -<li>Ultralearning; Anna Laurent; Self-published via Amazon</li> <li>The Bullet Journal Method; Ryder Carroll; Fourth Estate</li> +<li>101 Essays that change the way you think; Brianna Wiest; Audiobook</li> +<li>Deep Work; Cal Newport; Piatkus</li> <li>Psycho-Cybernetics; Maxwell Maltz; Perigee Books</li> -<li>Soft Skills; John Sommez; Manning Publications</li> -<li>Slow Productivity; Cal Newport; Penguin Random House</li> -<li>Buddah and Einstein walk into a Bar; Guy Joseph Ale, Claire Bloom; Blackstone Publishing</li> +<li>Influence without Authority; A. Cohen, D. Bradford; Wiley</li> +<li>Getting Things Done; David Allen</li> +<li>Who Moved My Cheese?; Dr. Spencer Johnson; Vermilion</li> </ul><br /> <a class='textlink' href='../notes/index.html'>Here are notes of mine for some of the books</a><br /> <br /> @@ -159,22 +159,22 @@ <span>Some of these were in-person with exams; others were online learning lectures only. In random order:</span><br /> <br /> <ul> -<li>Developing IaC with Terraform (with Live Lessons); O'Reilly Online</li> -<li>Algorithms Video Lectures; Robert Sedgewick; O'Reilly Online</li> +<li>Functional programming lecture; Remote University of Hagen</li> <li>Protocol buffers; O'Reilly Online</li> +<li>Developing IaC with Terraform (with Live Lessons); O'Reilly Online</li> +<li>MySQL Deep Dive Workshop; 2-day on-site training</li> <li>F5 Loadbalancers Training; 2-day on-site training; F5, Inc. </li> +<li>Cloud Operations on AWS - Learn how to configure, deploy, maintain, and troubleshoot your AWS environments; 3-day online live training with labs; Amazon</li> <li>Structure and Interpretation of Computer Programs; Harold Abelson and more...; </li> -<li>MySQL Deep Dive Workshop; 2-day on-site training</li> -<li>Red Hat Certified System Administrator; Course + certification (Although I had the option, I decided not to take the next course as it is more effective to self learn what I need)</li> <li>AWS Immersion Day; Amazon; 1-day interactive online training </li> -<li>The Well-Grounded Rubyist Video Edition; David. A. Black; O'Reilly Online</li> <li>Apache Tomcat Best Practises; 3-day on-site training</li> -<li>Functional programming lecture; Remote University of Hagen</li> -<li>Ultimate Go Programming; Bill Kennedy; O'Reilly Online</li> +<li>Red Hat Certified System Administrator; Course + certification (Although I had the option, I decided not to take the next course as it is more effective to self learn what I need)</li> +<li>The Well-Grounded Rubyist Video Edition; David. A. Black; O'Reilly Online</li> +<li>Algorithms Video Lectures; Robert Sedgewick; O'Reilly Online</li> <li>Linux Security and Isolation APIs Training; Michael Kerrisk; 3-day on-site training</li> -<li>Scripting Vim; Damian Conway; O'Reilly Online</li> +<li>Ultimate Go Programming; Bill Kennedy; O'Reilly Online</li> <li>The Ultimate Kubernetes Bootcamp; School of Devops; O'Reilly Online</li> -<li>Cloud Operations on AWS - Learn how to configure, deploy, maintain, and troubleshoot your AWS environments; 3-day online live training with labs; Amazon</li> +<li>Scripting Vim; Damian Conway; O'Reilly Online</li> </ul><br /> <h2 style='display: inline' id='technical-guides'>Technical guides</h2><br /> <br /> @@ -182,8 +182,8 @@ <br /> <ul> <li>How CPUs work at https://cpu.land</li> -<li>Raku Guide at https://raku.guide </li> <li>Advanced Bash-Scripting Guide </li> +<li>Raku Guide at https://raku.guide </li> </ul><br /> <h2 style='display: inline' id='podcasts'>Podcasts</h2><br /> <br /> @@ -192,59 +192,59 @@ <span>In random order:</span><br /> <br /> <ul> -<li>Deep Questions with Cal Newport</li> -<li>Cup o' Go [Golang]</li> <li>Fork Around And Find Out</li> -<li>BSD Now [BSD]</li> -<li>The Changelog Podcast(s)</li> -<li>Hidden Brain</li> <li>Dev Interrupted</li> +<li>Modern Mentor</li> <li>Maintainable</li> +<li>Cup o' Go [Golang]</li> +<li>Fallthrough [Golang]</li> +<li>BSD Now [BSD]</li> +<li>The Changelog Podcast(s)</li> <li>The ProdCast (Google SRE Podcast)</li> <li>Backend Banter</li> -<li>Fallthrough [Golang]</li> -<li>Modern Mentor</li> +<li>Hidden Brain</li> <li>The Pragmatic Engineer Podcast</li> +<li>Deep Questions with Cal Newport</li> </ul><br /> <h3 style='display: inline' id='podcasts-i-liked'>Podcasts I liked</h3><br /> <br /> <span>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.</span><br /> <br /> <ul> -<li>Modern Mentor</li> -<li>Java Pub House</li> -<li>Go Time (predecessor of fallthrough)</li> -<li>CRE: Chaosradio Express [german]</li> <li>FLOSS weekly</li> <li>Ship It (predecessor of Fork Around And Find Out)</li> +<li>CRE: Chaosradio Express [german]</li> +<li>Go Time (predecessor of fallthrough)</li> +<li>Java Pub House</li> +<li>Modern Mentor</li> </ul><br /> <h2 style='display: inline' id='newsletters-i-like'>Newsletters I like</h2><br /> <br /> <span>This is a mix of tech and non-tech newsletters I am subscribed to. In random order:</span><br /> <br /> <ul> -<li>Andreas Brandhorst Newsletter (Sci-Fi author)</li> -<li>Changelog News</li> -<li>byteSizeGo</li> <li>The Imperfectionist</li> -<li>Golang Weekly</li> -<li>Ruby Weekly</li> -<li>Applied Go Weekly Newsletter</li> <li>The Valuable Dev</li> +<li>Andreas Brandhorst Newsletter (Sci-Fi author)</li> +<li>byteSizeGo</li> <li>Monospace Mentor</li> +<li>Changelog News</li> +<li>Applied Go Weekly Newsletter</li> +<li>Register Spill</li> +<li>Golang Weekly</li> <li>VK Newsletter</li> <li>The Pragmatic Engineer</li> -<li>Register Spill</li> +<li>Ruby Weekly</li> </ul><br /> <h2 style='display: inline' id='magazines-i-liked'>Magazines I like(d)</h2><br /> <br /> <span>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:</span><br /> <br /> <ul> -<li>Linux Magazine</li> -<li>Linux User</li> <li>LWN (online only)</li> <li>freeX (not published anymore)</li> +<li>Linux User</li> +<li>Linux Magazine</li> </ul><br /> <h1 style='display: inline' id='formal-education'>Formal education</h1><br /> <br /> diff --git a/gemfeed/2025-07-22-task-samurai.html b/gemfeed/2025-07-22-task-samurai.html index 7f00b03a..8b385eb3 100644 --- a/gemfeed/2025-07-22-task-samurai.html +++ b/gemfeed/2025-07-22-task-samurai.html @@ -26,12 +26,12 @@ <li>⇢ ⇢ <a href='#how-it-works'>How it works</a></li> <li>⇢ <a href='#where-and-how-to-get-it'>Where and how to get it</a></li> <li>⇢ <a href='#lessons-learned-from-building-task-samurai-with-agentic-coding'>Lessons Learned from Building Task Samurai with Agentic Coding</a></li> -<li>⇢ ⇢ <a href='#how-it-went-down'>How It Went Down</a></li> -<li>⇢ ⇢ <a href='#what-went-wrong'>What Went Wrong</a></li> -<li>⇢ ⇢ <a href='#patterns-that-helped'>Patterns That Helped</a></li> -<li>⇢ ⇢ <a href='#what-i-learned-using-agentic-coding'>What I Learned Using Agentic Coding</a></li> -<li>⇢ ⇢ <a href='#how-much-time-did-i-save'>How Much Time Did I Save?</a></li> -<li>⇢ <a href='#wrapping-up'>Wrapping Up</a></li> +<li>⇢ ⇢ <a href='#how-it-went-down'>How it went down</a></li> +<li>⇢ ⇢ <a href='#what-went-wrong'>What went wrong</a></li> +<li>⇢ ⇢ <a href='#patterns-hhat-helped'>Patterns hhat helped</a></li> +<li>⇢ ⇢ <a href='#what-i-learned-using-agentic-coding'>What I learned using agentic coding</a></li> +<li>⇢ ⇢ <a href='#how-much-time-did-i-save'>How much time did I save?</a></li> +<li>⇢ <a href='#conclusion'>Conclusion</a></li> </ul><br /> <h2 style='display: inline' id='introduction'>Introduction</h2><br /> <br /> @@ -70,7 +70,7 @@ <br /> <span>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.</span><br /> <br /> -<h3 style='display: inline' id='how-it-went-down'>How It Went Down</h3><br /> +<h3 style='display: inline' id='how-it-went-down'>How it went down</h3><br /> <br /> <span>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:</span><br /> <br /> @@ -82,7 +82,7 @@ </ul><br /> <span>Most big breakthroughs (and bug introductions) came during that middle day of intense iteration. The latter stages were all about smoothing out the rough edges.</span><br /> <br /> -<h3 style='display: inline' id='what-went-wrong'>What Went Wrong</h3><br /> +<h3 style='display: inline' id='what-went-wrong'>What went wrong</h3><br /> <br /> <span>Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons:</span><br /> <br /> @@ -90,7 +90,7 @@ <li>Merge Floods: Every minor feature or fix existed on its branch, so merging was a constant process. It kept progress flowing but also drowned the committed history in noise and the occasional conflict. I found this to be an issue with OpenAI's Codex in particular. Not so much with other agentic coding tools like Claude Code CLI (not covered in this blog post.)</li> <li>Fixes on Fixes: Features like "fireworks on exit" had chains of "fix exit," "fix cell selection," etc. Sometimes, new additions introduced bugs that needed rapid patching.</li> </ul><br /> -<h3 style='display: inline' id='patterns-that-helped'>Patterns That Helped</h3><br /> +<h3 style='display: inline' id='patterns-hhat-helped'>Patterns hhat helped</h3><br /> <br /> <span>Despite the chaos, a few strategies kept things moving:</span><br /> <br /> @@ -101,13 +101,13 @@ <li>Live Documentation: Documentation, such as the README, is updated regularly to reflect all the hotkey and feature changes.</li> </ul><br /> <br /> -<h3 style='display: inline' id='what-i-learned-using-agentic-coding'>What I Learned Using Agentic Coding</h3><br /> +<h3 style='display: inline' id='what-i-learned-using-agentic-coding'>What I learned using agentic coding</h3><br /> <br /> <span>Stepping into agentic coding with Codex as my "pair programmer" was a genuine shift. I learned a ton—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. </span><br /> <br /> <span>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. I now see agentic coding not just as a productivity tool but also as a learning accelerator.</span><br /> <br /> -<h3 style='display: inline' id='how-much-time-did-i-save'>How Much Time Did I Save?</h3><br /> +<h3 style='display: inline' id='how-much-time-did-i-save'>How much time did I save?</h3><br /> <br /> <span>Here's the million-dollar (or many hours saved) question: Did it buy me speed?</span><br /> <br /> @@ -116,15 +116,15 @@ <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>That's a potential savings, so what's usually weeks of work got compressed into just a few frantic days.</li> +<li>That's a couple of days potential savings.</li> </ul><br /> -<h2 style='display: inline' id='wrapping-up'>Wrapping Up</h2><br /> +<h2 style='display: inline' id='conclusion'>Conclusion</h2><br /> <br /> <span>Building Task Samurai with agentic coding was a wild ride—rapid feature growth, plenty of churns, countless fast fixes, and more merge commits I'd expected. The big lessons? Keep the iterations short (or maybe in my next experiment, much larger, with better and more complete design before generating a single line of code), keep tests and documentation concise, and review and refine for final polish at the end. Even with the bumps along the way, shipping a polished terminal UI in days instead of weeks is a testament to the raw power (and some hazards) of agentic development.</span><br /> <br /> <span>Am I an agentic coding expert now? I don't think so. There are still many things to learn, and the landscape is constantly evolving.</span><br /> <br /> -<span>While working on Task Samuray, there were times I genuinely missed manual coding and the satisfaction that comes from writing every line yourself, debugging issues through sheer logic, and crafting solutions from scratch. However, this is the direction in which the industry seems to be shifting, unfortunately. If applied correctly, AI will boost performance, and if you don't use AI, your next performance review may be awkward.</span><br /> +<span>While working on Task Samurai, there were times I genuinely missed manual coding and the satisfaction that comes from writing every line yourself, debugging issues through sheer logic, and crafting solutions from scratch. However, this is the direction in which the industry seems to be shifting, unfortunately. If applied correctly, AI will boost performance, and if you don't use AI, your next performance review may be awkward.</span><br /> <br /> <span>If you're considering going agentic, be prepared for a sprint, keep your toolkit sharp, and be ready to learn a lot along the way.</span><br /> <br /> diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 31aacc89..a3b9d2bd 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:12:10+03:00</updated> + <updated>2025-06-22T19:29:25+03:00</updated> <title>foo.zone feed</title> <subtitle>To be in the .zone!</subtitle> <link href="https://foo.zone/gemfeed/atom.xml" rel="self" /> @@ -33,12 +33,12 @@ <li>⇢ ⇢ <a href='#how-it-works'>How it works</a></li> <li>⇢ <a href='#where-and-how-to-get-it'>Where and how to get it</a></li> <li>⇢ <a href='#lessons-learned-from-building-task-samurai-with-agentic-coding'>Lessons Learned from Building Task Samurai with Agentic Coding</a></li> -<li>⇢ ⇢ <a href='#how-it-went-down'>How It Went Down</a></li> -<li>⇢ ⇢ <a href='#what-went-wrong'>What Went Wrong</a></li> -<li>⇢ ⇢ <a href='#patterns-that-helped'>Patterns That Helped</a></li> -<li>⇢ ⇢ <a href='#what-i-learned-using-agentic-coding'>What I Learned Using Agentic Coding</a></li> -<li>⇢ ⇢ <a href='#how-much-time-did-i-save'>How Much Time Did I Save?</a></li> -<li>⇢ <a href='#wrapping-up'>Wrapping Up</a></li> +<li>⇢ ⇢ <a href='#how-it-went-down'>How it went down</a></li> +<li>⇢ ⇢ <a href='#what-went-wrong'>What went wrong</a></li> +<li>⇢ ⇢ <a href='#patterns-hhat-helped'>Patterns hhat helped</a></li> +<li>⇢ ⇢ <a href='#what-i-learned-using-agentic-coding'>What I learned using agentic coding</a></li> +<li>⇢ ⇢ <a href='#how-much-time-did-i-save'>How much time did I save?</a></li> +<li>⇢ <a href='#conclusion'>Conclusion</a></li> </ul><br /> <h2 style='display: inline' id='introduction'>Introduction</h2><br /> <br /> @@ -77,7 +77,7 @@ <br /> <span>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.</span><br /> <br /> -<h3 style='display: inline' id='how-it-went-down'>How It Went Down</h3><br /> +<h3 style='display: inline' id='how-it-went-down'>How it went down</h3><br /> <br /> <span>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:</span><br /> <br /> @@ -89,7 +89,7 @@ </ul><br /> <span>Most big breakthroughs (and bug introductions) came during that middle day of intense iteration. The latter stages were all about smoothing out the rough edges.</span><br /> <br /> -<h3 style='display: inline' id='what-went-wrong'>What Went Wrong</h3><br /> +<h3 style='display: inline' id='what-went-wrong'>What went wrong</h3><br /> <br /> <span>Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons:</span><br /> <br /> @@ -97,7 +97,7 @@ <li>Merge Floods: Every minor feature or fix existed on its branch, so merging was a constant process. It kept progress flowing but also drowned the committed history in noise and the occasional conflict. I found this to be an issue with OpenAI's Codex in particular. Not so much with other agentic coding tools like Claude Code CLI (not covered in this blog post.)</li> <li>Fixes on Fixes: Features like "fireworks on exit" had chains of "fix exit," "fix cell selection," etc. Sometimes, new additions introduced bugs that needed rapid patching.</li> </ul><br /> -<h3 style='display: inline' id='patterns-that-helped'>Patterns That Helped</h3><br /> +<h3 style='display: inline' id='patterns-hhat-helped'>Patterns hhat helped</h3><br /> <br /> <span>Despite the chaos, a few strategies kept things moving:</span><br /> <br /> @@ -108,13 +108,13 @@ <li>Live Documentation: Documentation, such as the README, is updated regularly to reflect all the hotkey and feature changes.</li> </ul><br /> <br /> -<h3 style='display: inline' id='what-i-learned-using-agentic-coding'>What I Learned Using Agentic Coding</h3><br /> +<h3 style='display: inline' id='what-i-learned-using-agentic-coding'>What I learned using agentic coding</h3><br /> <br /> <span>Stepping into agentic coding with Codex as my "pair programmer" was a genuine shift. I learned a ton—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. </span><br /> <br /> <span>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. I now see agentic coding not just as a productivity tool but also as a learning accelerator.</span><br /> <br /> -<h3 style='display: inline' id='how-much-time-did-i-save'>How Much Time Did I Save?</h3><br /> +<h3 style='display: inline' id='how-much-time-did-i-save'>How much time did I save?</h3><br /> <br /> <span>Here's the million-dollar (or many hours saved) question: Did it buy me speed?</span><br /> <br /> @@ -123,15 +123,15 @@ <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>That's a potential savings, so what's usually weeks of work got compressed into just a few frantic days.</li> +<li>That's a couple of days potential savings.</li> </ul><br /> -<h2 style='display: inline' id='wrapping-up'>Wrapping Up</h2><br /> +<h2 style='display: inline' id='conclusion'>Conclusion</h2><br /> <br /> <span>Building Task Samurai with agentic coding was a wild ride—rapid feature growth, plenty of churns, countless fast fixes, and more merge commits I'd expected. The big lessons? Keep the iterations short (or maybe in my next experiment, much larger, with better and more complete design before generating a single line of code), keep tests and documentation concise, and review and refine for final polish at the end. Even with the bumps along the way, shipping a polished terminal UI in days instead of weeks is a testament to the raw power (and some hazards) of agentic development.</span><br /> <br /> <span>Am I an agentic coding expert now? I don't think so. There are still many things to learn, and the landscape is constantly evolving.</span><br /> <br /> -<span>While working on Task Samuray, there were times I genuinely missed manual coding and the satisfaction that comes from writing every line yourself, debugging issues through sheer logic, and crafting solutions from scratch. However, this is the direction in which the industry seems to be shifting, unfortunately. If applied correctly, AI will boost performance, and if you don't use AI, your next performance review may be awkward.</span><br /> +<span>While working on Task Samurai, there were times I genuinely missed manual coding and the satisfaction that comes from writing every line yourself, debugging issues through sheer logic, and crafting solutions from scratch. However, this is the direction in which the industry seems to be shifting, unfortunately. If applied correctly, AI will boost performance, and if you don't use AI, your next performance review may be awkward.</span><br /> <br /> <span>If you're considering going agentic, be prepared for a sprint, keep your toolkit sharp, and be ready to learn a lot along the way.</span><br /> <br /> @@ -13,7 +13,7 @@ </p> <h1 style='display: inline' id='hello'>Hello!</h1><br /> <br /> -<span class='quote'>This site was generated at 2025-06-22T19:24:30+03:00 by <span class='inlinecode'>Gemtexter</span></span><br /> +<span class='quote'>This site was generated at 2025-06-22T19:29:25+03:00 by <span class='inlinecode'>Gemtexter</span></span><br /> <br /> <span>Welcome to the ...</span><br /> <br /> diff --git a/uptime-stats.html b/uptime-stats.html index 7b15e507..1aca75fd 100644 --- a/uptime-stats.html +++ b/uptime-stats.html @@ -13,7 +13,7 @@ </p> <h1 style='display: inline' id='my-machine-uptime-stats'>My machine uptime stats</h1><br /> <br /> -<span class='quote'>This site was last updated at 2025-06-22T19:24:30+03:00</span><br /> +<span class='quote'>This site was last updated at 2025-06-22T19:29:25+03:00</span><br /> <br /> <span>The following stats were collected via <span class='inlinecode'>uptimed</span> on all of my personal computers over many years and the output was generated by <span class='inlinecode'>guprecords</span>, the global uptime records stats analyser of mine.</span><br /> <br /> |