dotMavriQ Blog

Why I have been moving my personal projects to European infrastructure: openSUSE on the desktop, Bunny.net for media, and GERTY moving from Vultr to Hetzner.

A new preprint models LLM adoption like an epidemic.

Vivaldi let go of uBlock Origin, Google keeps deciding what ad blockers may do, and I am back on Firefox for personal browsing.

Sebastian Bergmann scores PHP in 2026 against a modern language checklist.

Walter White explains the strategy in one line in season two.

A page that shows my fediverse posts, why it is filtered the way it is, and the rebuild that took it from a browser fetching my server on every visit to an archive held in memory.

Every place the LagomCMS spec turned out wrong once I built it, what it looks like in production on this site, and the two lessons.

The specification survived contact with the compiler better than I expected and worse than I claimed.

The 2026 Portuguese tech talent report, the funnel that is left once you filter real openings through real constraints, and why the job market got precarious in a way the AI discourse still refuses to price in.

Six requirements, why OpenResty and LuaJIT, what I borrowed from Kirby, Sanity, Payload, WordPress and Neovim, where those ideas collided, and every decision I locked before writing code.

A design is not finished when there is nothing left to add.

Nothing in the design is mine.

The practical end of the series: the productivity gains that are real, the traps that remain, and how serious developers should use LLMs now.

PHP-native blocks in 7.0, a talent pipeline that is quietly drying up, and what it actually takes to run WordPress at scale in 2026.

LinkedIn is still where software work happens, which is the part that hurts.

The models are useful.

A working genealogy of the consumer LLM wave: the releases that hit the scene, how they were received, and what I actually used them for.

The runtime decision came before anything else, because it decides what is cheap.

What MCP is, where I used it, where it bites, and the rule I ended up with.

There is no shortage of content management systems, so the burden is on me to say what is missing.

I wanted to stay a Firefox person.

After a decade of streaming, I bought a DAP and started syncing FLACs from my own library.

Static site generators, flat-file CMSes, headless APIs, WordPress plugins and what actually makes a CMS slow: what I took from each into LagomCMS.

The received answer is the database, and it is usually wrong.

WordPress has about sixty thousand plugins and that is the reason it has sixty percent of the web, not the editor and not the themes.

A personal note on ergonomics, split keyboards, and the slow physical cost of a life spent at computers.

Between roughly 2013 and 2022 a set of systems appeared that treated the API as the product.

There is a small category of CMS that skipped the database entirely, and it has been quietly correct about several things for over a decade.

Your brain is a battery.

Jekyll landed in 2008 and the pitch was that your blog is a git repository.

Headless means the CMS does not render pages.

Before building LagomCMS I went back to where CMSes came from.

The thing that made WordPress win was not the editor.

A CMS for one person needs no permission system at all.

Everything except the body is easy.

The first version of any CMS has one content type and it is called post.

Open the top twenty CMSes by installs and nineteen of them put your writing in MySQL or Postgres.

Take WordPress and start deleting.

The phrase shows up in trade press around 1995 and 1996, and it is not describing anything you would recognise.

PHP grew up quietly while the JavaScript ecosystem kept tearing itself apart.

Long before a CMS meant a website, it meant a filing cabinet you could not lift.

The one thing a Markdown vault cannot do for you, and the analog tool that handles it.

Habit trackers own the record and throw away the history.