AI coding experiments, Ansible chaos, and that moment when the machine stares back at you… 👀


🧠 My AI Workflow So Far

I’ve been using ChatGPT for over a year now — pretty much daily.

Mostly for generating images, writing code, polishing wording, creating templates,
and of course for researching and summarizing texts.

Basically: if there’s a repetitive brain task, I outsource it to silicon. 🤓💡

🔄 Plot Twist: Trying Claude

Today, kind of by accident, I canceled ChatGPT and decided to try Claude instead.
I’ve read a lot about it, and from what I gather, it might actually have the edge when it comes to coding.

As a full-time nerd, I obviously had to test this theory immediately.
Because reading about tools is nice — but throwing them into production chaos is nicer. 😄

💻 VS Code + Claude Plugin = Nerd Playground

I currently love working with Visual Studio Code, so what really interested me
was integrating Claude via a plugin.

And now I have this setup:

  • VS Code
  • An Ansible playbook
  • 8 roles
  • A chat editor directly connected to Claude

Which basically means: the AI is now sitting right inside my dev environment.
Not watching… totally not watching… 👀

🚀 The Experiment

I wrote into the chat:

“Optimize my Ansible code, apply best practices…”

…and BÄÄÄMM!! 💥

The thing has been grinding away for minutes now — finding one issue after another.
Claude basically has full access to the Ansible codebase and is tearing through it like a senior DevOps engineer on caffeine. ☕🐧

Slightly terrifying. Slightly impressive. Definitely nerd-satisfying.

😱 Meanwhile, In My Head… (The Nerd Image Vibes)

If I had to visualize this moment, it would look exactly like that image:

A slightly panicking nerd in a server room, sweating, clutching his laptop,
while an evil-looking AI watches him intensely from a glowing screen.

And yes — he’s still wearing sunglasses. Indoors. At night. In a server room. 😎

Because when an AI starts reviewing your infrastructure code,
you either:

  • stay cool
  • pretend you planned everything
  • or whisper: “Please don’t read my TODO comments…” 😬

The vibe is somewhere between:
“This is amazing”
and

“Oh no… it sees everything.”

⏳ Letting It Cook

For now, I’m just letting Claude do its thing.

Tomorrow I’ll go through the code, check the optimizations, and see:

  • how good the improvements actually are
  • whether I still understand my own infrastructure
  • and if not… I’ll just have Claude generate documentation and explanations too 😄

Because why panic when you can automate your understanding?

Nerd conclusion:
AI writes code, fixes code, explains code… and quietly judges your old code. 🤖👀

Next step: see whether Claude becomes my new DevOps co-pilot — or my future replacement. 😅

By raphael

Leave a Reply