<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai // foron23</title><link>https://foron.dev/en/tags/ai/</link><description>Portfolio and blog of Iker Foronda: cloud and DevOps engineering (Kubernetes, Terraform, Azure), AI offensive security and LLM red teaming, and full stack development (Python, Node.js, PostgreSQL).</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://foron.dev/en/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>The Code Is Solved. Now What?</title><link>https://foron.dev/en/blog/the-code-is-solved/</link><pubDate>Tue, 29 Sep 2026 00:00:00 +0200</pubDate><guid>https://foron.dev/en/blog/the-code-is-solved/</guid><description>&lt;p&gt;The code is solved.&lt;/p&gt;
&lt;p&gt;Almost. Not quite. What has been solved is one very specific part of the job, the part that used to eat whole afternoons, and what is left is the part nobody ever had to train.&lt;/p&gt;
&lt;p&gt;For years, my job was this loop: write code, compile, run, it does not work, read the error, change one line, start again. A one-line error could take an entire afternoon. It did not matter how well I had thought the design through: if it would not start, there was nothing. There were days when I got nothing done, and the maddening part was never the error. It was the loop.&lt;/p&gt;</description><category>ai</category><category>development</category><category>sdlc</category></item></channel></rss>