https://foron.dev/en/tags/learning/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).Hugo -- gohugo.ioenTue, 06 Oct 2026 00:00:00 +0200https://foron.dev/en/blog/macgyver-on-a-raspberry-pi/Tue, 06 Oct 2026 00:00:00 +0200https://foron.dev/en/blog/macgyver-on-a-raspberry-pi/<p>Many of the things that are worth it come from curiosity. Others come from need. What I am telling here sits in the middle of the two.</p> <p>Among so much slop on the internet, I realised I could not keep up with every information channel. It was adapt or die, in the purest Darwinian style. Madafaka.</p> <p>Since the start of August I have been putting everything I read and everything I decide into a folder of text files. Today it holds 471 atomic notes, 333 sources, 79 syntheses and 7 exchanges. An hour ago it held 470 and one fewer, because the system keeps working while I do other things.</p>aihermeslearninghttps://foron.dev/en/blog/the-code-is-solved/Tue, 29 Sep 2026 00:00:00 +0200https://foron.dev/en/blog/the-code-is-solved/<p>The code is solved.</p> <p>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.</p> <p>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.</p>aidevelopmentsdlc