Arguing with Grok until PHP does what I want

Somewhat simple PHP script to read and extract information from images to a json. Fetches dimensions, EXIF taken date, adds tags based on folder structure. Built from arguing with Grok… refined, fixed, and mastered by Claude Code. Like Lemon said, “Grok stupid bro”.

If I could offer you only one tip for the future, choose life.
Choose Claude.

Script used in process to make gallery function for Killing Heat website.

// Meloslave.com // The First Real Project of 2026

Out of all the domains at my fingertips, Meloslave.com was the most straightforward project to approach. I needed a quick fix, a site that could go live fast without too many distractions or variable factors to contemplate. Glenn Thomas Andersen being an artist, musician and a DJ, my first thought was that Meloslave.com needed a linktree (link in bio). His main activity is on Spotify, where people stream his  music (he has 3.8K monthly listeners), so you don’t really need an elaborate website with pages, posts or galleries. You can find all of that on Meloslave’s social media accounts, hence the linktree.

Click here to view Meloslave.com 

The main goal was to figure out video playback as a background, together with social media sharing details, which I must say is rather easy with Grok and Claude at my disposal. Grok may not be perfect, but he does all the heavy lifting, all the noise and chatter, then I ask Claude to refine. Actually, I did ask Chad too… and while he does have good input, my attitude towards The Woke Chad is mostly fuck off. Come to think of it, are alle the LLMs male?

Doing a new thing here where I just link directly to the files on Meloslave.com. Should that work? Weird that it worked… I might have to learn GitHub, eventually.

Did you know? The video used in background was shot on location in Thailand. Click here to see the music video!


Update 17-03-26:
Added code reviewed by Claude into post, rather than fetching from file.

The Landing of Parked Domains

Tackling a sudden comeback to web development hasn’t been easy on my mind. Figuring out where to begin, what to start with, how to approach a long forgotten and perhaps even dead hobby within me… did take a couple rounds. Staring down the barrel of a forced retirement from being a layger gnome, I had to consider the future. My the future.

While I still constantly discuss with the endless voices of myself, the year of the future offered something I didn’t have last time I was active with webdev…

We marveled at our own magnificence as we gave birth to AI.

— Morpheus, The Matrix (1999)

Perhaps not quite the Skynet we were promised, so I will refrain from misusing the term. Glorified Google. Spell Checker on Steroids. Large Language Models… Chad? Grok? Claude? Any of the stupid terms we give each night? Anywho, this technology made it easier for me to discuss with a different entity other than myselves, one that could do the Google for me, collect information at light speed, and help me reach a starting point.

So we landed on making a template for my parked domains. Me, Myself and Grok. We have spun the tiny totem that will eventually weave itself into existence, as my brain reconnects to the web of dev. Or so to speak.

So here we are… screenshots of the parked-domain landings I’ve built so far, plus the code to view them. In time, each parking spot will become a real site, and this post will be the archive of those forgotten placeholders. Also I needed to kickstart writing about whatever the fuck it is that I’m doing…

I won’t go too much into details, I wanted a simple parked setup that would display something slightly different for each domain, with a countdown that is random (giving myself endless time to actually make a real website).

Built with the help of Grok, based on Bootstrap, using Grok Imagine to generate background images. Also I might’ve written a line or two…


Update 17-03-26:
Added refactored code into post, rather than fetching from file. Remember to add “learning GitHub” to ToDo-list.

Change name of menu item in Theme Options Framework

Legacy

 

High contrast (WCAG)

Legacy

 

Remove unnecessary body classes generated by WordPress

Legacy

 

Get parent page ID in WordPress

Legacy