Manuel de la Peña

This post was written as a guest post for internals-for-interns.com, Jesús Espino’s long-form blog on software internals, and published there first.

Most of the work I do on Docker Sandboxes does not fit in one repository.

T3 Code came through my timeline.

I am a core maintainer of testcontainers-go.

Every time we change a file in a repository, we are changing the worldview of every agent working in that repo.

I am a core maintainer of testcontainers-go.

I am a core maintainer of testcontainers-go.

I am a core maintainer of testcontainers-go.

I am a core maintainer of testcontainers-go and a Docker employee.

I am a core maintainer of testcontainers-go.

I am a core maintainer of testcontainers-go.

I am a core maintainer of testcontainers-go.

Originally written by Enin Kaduk, also published his personal blog: https://www.blueprismo.com/posts/2026/sk8s_testcontainers/ Intro If you ship Kubernetes workloads, you eventually want tests that go beyond helm template and YAML linting.

I am a core maintainer of testcontainers-go.

I typed a message in Telegram.

En el año 2000 me matriculé en un curso de creación de páginas web.

This post was originally published on the Docker Blog on May 1, 2026.

Every PR I open goes through four people.

There is a Synology NAS in my home office that already runs Plex, holds photo backups, and hosts a handful of Docker containers.

I have biomelab open all day.

En enero de 2026, iba con mi familia en un tren a Barcelona.

I started renfe-maps in January using GitHub Copilot’s agent mode directly on GitHub.

Ten years ago, if your company didn’t give you an AWS account, you were stuck spinning up servers under your desk.

Steve Yegge and Gene Kim published six tips for coding with agents while in Sydney for Vibe Coding workshops.

QA has always meant one thing.

In 2019 I was QA Team Lead at Liferay Cloud.

The Level 5 post ended with a promise: “Agent teams and /batch are where the automation goes next.

I kept calling them commands.

I described Level 5 in the six levels post: multiple agents in parallel, each on its own worktree, the IDE for reviews only.

The Manual Pain The Level 5 workflow was a workflow that worked.

In the previous post I described six levels of AI-assisted development, from no AI to fully autonomous agents.

I moved from VS Code to Cursor for the AI chat.

I went from one post a month to publishing every other day.

A colleague recommended Warp.

I needed to test a CLI tool across three platforms.

In Part 1 we set up SLMs with Docker Model Runner.

I used to need a full afternoon to write a blog post.

In Part 1 we covered what SLMs are and how to run them locally with Docker Model Runner.

In Part 1 I showed how to run Small Language Models locally with Docker Model Runner.

I recently gave a talk at ContainerDays London 2026 called “Choosing the Smallest LLM That Won’t Completely Fail You.”

Write specifications first, let something else handle the implementation.

Coding agents are powerful.

I’ve been coding with AI agents for the past year, and recently something clicked: the experience is remarkably similar to driving my Tesla with Autopilot engaged.

The Setup I recently bought an electric car and had a home charger installed.

The Problem: The Dreaded Laptop Switch We’ve all been there.

This post is about a real refactoring experience using AI coding agents on production code.

No AI has been harmed in the making of this post.

“Ever struggled with wiring up self-signed TLS certs for your Go tests and dev servers?

Open source isn’t just about code — it’s about trust, stewardship, and honoring the people and principles that built the foundations we stand on.

With the upcoming v3 release, Fiber is introducing a powerful new abstraction: Services.