When Ember introduced its router over a decade ago, it was one of the best in the JavaScript ecosystem. Today, it's showing its age. Limitations, quirks, and patterns that no longer match how we want to build apps. But you can't just rip out the router of a framework that powers thousands of production applications. This talk introduces the Route Manager: a new abstraction layer that lets us modernize Ember's routing concepts.

Nick Schot

Long time Ember.js developer from The Netherlands. Working at Mainmatter. Always interested in anything involving a lot of tinkering including but not limited to: animations, model railways, micro controllers & coffee.

As agentic engineering accelerates code generation, validation needs to keep up. The solution isn't new — it's the engineering culture, tooling, and infrastructure we've pushed for years, now called Harness Engineering. This talk explores what a good Ember harness looks like in practice.

Marco Otte-Witte

Marco has been working in web engineering for about 15 years and has used all kinds of technologies in projects of all kinds of sizes. His company Mainmatter offers custom development, team augmentation, and mentoring. He has worked with Ember for many years and is the original author of ember-simple-auth.

What does it take to keep an Ember app alive and evolving for over a decade?

This talk follows a real-world project that started on Ember 1.11 and is still running today on Ember 6.9, spanning 4,207 days of continuous development without a full rewrite.

Rather than presenting an idealized migration path, this talk focuses on the messy reality: incremental upgrades, dead ends, partial migrations, and legacy code that continues to coexist with modern patterns. It also looks at how teams make decisions when multiple paradigms live side by side in the same codebase.

If you’re maintaining a long-lived Ember app, or wondering whether you should rewrite yours, this talk offers a pragmatic perspective on how to evolve a codebase across multiple generations of framework ideas without starting from scratch.

MB

Michal Bryxi

Tech interviews are often treated like exams: a candidate sweats through a 30-minute coding challenge while someone watches silently, takes notes, and decides their fate. But interviews aren’t exams — they’re conversations. And the way a company runs its interview process tells you just as much about them as it tells them about you.

In this talk, I’ll share what I’ve learned from being on both sides of the table: from designing a hiring process as a solo frontend developer looking for my first peer, to interviewing senior candidates today. We’ll talk about why “I don’t know” is one of the most powerful answers a candidate can give, why how you say something often matters more than what you say, why a rejection is rarely a verdict on your worth as an engineer, and why interviewers carry the responsibility of making the room feel safe.

Whether you’re preparing for your next interview, running them at your company, or just tired of the broken patterns the industry keeps repeating, you’ll leave with a clearer idea of what a good interview looks like — and the red flags that should send you running.

LL

Luis Lorente

As agent-assisted coding gained momentum at Addepar, we were faced with a challenge: how do we get agents to build with modern Ember standards when our codebase contains so many outdated patterns? While Ember’s commitment to backwards compatibility and clear upgrade paths is a gift to humans, it also can be extremely confusing for autonomous agents. I’ll share the real-world steps we’ve taken to infuse guardrails into our 14 year old, 1.5 million line Ember codebase to make coding agents more productive, keep code quality high, and accelerate the modernization of our Ember enterprise monolith. Might we improve the codebase for human engineers in the process?

KP

Kevin Pfefferle