<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Andrea Cervesato</title><link>https://cervesato.it/</link><description>Recent content on Andrea Cervesato</description><generator>Hugo</generator><language>en</language><copyright>Andrea Cervesato</copyright><lastBuildDate>Tue, 07 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cervesato.it/index.xml" rel="self" type="application/rss+xml"/><item><title>From Alerting to Inference: Metrics Never Stopped Mattering</title><link>https://cervesato.it/posts/metrics-never-stopped-mattering/</link><pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate><guid>https://cervesato.it/posts/metrics-never-stopped-mattering/</guid><description>&lt;p&gt;Your LLM is slow. Users are complaining. Queues are growing. Someone on the team is already profiling the model, looking at batch sizes, considering a bigger GPU.&lt;/p&gt;
&lt;p&gt;Nine times out of ten, the answer is already in the metrics.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve spent most of my career staring at metrics. Bare-metal servers, Kubernetes clusters, managed services on public cloud. And if there&amp;rsquo;s one thing I keep re-learning, it&amp;rsquo;s that the infrastructure is lying to you, and you&amp;rsquo;re not asking the right questions.&lt;/p&gt;
&lt;p&gt;This isn&amp;rsquo;t a new lesson. Same lesson, different domain.&lt;/p&gt;</description></item><item><title>Making an NVIDIA eGPU Actually Work on Linux (The Hard Way)</title><link>https://cervesato.it/posts/egpu-thunderbolt-nvidia-bar-fix/</link><pubDate>Fri, 27 Mar 2026 00:00:00 +0000</pubDate><guid>https://cervesato.it/posts/egpu-thunderbolt-nvidia-bar-fix/</guid><description>&lt;p&gt;I have a Framework Laptop 13 (Intel 13th gen) and an RTX 3070 sitting in a Thunderbolt 3 eGPU enclosure. On Windows it just works. On Linux, I got this:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
NVRM: BAR1 is 0M @ 0x0 (PCI:0000:04:00.0)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The GPU was right there on the PCI bus. The driver loaded. And then it gave up because BAR1 — the 256MB framebuffer aperture the GPU needs to function — had zero bytes allocated. A 220W GPU reduced to a very expensive space heater.&lt;/p&gt;
&lt;p&gt;I spent the better part of a weekend on this. Here is what I found.&lt;/p&gt;</description></item><item><title>About</title><link>https://cervesato.it/about/</link><pubDate>Sat, 21 Mar 2026 00:00:00 +0000</pubDate><guid>https://cervesato.it/about/</guid><description>&lt;p&gt;&lt;img src="https://www.gravatar.com/avatar/4150c6d0df7b0fc7f6168fd7f4cc863c?s=200" alt="Andrea Cervesato"&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m Andrea Cervesato, based in Milan, Italy. I work on infrastructure — mostly cloud, mostly Kubernetes, mostly trying to keep things from falling over.&lt;/p&gt;
&lt;p&gt;I started in 2004 doing sysadmin work on HP-UX boxes in a telco. Since then I&amp;rsquo;ve racked servers, run cables, debugged things at 3 AM, and slowly moved up the stack from bare metal to cloud. Along the way I picked up some certifications, some scars, and a healthy distrust of slides that say &amp;ldquo;it just works.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Maslow's Hammer and the MCP Debate</title><link>https://cervesato.it/posts/mcp-not-everything-is-a-nail/</link><pubDate>Sat, 21 Mar 2026 00:00:00 +0000</pubDate><guid>https://cervesato.it/posts/mcp-not-everything-is-a-nail/</guid><description>&lt;p&gt;A few days ago, a Principal Software Engineer at Red Hat posted a one-liner on LinkedIn that split the comments section in half:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;&amp;ldquo;MCP is a layer of unnecessary indirection. A properly documented REST API is enough and works for everyone, not just agents.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;33 reactions, 13 comments, and a thread that surfaced some genuinely good arguments on both sides. I jumped in with &lt;a href="https://www.linkedin.com/posts/rigeldiscala_mcp-is-a-layer-of-unnecessary-indirection-share-7438853936566059008-86oB"&gt;my take&lt;/a&gt;, but a LinkedIn comment is not the right format for a nuanced opinion. So here&amp;rsquo;s the long version.&lt;/p&gt;</description></item><item><title>Kill Your Service Account Keys: Secure GitLab CI/CD on Google Cloud</title><link>https://cervesato.it/posts/killing-service-account-keys/</link><pubDate>Sun, 15 Dec 2024 00:00:00 +0000</pubDate><guid>https://cervesato.it/posts/killing-service-account-keys/</guid><description>&lt;p&gt;If your CI/CD pipeline authenticates to Google Cloud with a service account key stored in a CI variable, you have a problem. You might not know it yet, but you have a problem.&lt;/p&gt;
&lt;p&gt;That JSON key file is a static credential. It doesn&amp;rsquo;t expire (unless you rotate it, which you don&amp;rsquo;t). It has no context about &lt;em&gt;who&lt;/em&gt; or &lt;em&gt;what&lt;/em&gt; is using it. If it leaks — and CI variables leak more often than anyone admits — an attacker gets the same access your pipeline has. Forever, or until someone notices.&lt;/p&gt;
&lt;p&gt;So I built a POC to try the alternative: a keyless, signed, vulnerability-gated pipeline from GitLab to Google Cloud. No service account keys. No stored secrets.&lt;/p&gt;</description></item><item><title>Four People, Four Datacenters, Three Thousand Servers</title><link>https://cervesato.it/posts/hello-world/</link><pubDate>Thu, 08 Jun 2023 00:00:00 +0000</pubDate><guid>https://cervesato.it/posts/hello-world/</guid><description>&lt;p&gt;In 2015 I joined Irideos (then KPNQwest Italia) as a Cloud Architect. The job sounded fancy. The reality was four datacenters, roughly three thousand servers, a team of four engineers, and a budget that could generously be described as &amp;ldquo;creative.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;This is the story of how we made it work — and what I still carry from that experience today.&lt;/p&gt;</description></item></channel></rss>