Schedule

Let's look at why expressions and operators need to be treated as interfaces, show how asynchronous get/set work, what await new has to do with it, and how to make self-reproducible instances of classes.

Are web vitals really enough for you? Let's discuss why a product might have poor performance despite green metrics and what to do about it.

I'll tell you how we set up observability for almost 1,000 microfrontends, what tools we use, and how it differs from observability of services.

"Caching at the front" is a phrase that evokes a sense of maximum understanding for every front-end. I'll tell you why this can be a pain in a large project, and together we'll design a system that can adapt to different requirements.

We'll predict errors in our code, and we'll also talk about the future of testing and why it should be a concern for any modern engineer. We'll use real-life cases to demonstrate how to balance speed, quality, and risk in practice and how to prioritize functionality coverage.

We are on the verge of a revolution in layout related to a new approach—reactive CSS. Here the usual display logic "shifts" from JavaScript to styles, and the entire appearance of the component depends on CSS state variables.

This workshop is for those who want to learn how to set up a project for full-fledged testing at all levels, rather than just writing unit tests.

The talk is dedicated to an innovative development — an AI agent (codenamed "BroPilot"), which turns the Yandex Browser into an intelligent assistant capable of autonomously performing user tasks on the Internet.

Launching a fully functional version of UT99 with running multiplayer in the browser.

I'll show you my own agent on Node.js and client rendering via web-components in the spirit of A2UI.

How WebMCP reduces token consumption by providing action contracts instead of full DOM context, and in what scenarios this really impacts the cost and reliability of agents.

In my talk, I'll walk you through how we progressed from using models "in a window" to a well-established prompt reuse system. No complicated stuff — just ideas proven by practice.

From language models to agents, from agents to orchestration. Theory, practice, and open-source code.

I'll show you how a small team can build an AI-powered bug-fix automation pipeline — from Jira ticket to pull request. I'll break down what actually works, what's still a pain point, and share the concrete practices, mistakes, and patterns we've developed over several months of implementation.

Let's look at common myths about Angular and analyze how modern features of the framework (Signals, zoneless, SSR) are changing the approach to development. Let's also look at the ecosystem, including Analog.js, and future changes.

Has React really lost the performance race? Or is it quite capable of competing with frameworks like SolidJS?

In this talk, we will discuss non-trivial approaches to implementing components, support for existing components, and current trends in UI libraries that can be immediately incorporated into your projects.

Let's look at which architectural solutions in Vuetify turned out to be successful, and which ones made themselves felt only at the late stages of development, why the "one design system for all" approach stopped working, and how real product requirements pushed us to create Vuetify0.

Analysis of BFF in the plug-in frontend and practical architecture of the Host BFF with command plugins from a real product.

Using live examples, let's see what should be reused in modern web development.

Sometimes I feel that FSD has gained popularity undeservedly, and despite all the disadvantages it continues to be used.

I will analyze the problems of this architectural methodology,  the available alternatives and propose a worthy solution—the FDA.

How I faced the task of moving to a new design system with three conditions.

How to build a clean, predictable backend in Node.js using only the platform’s built‑in modules and a custom minimalist router—without Express or any other frameworks.

How can oilplan be used to work with memory, what tools do the guys who actively participate in the nodejs issue recommend using, and what problems do we face.

I will tell you about a real production incident in a Node.js + Express service behind Nginx (with SSR and multiple backends).

Is it possible to build a JS-based smart home?

A brief overview of the rocket engines design.

Creative graphics are not magic, but an engineering simulator. On the demo, I'll show you how to think frame by frame with Three.js and Phaser, profile the render, and apply these skills to improve performance in other frontend projects.

Let's see how 4D and non-Euclidean geometry are rendered. Grab your laptops, and let's fly through some mind-bending spaces together!

Is it possible to optimize the frontend without JS? Let's try it!

Let's take a step-by-step look at specific techniques: queryObjects, Memory Allocation Timeline, and the three snapshots method.

Cases when PWA is a conscious choice, and cases when it is a path to failure that requires native development.

How a front-end developer can distinguish a bad UX from a good one without the help of a designer.

In this talk, I’ll share configurations, techniques, and scripts that allow us to type not only the code itself, but also the boundaries between application layers.

We’ll explore how to make contracts verifiable across MobX stores, routing, CSS Modules and CSS Variables, ENV configs, i18next, API responses, feature toggles, Storybook, and even icons — reducing system fragility at the seams between them. And of course, we’ll also address performance.

Let's take a step-by-step look at specific techniques: queryObjects, Memory Allocation Timeline, and the three snapshots method.

I'll tell you what should be on your CV and show you life hacks. I will give specific and illustrative examples of a CV in Do and Don't format.

The format of the workshop is live coding in the spirit of pair programming. An educational application has been prepared for the demonstration, which simulates a real project (online store).

Interactive debates on technology, career and work in frontend focused on AI and the hiring market.

Try being a speaker and talk about everything special to you at the conference. 

Code in the Dark is a layout competition (HTML, CSS) where four participants simultaneously attempt to replicate a design using only a mockup.

Summing up the results of the conference, remembering the highlights and talking about plans.