I write this sitting in an airport on the way to Germany, where I will be meeting with leaders several European research agencies to discuss how we can ensure the resilience of infrastructure in an increasingly tumultuous world

As scientific data become increasingly distributed across specialised repositories, the challenge is no longer finding information but connecting it.

A little bit of what I have been working on for the last couple of years as part of the Fragment Screen project coordinated by the Day Job

There is a reasonable argument that the best way to design an interoperability standard for EOSC service catalogues is to look at what nodes are actually publishing before deciding what to mandate. So I pulled 239 service records from the EOSC Beyond sandbox, compared them against the EEN specification and a draft EEN-to-DCAT field mapping being developed within the working group, and mapped the results across all three schemas. The short version: the divergence between the two formats in active production use is real, it is already in the wild, and the empirical common core is smaller than either spec requires. Which is, somewhat inconveniently, the strongest possible argument for starting there.

The first EOSC catalogue hackathon proved federation could work. The second made it more real: messier, broader, and much more useful. With EOSC Beyond, Data Terra, ENVRI, EMBRC, EGI, GRNET, and the Life Science Connect node in the room, we moved from “can catalogues talk?” to the harder question: “can they understand each other well enough to build on?”

GitLab.com

Following on from the #EOSC hackathon I ran a few weeks ago, I thought I would write a brief implementation guide for any other nodes that want to try playing with what we did

Scratching an itch for my team, I build a Doodle clone over a couple of hours while enjoying some lovely wine in a sunny pub garden.

Not wanting to bury the lede; I built a todo list application to replace my Remember The Milk subscription, entirely using free AI tools, on a Saturday morning. Here's how...

Last week we had a hackathon during which time we successfully demonstrated discovery and federation of catalogues between EOSC nodes

Autistic note keeping, FTW!

As we rush towards the AI future, it is important to take a beat to consider that AI security is... terrible.

Based on work done in EOSC United, I have drafted how one might map the required fields from the EOSC EU Node service catalogue schema to DCAT.

Writing code is not what a developer gets paid for in 2026, but that doesn't mean you can get away without knowing how to code. AI has disrupted the software industry. The code is getting cheaper. Judgment is not

Got a little impatient so started making a thing

AI Agents are people too, and in the future they're going to want to use your services.

On Friday, I oriented my team about AI-driven development, discussing key concepts, benefits, risks, and personal case studies. We engaged in thoughtful discussions, highlighting shared concerns. I…

I realise I’ve been working on it for years, but never really talked about it. So, what is this ARIA thing anyway? I hear you ask…