<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Diogo Oliveira de Melo</title><description>Field notes on software engineering, AI coding agents, Linux and tooling.</description><link>https://diogomelo.net/</link><item><title>Claude Code: Handling the error &quot;API Error: The response stopped arriving&quot;</title><link>https://diogomelo.net/blog/26/claude-code-api-error-response-stopped-arriving.html</link><guid isPermaLink="true">https://diogomelo.net/blog/26/claude-code-api-error-response-stopped-arriving.html</guid><description>Every once in a while, I see a yellow warning on my claude code session: Searching about this error, it is exactly as it says: the server has stopped sending data mid-response, for over a certain time. I have multiple sessions opened, all the time. What would usually happen: I send a prompt I move…</description><pubDate>Wed, 28 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Simple Benchmark with Node.js against Apache</title><link>https://diogomelo.net/blog/12/simple-benchmark-nodejs-against-apache.html</link><guid isPermaLink="true">https://diogomelo.net/blog/12/simple-benchmark-nodejs-against-apache.html</guid><description>Today I did a very basic benchmark and the result was impressive. For this benchmark I&apos;m only interested in the overhead each web server creates to establish the connection, process the request and send the response. First, a simple hello world program on Node.js: After running node a.js the result…</description><pubDate>Sun, 26 Feb 2012 00:00:00 GMT</pubDate></item></channel></rss>