They hired me to add features. The codebase had less than 1% test coverage. Azure was retiring .NET 8, but upgrading seemed too hard, so they'd waited years. The kind of problems you know you should fix but never do.

Four weeks later: 560 commits, 65% test coverage, 13 database improvements, and yes, we shipped features too. Two programmers, four hours a day, one $17/month Claude subscription.

Here's what nobody tells you about AI: Day one, it took us eight hours to fix one nullable reference. Week four, I did fifty in under an hour with five minutes of my time. We didn't get faster because AI got smarter. We got faster because we built the infrastructure—scripts, CLIs, knowledge docs—that let AI scale what we'd already figured out.

This is a field report on what's actually possible when you stop thinking "AI makes me faster" and start thinking "AI lets me solve problems that used to be too expensive to touch."

Come see how we got a codebase under control.

It’s been a while since we last met but the Svelte team have kept shipping exciting new features! Let’s go through the changelog and discuss the most interesting additions to Svelte and SvelteKit so far this year.

We often add animations to "delight" users, but at what cost to our Lighthouse scores? As a solo developer, I need UIs that look high-end without the maintenance overhead of heavy libraries. In this talk, I’ll break down my "Animation Decision Matrix, a three-tier strategy for choosing the right tool for the job. We’ll explore Vue’s <Transition>, how the Web Animations API keeps the main thread free, and exactly when it's worth using the 30kb involved in GSAP. Expect a pragmatic look at the browser rendering pipeline.

I know, I know - another AI talk. But hear me out: this one isn't about prompts, it isn't about replacing developers, and ChatGPT won't be mentioned once. It's about what happens when you stop using AI as a fancy autocomplete and start wiring it up with tools, memory, and the ability to orchestrate other agents. We'll look at how Claude skills and plugins actually work, build a small agent pipeline live, and be honest about where it breaks. You might leave with ideas you can actually use on day-to-day bases.

What does it take to turn a from-scratch JavaScript engine into production software?

Johannes will go into detail on spec conformance, CI and benchmarking infrastructure, and how to catch regressions before they happen. There will also be live demos of what you can build when you can shape the entire runtime, plus a closer look at the corners of JavaScript most of us never have to think about.

Johannes has spent his professional career working on JavaScript across web, mobile and backend solutions. With agentic engineering, he has been looking for more complex and sophisticated projects to use AI with.

Modern JavaScript applications rarely fail because of a broken function. They fail at the boundaries: APIs, authentication, feature flags, browser APIs, payments and third-party services.

From a real journey at scale with over 1.3 million transactions, Eduardo will explore an outside-in testing strategy that focuses on what matters most: the interactions between your application and the outside world.

You’ll leave with practical techniques to build confidence, reduce brittle tests and ship changes with greater certainty, regardless of your JavaScript framework.

1771 Technologies is building LyteNyte Grid, a lightning-fast React data grid for complex, high-volume applications.

Lee will give a high-level overview of how LyteNyte Grid achieved best-in-class performance, with a small look at the technical details behind it.

Matias shares some slides from previous talks showcasing what npmx is, and why it exists, as well as the community that's grown around it