<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development on Antonio Cortés (DrZippie)</title><link>https://antoniocortes.com/tags/development/</link><description>Recent content in Development on Antonio Cortés (DrZippie)</description><generator>Hugo</generator><language>es-es</language><lastBuildDate>Mon, 30 Mar 2026 10:26:28 +0200</lastBuildDate><atom:link href="https://antoniocortes.com/tags/development/index.xml" rel="self" type="application/rss+xml"/><item><title>Auto Memory and Auto Dream: how Claude Code learns and consolidates its memory</title><link>https://antoniocortes.com/en/post/2026/03/2026-03-30-claude-code-auto-dream-consolidated-memory/</link><pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2026/03/2026-03-30-claude-code-auto-dream-consolidated-memory/</guid><description>&lt;p&gt;If you&amp;rsquo;ve been using Claude Code with Auto Memory enabled for a while, you&amp;rsquo;ve probably noticed that after several sessions, Claude&amp;rsquo;s notes about your project start accumulating contradictions. Entries saying &amp;ldquo;yesterday we decided to use Redis&amp;rdquo; without specifying which day &amp;ldquo;yesterday&amp;rdquo; was. Debugging notes referencing files that no longer exist. Three different entries about the same build quirk. What started as a useful notebook becomes noise.&lt;/p&gt;
&lt;p&gt;Anthropic has just released &lt;strong&gt;Auto Dream&lt;/strong&gt;, a feature that does exactly what its name suggests: it consolidates Claude Code&amp;rsquo;s memory the way the human brain consolidates memories during REM sleep.&lt;/p&gt;</description></item><item><title>Claude Code with LSP: from searching text to understanding code</title><link>https://antoniocortes.com/en/post/2026/03/2026-03-10-claude-code-lsp-upgrade-code-navigation/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2026/03/2026-03-10-claude-code-lsp-upgrade-code-navigation/</guid><description>&lt;p&gt;I have been using Claude Code daily for months, and there is one configuration that has completely changed how it works with my code. It is not a new plugin, a more powerful model, or a magic prompt. It is something that has existed since 2016 and that most developers use without knowing it every time they open VS Code: the Language Server Protocol (LSP).&lt;/p&gt;
&lt;p&gt;&lt;a href="https://karanbansal.in/blog/claude-code-lsp/"&gt;Karan Bansal published an excellent article&lt;/a&gt; explaining in detail how to enable LSP in Claude Code and why it matters. After trying it, I can confirm the difference is real and significant.&lt;/p&gt;</description></item><item><title>AI Coding Agents: Rules, Commands, Skills, MCP and Hooks Explained</title><link>https://antoniocortes.com/en/post/2026/02/ai-coding-agents-conceptos-clave/</link><pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2026/02/ai-coding-agents-conceptos-clave/</guid><description>&lt;p&gt;If you&amp;rsquo;re using tools like Claude Code, GitHub Copilot Workspace, or similar, you&amp;rsquo;ve probably noticed there&amp;rsquo;s technical jargon that goes beyond simply &amp;ldquo;chatting with AI&amp;rdquo;. I&amp;rsquo;m talking about terms like &lt;strong&gt;rules&lt;/strong&gt;, &lt;strong&gt;commands&lt;/strong&gt;, &lt;strong&gt;skills&lt;/strong&gt;, &lt;strong&gt;MCP&lt;/strong&gt;, and &lt;strong&gt;hooks&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;These concepts are the architecture that makes AI agents truly useful for software development. They&amp;rsquo;re not just fancy marketing words — each one serves a specific function in how the agent works.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s break them down one by one in a clear way.&lt;/p&gt;</description></item><item><title>Are We Outsourcing Our Thinking? Reflections on AI and Cognition</title><link>https://antoniocortes.com/are-we-outsourcing-our-thinking/</link><pubDate>Sat, 31 Jan 2026 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/are-we-outsourcing-our-thinking/</guid><description>&lt;p&gt;Lately I&amp;rsquo;ve been following a discussion that worries me quite a bit: &lt;strong&gt;to what extent are we delegating our thinking to AI&lt;/strong&gt;. It&amp;rsquo;s not an abstract or philosophical question, it&amp;rsquo;s something very real I&amp;rsquo;m seeing day to day in our profession and in society in general.&lt;/p&gt;
&lt;p&gt;Recently I read an article by Erik Johannes Husom titled &lt;em&gt;&amp;ldquo;Outsourcing thinking&amp;rdquo;&lt;/em&gt; that, among other things, discusses the concept of &lt;em&gt;&amp;ldquo;lump of cognition fallacy&amp;rdquo;&lt;/em&gt;. The idea is that, just as there&amp;rsquo;s an economic fallacy saying there&amp;rsquo;s a fixed amount of work to do, some believe there&amp;rsquo;s a fixed amount of thinking to do, and if machines think for us, we&amp;rsquo;ll just think about other things.&lt;/p&gt;</description></item><item><title>Five principles for using AI professionally (without going crazy)</title><link>https://antoniocortes.com/en/post/2025/07/cinco-principios-para-usar-ia-profesionalmente/</link><pubDate>Wed, 23 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2025/07/cinco-principios-para-usar-ia-profesionalmente/</guid><description>&lt;p&gt;A few days ago I read an article by &lt;a href="https://dominiek.substack.com/p/the-5-principles-of-using-ai-professionally"&gt;Dominiek about the 5 principles for using AI professionally&lt;/a&gt; and found myself constantly nodding. After years of watching technologies arrive and evolve, AI gives me the same feelings I had with other &amp;ldquo;revolutions&amp;rdquo;: enthusiasm mixed with a necessary dose of skepticism.&lt;/p&gt;
&lt;p&gt;Dominiek&amp;rsquo;s article especially resonated with me because it perfectly describes what we&amp;rsquo;re experiencing: a world where AI is getting into everything, but not always in the most useful or sensible way.&lt;/p&gt;</description></item><item><title>The New Promiscuity of Modern Developers: When Being Unfaithful to Tools Is Normal</title><link>https://antoniocortes.com/en/post/2025/07/promiscuidad-desarrolladores-modernos-10-julio_2025/</link><pubDate>Thu, 10 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2025/07/promiscuidad-desarrolladores-modernos-10-julio_2025/</guid><description>&lt;p&gt;Throughout my career, I&amp;rsquo;ve seen many things change. I&amp;rsquo;ve gone from Borland to Visual Studio, from vi to Sublime Text, from Sublime to VS Code&amp;hellip; And believe me, each change was a deliberate decision that cost me weeks of adaptation. But what&amp;rsquo;s happening now with AI tools is something completely different.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve found myself using Copilot in the morning, trying Cursor in the afternoon, and checking out Claude Code before going to bed. And I&amp;rsquo;m not alone. Developers have gone from being faithful as dogs to our tools to being&amp;hellip; well, promiscuous.&lt;/p&gt;</description></item><item><title>Jest: Cuando fallar rápido es la estrategia inteligente</title><link>https://antoniocortes.com/2025/07/09/jest-cuando-fallar-r%C3%A1pido-es-la-estrategia-inteligente/</link><pubDate>Wed, 09 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/2025/07/09/jest-cuando-fallar-r%C3%A1pido-es-la-estrategia-inteligente/</guid><description>&lt;p&gt;Trabajando en proyectos grandes, es habitual tener suites de tests que pueden tardar varios minutos en ejecutarse. Y cuando uno de esos tests falla al principio de la ejecución, es frustrante esperar a que todos los demás se ejecuten para ver el resultado completo.&lt;/p&gt;
&lt;p&gt;Jest incluye una funcionalidad que he encontrado muy útil en desarrollo: la opción &lt;code&gt;bail&lt;/code&gt;, que permite parar la ejecución de tests después de un número determinado de fallos. Es una de esas características que una vez la conoces y empiezas a usar, no entiendes cómo has vivido sin ella.&lt;/p&gt;</description></item><item><title>Jest: When Failing Fast is the Smart Strategy</title><link>https://antoniocortes.com/en/post/2025/07/jest-bail-09_julio_2025/</link><pubDate>Wed, 09 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2025/07/jest-bail-09_julio_2025/</guid><description>&lt;p&gt;When working on large projects, it&amp;rsquo;s common to have test suites that can take several minutes to run. And when one of those tests fails early in the execution, it&amp;rsquo;s frustrating to wait for all the others to complete just to see the full results.&lt;/p&gt;
&lt;p&gt;Jest includes a feature I&amp;rsquo;ve found very useful in development: the &lt;code&gt;bail&lt;/code&gt; option, which allows stopping test execution after a certain number of failures. It&amp;rsquo;s one of those features that once you know and start using, you don&amp;rsquo;t understand how you lived without it.&lt;/p&gt;</description></item><item><title>LM Studio Removes Barriers: Now Free for Work Too</title><link>https://antoniocortes.com/en/post/2025/07/lm-studio-gratis-trabajo-julio-2025/</link><pubDate>Wed, 09 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2025/07/lm-studio-gratis-trabajo-julio-2025/</guid><description>&lt;p&gt;In my years developing software, I&amp;rsquo;ve learned that the best tools are those that eliminate unnecessary friction. And LM Studio has just taken a huge step in that direction: &lt;strong&gt;&lt;a href="https://lmstudio.ai/blog/free-for-work"&gt;it&amp;rsquo;s now completely free for enterprise use&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This may sound like &amp;ldquo;just another AI news item,&amp;rdquo; but for those of us who have been experimenting with local models for a while, this is an important paradigm shift.&lt;/p&gt;
&lt;h2 id="the-problem-that-existed-before"&gt;The problem that existed before&lt;/h2&gt;
&lt;p&gt;Since its launch in May 2023, LM Studio was always free for personal use. But if you wanted to use it in your company, you had to contact them to obtain a commercial license. This created exactly the type of friction that kills team experimentation.&lt;/p&gt;</description></item><item><title>Reaper: When Deleting Code Is as Important as Writing It</title><link>https://antoniocortes.com/en/post/2025/07/reaper-eliminar-codigo-tan-importante-como-escribirlo/</link><pubDate>Tue, 08 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2025/07/reaper-eliminar-codigo-tan-importante-como-escribirlo/</guid><description>&lt;p&gt;In my experience with mobile development, I&amp;rsquo;ve seen how apps become increasingly complex and projects grow uncontrollably. I remember perfectly that feeling of having thousands of lines of code and not being sure what was really being used and what wasn&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s why I was so struck by the tool that Sentry (formerly from Emerge Tools) just released as open source: &lt;strong&gt;&lt;a href="https://blog.sentry.io/an-open-source-sdk-for-finding-dead-code/"&gt;Reaper&lt;/a&gt;&lt;/strong&gt;. An SDK that does something that sounds simple but is tremendously useful: find dead code in your mobile applications.&lt;/p&gt;</description></item><item><title>Context Engineering: Prompt Engineering Has Grown Up</title><link>https://antoniocortes.com/en/post/2025/context-engineering-el-prompt-engineering-ha-crecido/</link><pubDate>Sat, 05 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2025/context-engineering-el-prompt-engineering-ha-crecido/</guid><description>&lt;p&gt;A few years ago, many AI researchers (even the most reputable) predicted that prompt engineering would be a temporary skill that would quickly disappear. They were completely wrong. Not only has it not disappeared, but &lt;strong&gt;it has evolved into something much more sophisticated: Context Engineering&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;And no, it&amp;rsquo;s not just another buzzword. It&amp;rsquo;s a natural evolution that reflects the real complexity of working with LLMs in production applications.&lt;/p&gt;
&lt;h2 id="from-prompt-engineering-to-context-engineering"&gt;From prompt engineering to context engineering&lt;/h2&gt;
&lt;p&gt;The problem with the term &amp;ldquo;prompt engineering&amp;rdquo; is that many people confuse it with &lt;strong&gt;blind prompting&lt;/strong&gt; - simply writing a question in ChatGPT and expecting a result. That&amp;rsquo;s not engineering, that&amp;rsquo;s using a tool.&lt;/p&gt;</description></item><item><title>Deno 2.4: The Bundle is Back</title><link>https://antoniocortes.com/en/post/2025/deno-24-el-bundle-ha-vuelto/</link><pubDate>Sat, 05 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2025/deno-24-el-bundle-ha-vuelto/</guid><description>&lt;p&gt;Deno 2.4 has just been released, and I must admit it has pleasantly surprised me. Not only because of the number of new features, but because of one in particular that many of us thought would never return: &lt;strong&gt;&lt;code&gt;deno bundle&lt;/code&gt; is back&lt;/strong&gt;. And this time, it&amp;rsquo;s here to stay.&lt;/p&gt;
&lt;p&gt;This release comes packed with improvements ranging from importing text files directly to stable observability with OpenTelemetry. Let&amp;rsquo;s explore what this release brings us.&lt;/p&gt;</description></item><item><title>JSONPath: The XPath We Needed for JSON</title><link>https://antoniocortes.com/en/post/2025/jsonpath-el-xpath-que-necesitabamos-para-json/</link><pubDate>Sat, 05 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2025/jsonpath-el-xpath-que-necesitabamos-para-json/</guid><description>&lt;p&gt;I&amp;rsquo;ve seen how certain standards and tools become indispensable when working with data. And if there&amp;rsquo;s one thing we&amp;rsquo;ve learned over these years, it&amp;rsquo;s that &lt;strong&gt;JSON is everywhere&lt;/strong&gt;: APIs, logs, configurations, NoSQL databases&amp;hellip; The question is no longer whether you&amp;rsquo;ll work with JSON, but when you&amp;rsquo;ll face that 15-level nested structure that makes you sigh.&lt;/p&gt;
&lt;h2 id="the-problem-weve-all-lived-through"&gt;The Problem We&amp;rsquo;ve All Lived Through&lt;/h2&gt;
&lt;p&gt;How many times have you had to write something like this?&lt;/p&gt;</description></item><item><title>PHP 8.5.0 Alpha 1: Pipeline to the Future</title><link>https://antoniocortes.com/en/post/2025/php-85-alpha-1-pipeline-hacia-el-futuro/</link><pubDate>Sat, 05 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2025/php-85-alpha-1-pipeline-hacia-el-futuro/</guid><description>&lt;p&gt;The first alpha version of PHP 8.5 has just been released, and I must confess it has me more excited than recent versions. It&amp;rsquo;s not just for the technical improvements (which are many), but because &lt;strong&gt;PHP 8.5 introduces features that will change the way we write code&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;And when I say &amp;ldquo;change,&amp;rdquo; I mean the kind of changes that, once you use them, you can&amp;rsquo;t go back. Like when the null coalescing operator (&lt;code&gt;??&lt;/code&gt;) appeared in PHP 7, or arrow functions in PHP 7.4.&lt;/p&gt;</description></item><item><title>WebAssembly Agents: AI in the Browser Without Complications</title><link>https://antoniocortes.com/en/post/2025/webassembly-agents-mozilla-ai/</link><pubDate>Fri, 04 Jul 2025 12:00:00 +0200</pubDate><guid>https://antoniocortes.com/en/post/2025/webassembly-agents-mozilla-ai/</guid><description>&lt;h2 id="mozilla-ai-surprises-again-ai-agents-that-work-just-by-opening-an-html"&gt;Mozilla AI surprises again: AI agents that work just by opening an HTML&lt;/h2&gt;
&lt;p&gt;A few days ago I came across a Mozilla AI project that really caught my attention: &lt;a href="https://blog.mozilla.ai/wasm-agents-ai-agents-running-in-your-browser/"&gt;WebAssembly Agents&lt;/a&gt;. And after 30 years watching the industry complicate life with dependencies, installations, and configurations, seeing something that works just by &amp;ldquo;opening an HTML&amp;rdquo; made me smile.&lt;/p&gt;
&lt;h3 id="the-problem-it-solves-and-we-all-know-it"&gt;The problem it solves (and we all know it)&lt;/h3&gt;
&lt;p&gt;How many times have you tried to test an AI project and encountered this?&lt;/p&gt;</description></item><item><title>LLMs in Software Engineering: 2025 Reality Check</title><link>https://antoniocortes.com/en/post/2025/llms-ingenieria-software-reality-check-2025/</link><pubDate>Thu, 03 Jul 2025 10:00:00 +0200</pubDate><guid>https://antoniocortes.com/en/post/2025/llms-ingenieria-software-reality-check-2025/</guid><description>&lt;h2 id="the-hype-vs-reality-reflections-from-a-developer-with-30-years-of-experience"&gt;The hype vs reality: reflections from a developer with 30 years of experience&lt;/h2&gt;
&lt;p&gt;This morning I came across a talk that made me reflect quite a bit about all this fuss surrounding AI and software development. The speaker, with a healthy dose of skepticism, does a &amp;ldquo;reality check&amp;rdquo; on all the grandiose claims we&amp;rsquo;re hearing everywhere.&lt;/p&gt;
&lt;div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"&gt;
 &lt;iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/EO3_qN_Ynsk?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"&gt;&lt;/iframe&gt;
 &lt;/div&gt;

