Ten years ago, we pulled libraries and frameworks into our projects not because we wanted to — but because we had to. It was the only way to survive the “browser wars” era and avoid drowning in spaghetti code. Frameworks became our спасіння, and we got used to them. Since then, the web has evolved — but our habits haven’t. HTML, CSS, and JavaScript have made huge leaps forward, yet we still automatically pull in megabytes of abstractions just to render a simple product list — and proudly call it a “modern stack.” It’s time to ask ourselves some uncomfortable questions: • What problems do frameworks actually solve today — beyond our fear of being left alone with plain JavaScript? • Where is the line where “developer comfort” turns into unnecessary weight for the product? • Have frameworks become just a convenient shield — hiding our reluctance to truly understand the platform? I’m not saying we should delete React tomorrow (although…). But I do want to explore this: do frameworks still solve real technical problems — or are we just building another “Hello World” in React because we’ve forgotten how to do it any other way?

Many consider frontend architecture to be a meme. And honestly, there are reasons for that. But we build it anyway — on a real product, in a real migration. This talk is about how we're moving a large e-commerce platform from a Clojure monolith to a separate frontend: thin client approach, React as a UI library, and Next.js as a system detail — not the core. How well it actually works, where reality diverges from diagrams and initial plans. No canonical recipes — just real experience from a live product.

Turbo-guide to the hottest Chrome DevTools updates for 2024–2025 that radically transform the frontend development workflow. We will dive into the integration of Gemini AI, which now acts as your personal super-analyst inside the Performance Panel. Beyond AI, we will explore enhanced performance analysis with expanded Core Web Vitals support and calibrated CPU throttling presets, helping you turn the battle with the “slippery” LCP into a clear detective-style investigation. Along with hardcore debugging, we will cover new styling and usability features such as scroll-driven animations and improved work with CSS Nesting, Autofill, and many other perks. We’ll take a closer look at MCP, because if you don’t know what MCP is — you won’t get paid in 2026.

In the age of AI, anyone can generate code — even your team lead or the baker next door. But who ensures its quality? This talk will show why TDD is more relevant than ever, how to tell a good test from a bad one, make AI write proper code from the start, and why discipline and architectural thinking save both your nerves and your projects.

This talk will show how to boost developer productivity with AI tools in Cursor — from automated code reading and writing to building custom AI teammates and end-to-end feature pipelines.

In many projects, hooks have become a reflex: they’re added automatically, even where they aren’t needed. But every unnecessary hook adds extra complexity—often without any benefit. In this talk, we’ll explore when hooks are unnecessary and how to write simpler, more readable code without redundant use*.

Do you remember the times when we spent a week configuring Webpack before even starting to code? Now we have a builder deeply integrated with a framework. Do you even know what Vite configuration you have inside your Next.js or Remix.js application? But do we even need this? What are we missing to forget about all these nasty bundlers?! Let's find out!

Why are modern frameworks once again trying to reinvent reactivity — and what do signals have to do with it? In this talk, we’ll take a look at signals as an attempt to give JavaScript developers fine-grained reactivity tools without extra code, proxies, or memoization. The problem they aim to solve is as old as frontend itself: how to update only what needs updating — and do it predictably. We’ll explore how this approach works, which frameworks have already adopted it, and what the current TC39 proposal means. Most importantly — do signals actually solve the problem, or are they just introducing a new layer of complexity with different syntax?

This talk is a lighthearted yet painfully familiar existential crisis of a frontend developer. We’ll start with simple DOM manipulation, walk through jQuery, SPA, React, and end with some thoughts on server-side rendering — with the help of a certain Twitter thread that turned out to be wiser than most textbooks.

This talk begins with a brief overview of frontend history, mentioning the era of AngularJS dominance and the reasons for its subsequent decline in popularity (particularly its complexity and the rise of React)