In May 2026, after almost 10 years at RubiconMD, I was laid off along with everyone else in the Spain section.

It didn’t feel great, to be honest, but I’m proud of everything we accomplished there, from Series B and the rushed feature development days to two acquisitions and full corporate transformation. I’m forever grateful for the opportunity I was given by the team back in 2016, all the awesome people I worked with and now count as friends, and everything I’ve learned along the way.

So, I took a short break, and now I’m back on the job market: looking for senior+ roles in platform engineering, technical leadership or good old hands-on development, full-time or contract, fully remote (and happy to travel). If that sounds like something you need, my resumé is here.

Coming back to the market in 2026 means facing the elephant in the room: AI. The same tools that are turning hiring for people like me upside down are the ones I’ve had to fully embrace to keep going. Turns out, I’m actually enjoying it.

A day with an agent

Back in December 2024 I wrote that I needed to review the resumé content and links, and that I definitely should write more. Then, in July 2025, I mentioned it had been my first time in a while without AI agents around, since we were heavily using them on the job. Well. Today, after mulling some ideas in my head, I sat down with the Claude Code CLI agent and, in a single session, “we”:

• wrote an AGENTS.md and a few skills, so agents know how this site works;
• fixed a pile of small template and SEO issues;
• reworked the blog: five full posts per page, a page per tag, a tag cloud, and an archive by year in the sidebar;
• cleaned up 143 messy tags (RAILS, ruby on rails and friends);
• gave the whole site a visual refresh: IBM Plex fonts, a green accent, about 80 characters per line and a 📝 favicon;
• rescued my 31 old CookiesHQ posts: the company’s blog went offline in 2025, but the Internet Archive kept every single article, so the links work again;
• fixed my resumé (wrong dates, a typo, a broken separator) and gave it a “Save as PDF” button;
• rewrote the About page so it actually says what I do, and that I’m looking;
• and split the CSS into tidy files, checking pixel by pixel that nothing changed.

Every one of those would have taken me an evening or a weekend on my own, and realistically most of them would have stayed on the “someday” list forever. They’ve been sitting there for years.

It wasn’t magic, and it wasn’t me just pressing a button either. I still reviewed every change, said no to some suggestions, rewrote bits myself and made the calls. But the distance between “I should really fix that” and “done” has never been shorter.

So, into the future. Allons-y!

If you’re hiring, drop me a line.

From January 2014 to the summer of 2016 I worked remotely from Seville for CookiesHQ, a small Ruby on Rails agency in Bristol founded by Nic and Nathalie Alpi. It was my first remote job for a company abroad, and I was their only remote worker at the time.

Besides building client projects, from startup MVPs to bespoke CRMs, I was one of the regular writers on the company’s technical blog: 31 posts between January 2014 and July 2016, two of them featured in Ruby Weekly (#209 and #212).

In October 2021 CookiesHQ was acquired by one of its clients, Amba Health and Care, and the company was dissolved in May 2023. The website stayed up, unmaintained, for a couple more years, until it went offline in the summer of 2025 and took the blog with it. For each article I used to publish a short post here pointing to it, and all of those turned into dead links. Luckily, the Internet Archive kept a copy of every one of them, so those posts now point to the archived copies instead. Now with agents, compiling the links to the archive is easy peasy and the fix takes almost no time. What a time to be a live.

I learned a lot from Nic, Nathalie, Rob, Gemma, Dennis and all the clients I collaborated with; the foundations of my “Rails persona” was shaped by those years!! :D Going back through these posts with the help of AI agents and bringing them back has been a trip down memory lane I’ll cherish <3

Browse all 31 CookiesHQ posts, from January 2014 to July 2016.

I’m in full Ruby 3.4 upgrade at work and for the Injectable gem we released as OSS and is now an independent organization.

So my personal site should not fall behind! Upgraded the ruby versions to 3.4.5, started using bundler 2.7 in v4 simulation mode, and threw in a bump to bootstrap 5.3.7.

It’s been weird because since at work we’re using Cursor, it’s been my first time in a while without AI agents suggesting code or being there easily accessible for questions. For a minute there I thought I had forgotten how to do this myself haha. Anyway, added an AI generated Changelog because it’s kinda easy to feed a git log to chatgpt and ask to format it.

Would like to try something different to bootstrap tho.

So, I was setting up again my old intel macbook from 2020 because the security restrictions around personal usage of work laptops are becoming a bit too uncomfortable (although standard).

Then I remembered I had this site still going, and that sometime ago I pushed some changes that were never published. So, I started doing some changes to the site while setting up the tools: lazyvim, wezterm, lazygit, tokyo night and caskaydia mono nerd font.

You can tell I’m still a noob at vim because I just wont face the work of adding links for the items in the list above haha. Wanna save me some frustration. There’s always tomorrow for that!

It’s been four years or so, phew. A while indeed. Need to review the resume content and links, and probably add up some new content as well.

I’m learning a lot about technology organizations, scale, behavior and people in these latest years, but need to find the way to post without breaking any policies.

I’ve updated the site to use Bootstrap 5.3 from a CDN. Wanted to try out tailwindCSS but I saw I needed to build and I said hell naw. Another thing to try out some other day.

Also set up a new (better) pic in the home page!

Definitely should write more. Let’s hope that happens soon™.

Some months ago a workmate suggested we upgraded some of our pages from Bootstrap version 3.4 to 4.4. We didn’t do it in the end, since this came up inside a specific project and we didn’t want to fix some other critical pages while doing this upgrade.

Also we had some voices in the team advocating for ditching Bootstrap altogether, so, in the face of several possibilities, inaction took the best of us.

Anyway, while doing this work several differences in the usage of classes in the HTML markup made me curious about Bootstrap 4, so I decided to give it a try on this very site.

This past couple of days I have set this jekyll project to use the latest and greatest from Ruby and Jekyll, removed MaterializeCSS and moved everything to Bootstrap 4. In the meantime, I’ve changed the colorscheme of the site, as well as lots of copy, the layout and navigation (now you get to see my face when you first enter the site!).

I’ve kept everything as vanilla Bootstrap as possible, and it’s fast to use. Looking at the dev tools I see there’s a ton less of CSS than it used to be on previous versions, so that’s a win!