# Nuxt co-creator Alexandre Chopin joins Encore

> Source: <https://encore.dev/blog/alexandre-chopin-joins-encore>
> Published: 2026-09-07 12:59:59+00:00

Alexandre joins as Head of Developer Relations to help bring automated infrastructure to more developers and teams.

Today, we're excited to share that Alexandre Chopin, the co-creator of [Nuxt](https://nuxt.com/), has joined Encore as Head of Developer Relations.

Encore lets developers define services and infrastructure directly in application code. It runs that infrastructure locally and automates provisioning in cloud environments, giving developers and AI agents faster feedback loops and a safe path to production. Alexandre joins us to bring this way of building to more teams.

Alexandre co-created Nuxt back in 2016 with the goal of removing the repetitive setup that came with every new Vue application. Much like Encore, Nuxt brought a recurring set of decisions under one set of conventions, giving developers a common foundation they could understand and extend as their application grew.

As agentic development becomes a larger part of how software is built, these primitives and conventions become even more important, giving agents a consistent way to work along with guardrails that make their output harder to get wrong and easier for developers to review and maintain.

As Head of Developer Relations, Alexandre will work with the developers and engineering teams building on Encore, and help shape the roadmap. We'd love to hear about your experience building infrastructure in the cloud, with or without agents, and what still gets in the way. You can reach Alexandre directly on X at [@alexchopin_](https://x.com/alexchopin_).

Welcome to Encore, Alexandre!

Encore's SDK, CLI and runtimes are open source on [GitHub](https://github.com/encoredev/encore), and the [quick start](/docs/quick-start) is the fastest way to get started.

Keep the agent session behind every Encore change, directly in Git.

Maybe we should have just moved everyone to Linux.

The AWS Rust SDK ships no request timeout by default, so one SQS receive on a dead connection can hang a whole consumer with nothing in the logs.
