<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alexandre Nuttinck</title><link>https://alexnuttinck.dev/</link><description>Recent content on Alexandre Nuttinck</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 07 Jul 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://alexnuttinck.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>The One Person Who Knows</title><link>https://alexnuttinck.dev/posts/30-the-one-person-who-knows/</link><pubDate>Tue, 07 Jul 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/30-the-one-person-who-knows/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/30-the-one-person-who-knows.png"
alt="Adventures in Uptime - The One Person Who Knows"
&gt;
&lt;p&gt;Every company has one. That one sysadmin sitting behind a fortress of monitors, cables, and coffee cups. They are the legend of the open space. When a complex legacy system acts up, colleagues point at them in reverence and whisper:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;That’s the one who knows everything. Don’t touch anything without asking them.&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;But this legendary status comes with a dark side: Solo Mode. Whenever an over-eager junior dev or a desperate teammate tries to peek at the terminal and politely asks for a runbook or documentation, the answer is always the same annoyed grumble:&lt;/p&gt;</description></item><item><title>The Midnight Doubt</title><link>https://alexnuttinck.dev/posts/29-the-midnight-doubt/</link><pubDate>Mon, 22 Jun 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/29-the-midnight-doubt/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/29-the-midnight-doubt.png"
alt="Adventures in Uptime - The Midnight Doubt"
&gt;
&lt;p&gt;We&amp;rsquo;ve all been there. It’s 5:00 PM, you’re packing up your bag, and the client leans against your desk looking relaxed but serious with a casual request:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Hey, the cloud bill is getting scary. Can you just turn off the big servers when you leave tonight?&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Without missing a beat, you give the classic sysadmin guarantee: &amp;ldquo;No worries. I&amp;rsquo;ll hit the &amp;lsquo;Stop&amp;rsquo; button manually before I head out. Consider it done.&amp;rdquo; It’s a simple promise. What could go wrong?&lt;/p&gt;</description></item><item><title>The Meeting Singularity</title><link>https://alexnuttinck.dev/posts/28-the-meeting-singularity/</link><pubDate>Tue, 16 Jun 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/28-the-meeting-singularity/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/28-the-meeting-singularity.png"
alt="Adventures in Uptime - The Meeting Singularity"
&gt;
&lt;p&gt;It starts as a classic sysadmin trap. I was assigned to five projects at the same time&amp;hellip; At first glance, you tell yourself, &amp;ldquo;Busy&amp;hellip; but manageable.&amp;rdquo;. After all, spinning up infrastructure and automating pipelines for multiple environments is just part of the job.&lt;/p&gt;
&lt;p&gt;But then comes the calendar takeover.&lt;/p&gt;
&lt;p&gt;Each project came with its own meetings. Suddenly, your schedule is completely packed from morning to evening. The deep-work time you need to write actual code is rapidly replaced by a wall of colored blocks representing a status meeting, a sync call, an alignment meeting, and a steering committee. You find yourself staring at your screen, muttering, &amp;ldquo;When do I actually work?&amp;rdquo;.&lt;/p&gt;</description></item><item><title>Annual Review Season</title><link>https://alexnuttinck.dev/posts/27-annual-review-season/</link><pubDate>Sat, 06 Jun 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/27-annual-review-season/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/27-annual-review-season.png"
alt="Adventures in Uptime - Annual Review Season"
&gt;
&lt;p&gt;It’s a classic tale in the world of IT and operations. All year long, you grind through on-call nights, manage complex migrations, and extinguish fires before anyone even realizes there was smoke. You look at your screens, and everything is beautifully stable. All systems are operational.&lt;/p&gt;
&lt;p&gt;Then comes the dreaded annual review meeting.&lt;/p&gt;
&lt;p&gt;You sit down in the small meeting room across from your manager, ready to present hard facts. You calmly explain your solid list of technical achievements:&lt;/p&gt;</description></item><item><title>The Two-Day Onboarding</title><link>https://alexnuttinck.dev/posts/26-the-two-day-onboarding/</link><pubDate>Tue, 19 May 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/26-the-two-day-onboarding/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/26-the-two-day-onboarding.png"
alt="Adventures in Uptime - The Two-Day Onboarding"
&gt;
&lt;p&gt;There is an unspoken rule in IT: the amount of time an employee stays at a company is inversely proportional to the effort it took to bring them there.&lt;/p&gt;
&lt;p&gt;This story is a perfect example. We spent months dealing with heavy paperwork, organizing a visa, and sorting out relocation and housing just to bring a new colleague over from the US. When the big day finally arrived, the whole team welcomed our new hire with bright smiles. We even put a small US flag on their desk, right next to their freshly printed badge and ready-to-go laptop.&lt;/p&gt;</description></item><item><title>The 20,000-Dollar Commit</title><link>https://alexnuttinck.dev/posts/25-the-20000-dollar-commit/</link><pubDate>Sun, 03 May 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/25-the-20000-dollar-commit/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/25-the-20000-dollar-commit.png"
alt="Adventures in Uptime - The 20,000-Dollar Commit"
&gt;
&lt;p&gt;It started as a perfectly normal afternoon. A developer, happily working at their desk, pushed some code to a public repository.
But that colleague made a tiny, seemingly harmless mistake. In the rush to get things done, he hardcoded an AWS access key and pushed it straight to a public repository.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Maybe no one saw it&amp;hellip; right?&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;That is the desperate hope of every engineer who realizes what they’ve just done. But the internet never sleeps, and more importantly, the scraping bots never sleep. Within seconds of that repository going public, the keys were harvested.&lt;/p&gt;</description></item><item><title>The Schrödinger Server</title><link>https://alexnuttinck.dev/posts/24-the-schrodinger-server/</link><pubDate>Sun, 03 May 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/24-the-schrodinger-server/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/24-the-schrodinger-server.png"
alt="Adventures in Uptime - The Schrödinger Server"
&gt;
&lt;p&gt;Before we dive into today&amp;rsquo;s infrastructure mystery, you might notice a slight shift in the comic&amp;rsquo;s aesthetic! Starting with this story, I&amp;rsquo;ve switched the AI image generation model I use from &lt;em&gt;gpt-image-1&lt;/em&gt; to &lt;em&gt;Nano Banana Pro&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;While the art style has evolved a bit, the trade-offs are incredibly worth it. I&amp;rsquo;m getting much better visual coherence across the panels, and the model produces far fewer &amp;ldquo;hallucinations.&amp;rdquo; This allows me to reach the exact framing I want much faster, giving me more time to refine the small details. Honestly, I&amp;rsquo;m having a blast with it! 😄&lt;/p&gt;</description></item><item><title>The Cowboy Sysadmin</title><link>https://alexnuttinck.dev/posts/23-the-cowboy-sysadmin/</link><pubDate>Mon, 27 Apr 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/23-the-cowboy-sysadmin/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/23-the-cowboy-sysadmin.png"
alt="Adventures in Uptime - The Cowboy Sysadmin"
&gt;
&lt;p&gt;The Grafana dashboards are glowing a reassuring green, and the ticket queue is finally down to single digits, when he walks into the open space.&lt;/p&gt;
&lt;p&gt;The Cowboy Sysadmin.&lt;/p&gt;
&lt;p&gt;He doesn&amp;rsquo;t need automated deployment scripts. He scoffs at the concept of a &amp;ldquo;read-only&amp;rdquo; Friday. To him, SSH-ing directly into the production server as root isn&amp;rsquo;t a violation of company policy; it&amp;rsquo;s a lifestyle choice.&lt;/p&gt;
&lt;p&gt;In this week&amp;rsquo;s Adventures in Uptime, we chronicle the legendary, high-adrenaline, and deeply terrifying phenomenon of &amp;ldquo;Cowboy Ops.&amp;rdquo; It’s that magical, heart-stopping moment when someone decides to run &lt;code&gt;rm -rf&lt;/code&gt; in the wild without a safety net.&lt;/p&gt;</description></item><item><title>The Update Panic</title><link>https://alexnuttinck.dev/posts/22-the-update-panic/</link><pubDate>Tue, 21 Apr 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/22-the-update-panic/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/22-the-update-panic.png"
alt="Adventures in Uptime - The Update Panic"
&gt;
&lt;p&gt;I’ve worked with a lot of developers over the years, but there is one I’ll never forget. His code was&amp;hellip; fine. Mostly functional. But the moment it was time to deploy? Total meltdown.&lt;/p&gt;
&lt;p&gt;While most of the team treats a deployment as a routine click, he treated it like he was defusing a live bomb. Sweating bullets, his finger would tremble over the &amp;ldquo;Deploy to Production&amp;rdquo; button like he was about to launch a rocket. In his mind, a single typo wasn&amp;rsquo;t just going to break the build: it was going to take down the entire infrastructure, permanently erase the database, and somehow set the office coffee machine on fire.&lt;/p&gt;</description></item><item><title>Baptism of Fire</title><link>https://alexnuttinck.dev/posts/21-baptism-of-fire/</link><pubDate>Mon, 13 Apr 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/21-baptism-of-fire/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/21-baptism-of-fire.png"
alt="Adventures in Uptime - Baptism of Fire"
&gt;
&lt;p&gt;It started like any normal morning. Coffee in hand, sleepy colleagues, the gentle hum of the open space. And then&amp;hellip; total darkness.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Did someone trip on a cable?&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;We weren&amp;rsquo;t too worried at first. After all, we had an UPS and a massive diesel generator out back. It was supposed to be our safety net.&lt;/p&gt;
&lt;p&gt;Well, the safety net had a massive hole in it. The generator sputtered, coughed, and died with a sad pouf. Suddenly, our entire server room went completely silent. If you work in IT, you know there is nothing more terrifying than a cold, dead-silent server room.&lt;/p&gt;</description></item><item><title>Version Control by Outlook</title><link>https://alexnuttinck.dev/posts/20-version-control-by-outlook/</link><pubDate>Mon, 23 Mar 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/20-version-control-by-outlook/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/20-version-control-by-outlook.png"
alt="Adventures in Uptime - Version Control by Outlook"
&gt;
&lt;p&gt;We’ve all been there: joining a new project, grabbing a fresh cup of coffee, and asking the developer the most basic, innocent question imaginable:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Hey, where&amp;rsquo;s the code repo for your project?&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;You expect a Github link, maybe a Gitlab URL, or even an ancient SVN server if you&amp;rsquo;re feeling unlucky. What you don&amp;rsquo;t expect is the developer to smile with 100% unshakeable confidence and say:&lt;/p&gt;</description></item><item><title>The Intern Factory</title><link>https://alexnuttinck.dev/posts/19-the-intern-factory/</link><pubDate>Mon, 16 Mar 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/19-the-intern-factory/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/19-the-intern-factory.png"
alt="Adventures in Uptime - The Intern Factory"
&gt;
&lt;p&gt;Ah, the memories of early consulting missions. You walk into a new client&amp;rsquo;s office, expecting the usual setup: a grizzled senior dev nursing their third coffee, a stressed sysadmin, and a project manager asking for the impossible by Friday.&lt;/p&gt;
&lt;p&gt;But sometimes, you walk into something entirely different. You walk into a modern-day &amp;ldquo;cost-efficiency&amp;rdquo; miracle.&lt;/p&gt;
&lt;p&gt;In Belgium, there’s a well-known reality for startups and budget-conscious companies: student internships are often unpaid. During one of my very first missions, I encountered a company that didn&amp;rsquo;t just use this system&amp;hellip; They built their entire engineering department around it.&lt;/p&gt;</description></item><item><title>The KubeCon Goodies Hunt</title><link>https://alexnuttinck.dev/posts/18-the-kubecon-goodies-hunt/</link><pubDate>Tue, 10 Mar 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/18-the-kubecon-goodies-hunt/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/18-the-kubecon-goodies-hunt.png"
alt="Adventures in Uptime - The KubeCon Goodies Hunt"
&gt;
&lt;p&gt;We’ve all been there. You register for a major tech conference like KubeCon with the best intentions.
You mark the schedule with all the deep-dive technical sessions you want to attend. You promise yourself you’ll network with industry leaders and learn about the latest in service mesh architecture.&lt;/p&gt;
&lt;p&gt;Then you walk into the expo hall.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Grab a hoodie! Free socks! Do you want a light-up yoyo that connects to Bluetooth?&amp;rdquo;&lt;/p&gt;</description></item><item><title>Everything is Priority</title><link>https://alexnuttinck.dev/posts/17-everything-is-priority/</link><pubDate>Sun, 01 Mar 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/17-everything-is-priority/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/17-everything-is-priority.png"
alt="Adventures in Uptime - Everything is Priority"
&gt;
&lt;p&gt;We’ve all been in that meeting.
The one where the manager stands in front of a whiteboard covered in sticky notes, eyes wide with excitement.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Okay team. These are all top priority tasks!&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;You scan the board.
&amp;ldquo;Urgent.&amp;rdquo;
&amp;ldquo;Critical.&amp;rdquo;
&amp;ldquo;Do Now.&amp;rdquo;
&amp;ldquo;Top Priority.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Every single item is flagged as essential. Every feature is a must-have. Every bug is a showstopper.&lt;/p&gt;
&lt;p&gt;When you ask the logical question: &amp;ldquo;If they are all priority one, which one do we do first?&amp;rdquo;. You get the classic answer:&lt;/p&gt;</description></item><item><title>Bitnamipocalypse</title><link>https://alexnuttinck.dev/posts/16-bitnamipocalypse/</link><pubDate>Mon, 16 Feb 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/16-bitnamipocalypse/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/16-bitnamipocalypse.png"
alt="Adventures in Uptime - Bitnamipocalypse"
&gt;
&lt;p&gt;Do you remember where you were last summer when the notification popped up?&lt;/p&gt;
&lt;p&gt;It started as a normal morning in DevOps. You were sipping your coffee, scrolling through GitHub issues, thinking the day would be about optimization or maybe finally tackling some tech debt. Then you saw it: &lt;strong&gt;bitnami/charts issue #35164&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;The announcement was brief, but the implications were heavy: Community charts were moving. The migration window? One month&amp;hellip;&lt;/p&gt;</description></item><item><title>Working from Shed</title><link>https://alexnuttinck.dev/posts/15-working-from-shed/</link><pubDate>Mon, 09 Feb 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/15-working-from-shed/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/15-working-from-shed.png"
alt="Adventures in Uptime - Working from Shed"
&gt;
&lt;p&gt;Remote work has invited us into everyone’s homes. We’ve all seen the kitchen counters, the unmade beds in the background, or the cats walking across keyboards.&lt;/p&gt;
&lt;p&gt;But during a video call, I witnessed a setup that truly redefined &amp;ldquo;dedication.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;I called a colleague for a quick sync. When his video feed popped up, I didn&amp;rsquo;t see a home office or a living room. I saw wooden planks, a lawnmower, and a shovel hanging on the wall.&lt;/p&gt;</description></item><item><title>Caught by Your Own Phish</title><link>https://alexnuttinck.dev/posts/14-caught-by-your-own-phish/</link><pubDate>Mon, 02 Feb 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/14-caught-by-your-own-phish/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/14-caught-by-your-own-phish.png"
alt="Adventures in Uptime - Caught by Your Own Phish"
&gt;
&lt;p&gt;We often talk about the &amp;ldquo;human firewall&amp;rdquo; in cybersecurity. But sometimes, that firewall has a few open ports due to distraction.&lt;/p&gt;
&lt;p&gt;This story comes from a security team I worked with. One of the team was deeply involved in the elaboration of the quarterly internal phishing simulation. He spent days brainstorming with the team, debating the best subject lines, and fine-tuning the fake login page to make it look just authentic enough to fool the unwary.&lt;/p&gt;</description></item><item><title>The Desk Production Server</title><link>https://alexnuttinck.dev/posts/13-the-desk-production-server/</link><pubDate>Mon, 26 Jan 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/13-the-desk-production-server/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/13-the-desk-production-server.png"
alt="Adventures in Uptime - The Desk Production Server"
&gt;
&lt;p&gt;We live in the era of the Cloud, Kubernetes clusters, and geo-redundant data centers. But sometimes, the most critical infrastructure is much closer to the ground. Literally.&lt;/p&gt;
&lt;p&gt;This story comes from a moment of pure realization. I was at the office while a colleague was working remotely. He called me up, looking a bit sheepish, and asked for a favor: &amp;ldquo;Can you reboot the tower under my desk? There was a power cut and it didn&amp;rsquo;t come back up.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Alias of Shame</title><link>https://alexnuttinck.dev/posts/12-alias-of-shame/</link><pubDate>Mon, 19 Jan 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/12-alias-of-shame/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/12-alias-of-shame.png"
alt="Adventures in Uptime - Alias of Shame"
&gt;
&lt;p&gt;Mistakes happen.
Even in carefully planned communication campaigns.&lt;/p&gt;
&lt;p&gt;One day, a brand-new email campaign was sent out to a large audience. Everything looked fine&amp;hellip; until someone noticed it.&lt;/p&gt;
&lt;p&gt;The email address in the communication was wrong.&lt;/p&gt;
&lt;p&gt;Panic followed quickly.&lt;/p&gt;
&lt;p&gt;Instead of preparing a simple correction and sending a follow-up email with the proper address, the communication team came to us with a different request:&lt;/p&gt;</description></item><item><title>Just Use Nix</title><link>https://alexnuttinck.dev/posts/11-just-use-nix/</link><pubDate>Mon, 12 Jan 2026 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/11-just-use-nix/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/11-just-use-nix.png"
alt="Adventures in Uptime - Just Use Nix"
&gt;
&lt;p&gt;It all started with a classic developer frustration:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Why doesn’t this app build the same way on my machine?!&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;A colleague leaned over, smiling with the confidence of someone who has already been converted:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;You should just use Nix.&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;How complicated could it be?&lt;/p&gt;
&lt;p&gt;Well&amp;hellip; Nix isn’t &lt;em&gt;just&lt;/em&gt; a package manager.
It’s a whole paradigm shift: reproducibility, determinism, portability, system stability: everything defined declaratively.
It promises environments that never drift and setups that behave exactly the same everywhere.
And then there’s &lt;strong&gt;NixOS&lt;/strong&gt;. Not just a tool, but an entire operating system built on the same ideas.&lt;/p&gt;</description></item><item><title>Christmas Sweater Outage</title><link>https://alexnuttinck.dev/posts/os-1-christmas-sweater-outage/</link><pubDate>Mon, 22 Dec 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/os-1-christmas-sweater-outage/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/os-1-christmas-sweater-outage.png"
alt="Adventures in Uptime - Christmas Sweater Outage"
&gt;
&lt;p&gt;We had a Christmas Sweater Day at the office with colleagues.
Let’s just say&amp;hellip; that day was particularly inspiring. 😄&lt;/p&gt;
&lt;p&gt;This also feels like a good moment to slow things down a bit.
There won’t be any new Adventures in Uptime stories next week.
But don’t worry, I still enjoy creating these little comic strips just as much, and there will be more to come in 2026!&lt;/p&gt;</description></item><item><title>Load Test Reality</title><link>https://alexnuttinck.dev/posts/10-load-test-reality/</link><pubDate>Mon, 15 Dec 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/10-load-test-reality/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/10-load-test-reality.png"
alt="Adventures in Uptime - Load Test Reality"
&gt;
&lt;p&gt;It was a new mission: run performance tests on an application built by another consultant. The goal was simple: either confirm everything was fine, or prove there were real performance issues.&lt;/p&gt;
&lt;p&gt;The original consultant was very confident. From his point of view, there was no problem at all.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;We tested with JMeter. It scales perfectly. No problem.&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Let’s just say&amp;hellip; our results didn’t exactly match that statement.&lt;/p&gt;</description></item><item><title>The Coffee Crisis</title><link>https://alexnuttinck.dev/posts/9-the-coffee-crisis/</link><pubDate>Tue, 09 Dec 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/9-the-coffee-crisis/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/9-the-coffee-crisis.png"
alt="Adventures in Uptime - The Coffee Crisis"
&gt;
&lt;p&gt;It’s a classic scene in any office&amp;hellip; but even more so in IT. Caffeine consumption is high, dependency is real, and when the coffee machine goes down, everything suddenly becomes a critical incident.&lt;/p&gt;
&lt;p&gt;What always makes me laugh is how seriously teams treat it, almost like a real outage (including myself 😅). Emergency discussions, improvised failover plans, desperate workarounds&amp;hellip; All for a working espresso.&lt;/p&gt;</description></item><item><title>The Accidental Production</title><link>https://alexnuttinck.dev/posts/8-the-accidental-production/</link><pubDate>Mon, 01 Dec 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/8-the-accidental-production/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/8-the-accidental-production.png"
alt="Adventures in Uptime - The Accidental Production"
&gt;
&lt;p&gt;It started as a simple mission: build a Kubernetes POC to explore the benefits and rethink the current architecture.
The demo worked, the checklist was green, everyone was happy.&lt;/p&gt;
&lt;p&gt;We made it clear to the client:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;This is only a demo environment, nothing critical.&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;They nodded, satisfied.
We moved on.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;A few weeks later, the phone rang.
It was the same client. Except this time, they didn’t sound calm at all. 😨&lt;/p&gt;</description></item><item><title>AI Title Generator</title><link>https://alexnuttinck.dev/posts/7-ai-title-generator/</link><pubDate>Mon, 24 Nov 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/7-ai-title-generator/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/7-ai-title-generator.png"
alt="Adventures in Uptime - The AI Title Generator"
&gt;
&lt;p&gt;I was browsing LinkedIn and a few other platforms, looking for sysadmin or system engineer positions.
Nothing. Or almost nothing.&lt;/p&gt;
&lt;p&gt;It turns out that “System Administrator” is apparently too old-school now.
The title seems to have quietly disappeared, replaced by an explosion of new ones:
DevOps Engineer, Cloud Engineer, Platform Engineer, Site Reliability Engineer, Cloud Architect&amp;hellip;
and even Operations Ninja.&lt;/p&gt;
&lt;p&gt;All these roles sound different, yet when you read the job descriptions, they all seem to mean the same thing.
Run servers, automate stuff, fix things, you know, the usual.&lt;/p&gt;</description></item><item><title>Untouchable Server</title><link>https://alexnuttinck.dev/posts/6-untouchable-server/</link><pubDate>Mon, 17 Nov 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/6-untouchable-server/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/6-untouchable-server.png"
alt="Adventures in Uptime - Untouchable Server"
&gt;
&lt;p&gt;Every IT team has that one server.
The one sitting in the corner of the rack with a dusty case, a yellowed label that says “DO NOT TOUCH”, and an aura of mystery.&lt;/p&gt;
&lt;p&gt;This one ran on RHEL 3.
When it was first installed, I was around 10 or 12 years old.
It had lived through hardware migrations, OS updates, and entire generations of sysadmins: or rather, survived them.&lt;/p&gt;</description></item><item><title>The Day Sysadmins Quit</title><link>https://alexnuttinck.dev/posts/5-the-day-sysadmins-quit/</link><pubDate>Mon, 10 Nov 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/5-the-day-sysadmins-quit/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/5-the-day-sysadmins-quit.png"
alt="Adventures in Uptime - The Day Sysadmins Quit"
&gt;
&lt;p&gt;This story is inspired by something very real: the invisible work of system administrators.&lt;/p&gt;
&lt;p&gt;Their job isn’t to ship new features or flashy updates, it’s to make sure that everything just works.
Servers stay up, backups run, emails flow, and systems stay secure.
Most of it happens quietly, behind the scenes, where no one really notices&amp;hellip; until something breaks.&lt;/p&gt;
&lt;p&gt;Unfortunately, some managers don’t see that.
When they don’t understand the technical side, they think &amp;ldquo;nothing’s happening.&amp;rdquo;
Micromanagement takes over, trust disappears, and appreciation fades.
And eventually, the sysadmins decide to leave. Because, let’s be honest, there’s no shortage of work for skilled people elsewhere.&lt;/p&gt;</description></item><item><title>The Million-Dollar Mistake</title><link>https://alexnuttinck.dev/posts/4-the-million-dollar-mistake/</link><pubDate>Mon, 03 Nov 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/4-the-million-dollar-mistake/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/4-the-million-dollar-mistake.png"
alt="Adventures in Uptime - The Million-Dollar Mistake"
&gt;
&lt;p&gt;A major project had just been approved: a collaboration between several partners, with a generous budget to set up new infrastructure.
One partner was in charge of purchasing the servers and hosting them in their datacenter.
The plan was simple: coordinate with everyone, agree on the specifications, and move forward together.&lt;/p&gt;
&lt;p&gt;Well&amp;hellip; that last part didn’t happen.&lt;/p&gt;
&lt;p&gt;Without consulting anyone, the partner decided to order high-end IBM proprietary Big Data servers, proudly announcing the purchase once it was too late to change anything. 💸&lt;/p&gt;</description></item><item><title>The Blue Screen of Container Death</title><link>https://alexnuttinck.dev/posts/3-the-blue-screen-of-container-death/</link><pubDate>Wed, 29 Oct 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/3-the-blue-screen-of-container-death/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/3-the-blue-screen-of-container-death.png"
alt="Adventures in Uptime - The Blue Screen of Container Death"
&gt;
&lt;p&gt;It started as a new and exciting mission.
The client needed help setting up proper CI/CD pipelines and introducing DevOps best practices. Everything sounded great.&lt;/p&gt;
&lt;p&gt;Then came the small detail that hadn’t been mentioned during the initial discussions.&lt;/p&gt;
&lt;p&gt;“Oh, by the way, our application runs on Windows… and we use Windows containers.”&lt;/p&gt;
&lt;p&gt;I froze for a second.
Windows… containers? I didn’t even know those existed before that project.&lt;/p&gt;</description></item><item><title>Cloud Loops</title><link>https://alexnuttinck.dev/posts/2-cloud-loops/</link><pubDate>Wed, 22 Oct 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/2-cloud-loops/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/2-cloud-loops.png"
alt="Adventures in Uptime - Cloud Loops"
&gt;
&lt;p&gt;It happened during a mission for a client.
They had decided to move everything to AWS, hoping to scale faster and more easily than with their old bare-metal self-hosted infrastructure.&lt;/p&gt;
&lt;p&gt;At first, everything looked perfect. Deployments were smoother, scaling was instant, and everyone was proud of how modern it all felt.
The promise of “infinite scalability” seemed within reach.&lt;/p&gt;
&lt;p&gt;But then, the invoices started growing.
Each month, the costs climbed higher, and every time the cluster expanded, the bill followed.&lt;/p&gt;</description></item><item><title>The Reproducibility Crisis</title><link>https://alexnuttinck.dev/posts/1-the-reproducibility-crisis/</link><pubDate>Wed, 15 Oct 2025 10:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/1-the-reproducibility-crisis/</guid><description>&lt;img src="https://alexnuttinck.dev/posts/adventures-in-uptime/1-the-reproducibility-crisis.png"
alt="Adventures in Uptime - The Reproducibility Crisis"
&gt;
&lt;p&gt;This one goes back to one of my very first missions.
I arrived at the client’s office, full of energy, ready to dive into their development environment.&lt;/p&gt;
&lt;p&gt;So I asked the classic first question:&lt;/p&gt;
&lt;p&gt;“Can I get access to the dev environment?”&lt;/p&gt;
&lt;p&gt;The answer? A USB key.
Inside it, a virtual machine image, several gigabytes of it, along with a Word document as the only piece of documentation for the setup. No Git repository, no configuration management, &amp;hellip;&lt;/p&gt;</description></item><item><title>Adventures in Uptime</title><link>https://alexnuttinck.dev/posts/adventures-in-uptime/</link><pubDate>Sun, 12 Oct 2025 09:00:00 +0200</pubDate><guid>https://alexnuttinck.dev/posts/adventures-in-uptime/</guid><description>&lt;p&gt;Adventures in Uptime is a comic series born from real-life stories I’ve experienced during my years working in IT as a sysadmin and DevOps engineer.&lt;/p&gt;
&lt;p&gt;It’s a humorous take on the sometimes absurd, always unpredictable world of technology, where coffee machines crash, servers live under desks, and “everything is a priority.”&lt;/p&gt;
&lt;p&gt;I wanted to capture those everyday anecdotes we all laugh about later. The kind of moments that every engineer, sysadmin, or office worker has lived at least once.
So I decided to turn them into comics.&lt;/p&gt;</description></item></channel></rss>