&lt;p&gt;&lt;em&gt;The complete talk that inspired these reflections. It&amp;rsquo;s worth watching in full.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Cocos2d x</title><link>https://antoniocortes.com/en/cocos2d-x/</link><pubDate>Sat, 15 Dec 2012 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/cocos2d-x/</guid><description>&lt;p&gt;When developing games for mobile devices, we have multiple cross-platform alternatives:&lt;/p&gt;</description></item><item><title>Implement Haanga as a template system for OpenCart</title><link>https://antoniocortes.com/en/implement-haanga-as-template-system-for-opencart/</link><pubDate>Sun, 31 Oct 2010 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/implement-haanga-as-template-system-for-opencart/</guid><description>&lt;p&gt;&lt;a href="http://www.opencart.com/"&gt;OpenCart&lt;/a&gt; is an e-commerce platform made in php, with impeccable development, 100% MVC. As a proof of concept, I have rewritten the template system of &lt;a href="http://www.opencart.com/"&gt;OpenCart&lt;/a&gt; to &lt;a href="http://github.com/crodas/Haanga"&gt;Haanga&lt;/a&gt; (Django templates for PHP, über efficient) by &lt;a href="http://crodas.org/"&gt;César Rodas&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Icons for Android developers</title><link>https://antoniocortes.com/en/icons-for-android-developers/</link><pubDate>Sun, 08 Nov 2009 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/icons-for-android-developers/</guid><description>&lt;p&gt;WebAppers offers us 30 icons, and their sources for developers of this platform.&lt;/p&gt;</description></item><item><title>In the Works</title><link>https://antoniocortes.com/en/in-the-works/</link><pubDate>Mon, 22 Sep 2008 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/in-the-works/</guid><description>&lt;p&gt;Lately I&amp;rsquo;ve been busy studying and testing different libraries and resources:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://extjs.com/"&gt;ExtJS&lt;/a&gt;: Javascript.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.cakephp.org"&gt;CakePHP&lt;/a&gt;: PHP.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://code.google.com/p/joose-js/"&gt;Joose&lt;/a&gt;: Javascript.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.imatia.com/ontimize"&gt;Ontimize&lt;/a&gt;: Java.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://developer.yahoo.com/yui/"&gt;Yahoo UI Library&lt;/a&gt;: Javascript.&lt;/li&gt;
&lt;li&gt;…&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I have many examples, tricks, and &amp;ldquo;recipes&amp;rdquo; for each of these that I&amp;rsquo;ll be publishing to keep them organized and easily accessible, and also because they&amp;rsquo;ll surely be useful to others.&lt;/p&gt;</description></item></channel></rss>