11:15 Am EST - The Life and Times of a Node.js Release

Danielle Adams - Software Engineer, Amazon Web Services

The Node.js release schedule may seem overwhelming to keep up with, maintaining 3 or 4 versions at a time, but there’s no shortage of effort that goes into releases to support the wide use of JavaScript across the web. Many Node.js contributors spend hours discussing APIs, running tests, and preparing release notes for a single release - but how does it all come together? As a releaser, I will discuss the work that goes into a release, tips I’ve picked up along the way, and how every contribution counts. Learn how the Node.js project manages major releases, security releases, long-term support, and everything in between.

11:55 am EST - ElectronJS from the Source

Jacob Groundwater - Manager & Maintainer, Microsoft

Electron is a fast-moving project, and it can be difficult to keep up with the latest best practices, features, and state of the project. Jacob manages the Electron team at GitHub/Microsoft and has been a project maintainer since version 1.0. Beginner accessible but focused on current best practices using Electron, risk mitigation, and how organizations can interact with the project at large.

1:55 pm EST - Debugging Node.js Upgrades

Bethany Griggs - Senior Software Engineer, Red Hat

New major versions of Node.js are often anticipated for all the new features and capabilities they will bring. Though, for many engineering teams upgrading to a new major version can be a daunting process. It’s not always easy to associate the change of behaviour in your application with an entry in the changelog. And it’s not always obvious if or how you need to amend your code to successfully upgrade. In this talk, I’ll share my experiences of helping teams upgrade to new Node.js versions, with some practical shortcuts and tips I’ve learned along the way.

2:35 pm EST - Loosely Coupled - Micro-Frontends And Capital One’s Contact Centers

Stephen Husak - Distinguished Engineer, Capital One

Noah Mandelbaum - Distinguished Engineer, Capital One

Capital One’s Contact Center application allows customer service agents to help our customers 24/7 across different channels of engagement including phone and chat. At the same time, up to 50 teams are developing new intent, making changes, and releasing in near real-time to accommodate shifting business, legal and regulatory needs. This talk will provide an overview of the history of challenges that were overcome to move from a pure monolith system to a platform that provides for fast, high-quality delivery with a minimum of friction among teams while establishing code consistency, open communication and open collaboration across our enterprise. We will go over the high level architecture of the application as well as provide the lessons we have learned along the way in utilizing the Node.js/JavaScript ecosystem for our solution.

3:15 pm EST - Securing the npm Ecosystem

Abigail Cabunoc Mayes - Senior Program Manager, GitHub

In this breakout session, Abby will go over the work GitHub is doing to secure the npm ecosystem. From 2FA to Sigstore, we are working to secure the open source we all depend on.

4:15pm EST - The JavaScript Survival Guide for Financial Services

Robin Ginn - Executive Director, OpenJS Foundation

Daniel Cousineau - Senior Engineering Manager, GoDaddy

With more than 98 percent of the world’s websites using JavaScript, it’s the foundation for online commerce, economic growth, and innovation. Hear from OpenJS leadership on recent investments in security, infrastructure and developer programs to ensure the long-term viability of important technologies that the financial services industry depends upon, including Node.js, Electron, jQuery, webpack, Jest and more.

4:55PM EST - How Brex Leverages Backstage for Fintech Engineering Growth

James Russo - Staff Software Engineer, Tech Lead of Backend Developer Platform Group, Brex

As a high-growth fintech startup with multiple integrated partners, Brex was doubling its engineering headcount year over year for multiple years in a row. With this rapid growth came an ever-increasing number of software developers and tools to manage that software. In order to wrangle this rapid growth, we looked to build an internal developer platform which led us to Backstage. We quickly decided to move forward with Backstage because it had a cohesive ecosystem and was extensible. Over the past couple of years we have been adopting Backstage throughout our engineering organization and this presentation outlines our adoption journey and learnings.

Interested in learning more about OSFF? Check out our website for the full schedule and register today!