Picking up a new language or framework is always a fun side project, but bringing these into production software at work is always a challenge. It may not be compatible with other technologies you use. The project will need to be maintained for possibly years to come. You will have to convince the rest of your team it's a good idea and they should invest the time to learn.

At Codat, we have used React for our front ends for years but earlier this year we successfully did a project using Svelte. In this talk I will discuss why we decided to use Svelte, how to convince people to use a new language or framework, and why you maybe shouldn't.

How can a software engineer get a world-wind education on the practical tools and tactics of experienced product managers to apply to their own internal platform or developer experience?

With the growing trend of internal tooling teams, often called “platform” or “developer experience”, these teams vary in their size and maturity, from one engineer who cares deeply about developer experience, to funded and strategic platform teams.

A best practice has emerged called “platform as a product”—to applying product and design thinking to platforms. But, how do we practically do that? In this talk Lou will share practical and hands-on tips, advice, tools and techniques for platform teams of any maturity to apply product thinking internally.

Lou previously worked building on platform and developer experience at DAZN and now works as a PM for Gitpod, building developer tools for the masses.

Recently I have been building Menagerie a tool for dispatching many Claude Code agents to complete tasks in parallel while maintaining visibility of progress, status and outputs. agents can show you what they are doing to the web app via playwright and ask for help when the need it.

I think the future of engineering will be based on creating robust agentic systems and amid all the doom and gloom that can exist in the industry these days I want to paint a positive picture of the exciting engineering problems that actually lay ahead of us.

Along with this I'll describe what it has taken me to deploy a system like this, e.g. sandboxing, cursor compatibility, terminals over the network and also how i've made it fun to use (for example you can give your agent a cute avatar, and if you so choose also a top hat)

If you write JS or TS, probably every tool you use daily is currently being rewritten in Rust.

This has advantages (have you heard that Rust is "blazing fast"?), but also potential downsides.

The evolution of JS from the dark days before async/await was fuelled by tooling written in JS. If our tools migrate to a language we don't know, will we lose the ability to control or customize them?

In this talk, I'll explain how in Oxc (the compiler underlying the next generation of the open source Vite bundler), we're trying to "square the circle" - providing rich customisation via plugins written in JS, but maintaining the exceptional performance of Rust - and take you into the nerdy details of memory layouts, allocators, garbage collection, and the tricks that make it possible to have our Rusty cake and eat it with a JS fork.