February 26-28, 2025
Montreal, Canada

Adam L Barrett

Adam L Barrett

Adam L Barrett is a JavaScript and Front-End consultant, a contributor to open source, and avid bike-shedder. Adam believes, when writing conference bios, he should probably mention his two children, his love of movies and probably his hobbies, like hosting a board game podcast, to help the reader connect with him as a person, but ...well, that sounds sort of manipulative so Adam has chosen not to. Adam is above that.

Proposals - Montreal 2025

Front to back, Never back to front

When you're just starting out, often web dev classes and tutorials start with "design a schema". This one, tiny mistake may be the root cause of billions of dollars lost, time wasted, and unnecessary complexity embedded in countless applications The problem: coding "back-to-front" Let me show you how the simple idea of coding "front-to-back" can reduce complexity, increase security, and help keep your codebase performant and maintainable

Perfect Progressive Enhancement with SvelteKit

Progressive Enhancement: the design philosophy where you code to offer your core functionality and content to as wide an audience as possible, and then, for each user, individually enhance the user experience based on the modern features supported by their browser. Using the extremely popular web framework SvelteKit, I will show you how to solve some particularly tricky web interactions while maintaining progressive enhancement perfectly.

Astro for Everything!

Astro is an amazing web framework for content-driven websites, and they will be the first to tell you it was designed specifically for marketing sites, blogs, e-commerce websites. BUT… let me tell you, not only is Astro just as good as any of the major frameworks for building complex web applications, some of Astro's unique features solve real problems common in mid-to-enterprise application development! Come and find out what I mean.

JS Signals

JavaScript has a new primitive for reactive programming: Signals. Almost all the major frameworks have adopted them and there is even a TC39 proposal to add signals directly into the language. But what do they do? In this talk we will dig deep into the (imho) poorly named Signal, discuss how they are used in modern programming, demystify them by implementing our own in JS, and address the current status of the ECMAScript Signals proposal.