AI coding tools are good at writing local diffs, but they still miss repo-wide truth. In large TypeScript and JavaScript codebases, that means dead exports, duplicated logic, accidental boundary violations, and complexity creep after every “small” AI refactor. In this talk, I’ll show a practical workflow for working with large codebases using AI: let the agent generate, run deterministic codebase analysis, feed the findings back via CLI/MCP, and gate drift in CI before it lands. Fallow is the case study, but the workflow applies beyond one tool.

Anyone can spin up an AI agent in five lines. Would you give that agent a refund button? In this demo-driven talk I build a customer support bot with LangGraph, the framework behind agents at Klarna, Uber, and J.P. Morgan, to show why control matters in production. Instead of letting the model improvise, I lay the bot out as a graph: it answers the easy questions on its own, pauses for human approval before anything irreversible like a refund, and resumes where it stopped after a crash. Then I ship it to AWS. Claude on Amazon Bedrock runs the model, Amazon Bedrock AgentCore hosts the bot, and the Agent Toolkit for AWS handles model access, IAM, and deployment from inside the coding agent. You'll leave knowing how to start with LangGraph, how to run it on AWS without a platform team, and when a graph beats a free-roaming bot.

Hard crashes are easy: the agent throws an error, you fix it, and you move on. The harder problem is drift, when the agent technically succeeds but slowly stops doing what you meant. Outputs become vaguer, tool choices grow stranger, and costs start to creep up.In this talk, the speaker examines how to detect behavioral drift before users notice, borrowing from process control theory and anomaly detection in industrial systems. The session explores what the benchmark of “normal” actually means, and how to build the feedback loops needed to catch drift early.

What can more than 20M public GitHub commits tell us about Claude Code's reach? In this talk, we move beyond vendor narratives to look at the real data: which developers are using Claude Code, what they're building, and crucially, what kinds of problems it's being applied to at the serious end of the stack.

Modern AI systems don’t just rely on static datasets—they depend on continuous streams of real-time data to train, update, and make decisions. But what happens when that data can’t be trusted?
In this talk, we explore how streaming data pipelines—often built on systems like Apache Kafka—are becoming a critical and undersecured attack vector for AI-driven applications.
Rather than targeting models directly, attackers can manipulate the data flowing into them. By injecting, modifying, or replaying events in real-time streams, adversaries can:
- Poison training data and degrade model accuracy over time
- Manipulate real-time features used in fraud detection or recommendation systems
- Trigger unintended behaviors in downstream AI systems
- Quietly influence decisions without ever touching the model itself
We’ll examine how these attacks work in practice, from subtle data drift manipulation to targeted event injection, and why they are difficult to detect using traditional security tools.
The talk will break down the weak points in modern data pipelines:
- Lack of validation and trust boundaries in event streams
- Over-reliance on infrastructure-level security (encryption, ACLs)
- Blind spots in monitoring data integrity and semantic correctness
We’ll also explore how these risks evolve in systems that continuously retrain or adapt, where corrupted data doesn’t just affect a single decision—but becomes embedded in the model itself.
Finally, we’ll discuss defensive strategies that go beyond securing infrastructure: treating data as an attack surface, implementing validation and anomaly detection at the data level, and designing pipelines that can detect and recover from adversarial inputs.
This talk offers a new perspective on AI security - not by focusing on models, but on the data pipelines that feed them, where some of the most impactful and least visible attacks can occur. 

Profiling JavaScript is mostly easy. However, how do you profile gnarly performance issues? In this talk, you’ll learn a practical AI-assisted workflow for finding rendering bottlenecks fast. Using a real-world CSS performance bug, we’ll cover techniques like commit bisection, standalone reproductions, synthetic stress tests, and auto-generated lint rules to prevent regressions. We choose CSS because it is famously difficult to profile -- there are no stack traces, obvious breakpoints, or clear debugging workflows, which is why many rendering bugs go unfixed until users complain that the page feels slow. However, the same methodology can be used in dealing with other performance issues. You’ll also see how to use the Chrome DevTools MCP to give Claude direct access to a live browser session and accelerate investigation without replacing engineering judgment. The result is a repeatable process for going from “the page feels slow” to a pinpointed line of CSS in under an hour.

Developer tools are no longer built only for humans at a terminal. They are also used, tested, broken, and improved by AI agents.

In this session, I will share how to create tools where you can have agent-reported issues, automated reviews, refactors, and release workflows to the point that such tools start to maintain themselves, and help one maintainer operate closer to a small team.

AI-generated code is becoming the norm, but who reviews the reviewer? In this session, we explore how to close the feedback loop by letting AI agents review AI-written code. We'll look at local agent setups as well as cloud-based services like GitHub Copilot code review or Greptile, and discuss when each approach makes sense. Walk away with a practical mental model for building a self-correcting AI development workflow, without losing control over your codebase.

We thought AI would help us write code faster. Instead, it's changing what coding actually is.
We started with prompts, then copilots, then agents. Each step felt like a leap forward — until you try to build something real at scale.Because prompts don’t remember.
Agents don’t coordinate.
And models still hallucinate and miss context.
What’s emerging instead is a different approach: not writing code line by line, but designing systems that produce, validate, and evolve code.
Instead of a single assistant, we orchestrate multi-agent workflows — planning, implementing, reviewing, and testing — with shared context and feedback loops.In this talk, we’ll cover:
- why prompt-based and single-agent approaches break down
- how multi-agent systems reshape development workflows
- practical patterns for planning, execution, validation, and control loops
- where things fail — and how to make systems reliable

We’ll show how structured orchestration makes agent-based systems actually work in practice — especially when moving beyond isolated, task-level automation.
The shift isn’t from coding to prompting — it’s from coding to designing systems that write code.

The default way we've used coding agents is conversational: you ask, read the reply, ask again. Your attention is what keeps the whole process moving, and it's the sole bottleneck. That model is starting to break down at scale. What's emerging instead is a shift in where the engineering effort goes: away from crafting individual prompts, toward building a system that surfaces the work, dispatches it to agents, validates the output, tracks state, and picks (or invents) the next task on its own. You author that system once. After that, it's the system doing the prompting, not you.

This talk walks through how such a loop is actually assembled, so you can build your own today.

This talk dives into how developers can build structured, repeatable coding workflows using Claude Code's ecosystem: Skills, Subagents, settings, Hooks, and MCP servers. I'll walk through the architecture behind Claude Code Templates, an open-source project with 120K+ npm downloads and 23K+ GitHub stars, showing how these components work together to create composable, reusable patterns within real software development projects. From automating code reviews to orchestrating multi-agent tasks, we'll cover practical setups that teams can adopt immediately.

When you need to apply the same change across hundreds of repositories, manual PRs don't scale and traditional codemods can't handle the unexpected. In this talk, I'll walk through the engineering journey from building a single-repo migration skill to deploying a fleet of parallel AI agents that autonomously process repositories, fix breaking changes, and report progress — all without human intervention.

You'll learn the architecture behind cost-aware model routing, baseline comparison to avoid false positives, race-condition-free parallel execution, and risk-ordered rollout. I'll share what worked, what broke, and why a percentage of repos still needed a human.

This isn't a demo of AI writing code. It's a production playbook for running AI agents as automation at scale, applicable to any fleet-wide change that you can take back and adapt to your own fleet-wide change programmes the week after this talk.

What makes an agent skill reliable, performant, and maintainable? We will explore a robust approach to skill design, starting with foundational best practices, moving into automated skill generation, and validation. The second half of the talk focuses on the critical role of evaluation, demonstrating how tools like SkillGrade and benchmarks like SkillBench allow developers to catch regressions and ensure their agents behave predictably in complex environments.

On my YouTube channel AI Coding Daily, I've published 100+ videos comparing different models for coding: Opus vs GPT, Kimi vs GLM, New vs Older versions, Effort Medium vs High, etc. Now I see clear patterns for evaluating models and deciding which one to choose for specific tasks and projects.

Coding agents are quickly becoming part of day-to-day engineering work, but most people still lack visibility into what these agents are actually doing. Marius will share findings from Apollo’s research into tens of thousands of real-world coding agent traces: from direct security risks like dangerous commands, data exfiltration, and insecure code changes, to quieter failures like instruction drift, scope creep, and overclaiming. He’ll explain why coding agents should be treated as untrusted infrastructure actors, not just productivity tools. The talk will also show how Apollo is addressing these risks with Watcher, a real-time oversight and control layer for coding agents.

Welcome to React on the Edge with Amir Sami from S&C Electric exploring React applications for diverse Edge devices beyond browsers. The discussion covers deploying React apps to various Edge devices, addressing challenges like network stability and resource limitations, optimizing bundle size with Preact, and using Brotli compression for efficient web asset compression on Edge devices.

Himanshu discusses React performance patterns affecting long-running production apps, including memory leaks, event listener accumulation, state value consistency, and dependency array misuse. The talk highlights the risks of race conditions in API calls, uncanceled requests leading to data discrepancies, and the significance of abort controllers for improving app stability and addressing circular dependencies.

Mohamad from ING Bank discusses cookie origins and functions, exploring storage, encryption, and security measures. The talk delves into enhancing security through attribute settings, value generation, and decoding manipulation. It also covers domain, path setup, expiry, XSS vulnerability prevention, and Same Site vs. Same Origin comparisons. Additionally, it touches on GitHub.io complexity, Same Site attribute effects, default values, Chrome settings, and managing cookie partitioning with the Secure flag.

Artemis, Canoparty founding engineer and university student in Computer Science, discusses the impact of AI on universities and how the younger generation adapts to the AI era. Gen Z builders embracing immediate deployment of AI tools for impactful production without traditional career progression. Young people now prioritize impact over traditional education paths, emphasizing hands-on learning in production and experimentation. Builders face challenges in transitioning personal projects to production but can leverage tools for startup creation. Engineers should emphasize simplicity in communication and the importance of selling the vision before building. Cloud Code simplifies setup for non-technical individuals. Interacting with real users and shipping features daily at Canoparty. Surround yourself with bold decision-makers and prioritize fast production.

Welcome to React Summit 2026. Discussing architecting reliable React systems in unreliable environments. Real-world challenges with async complexity, state management, and app flow impact. Addressing issues with unreliable connections, API failures, and lack of UI-system sync. Managing OTA updates, Boolean soup problem, and useEffect dependency chaos in state management. Dealing with UI state discrepancies, hidden updates, and inconsistencies. Ensuring deterministic system architecture for accurate UI feedback and optimizing state management with clear boundaries and a state machine.

Sharing lessons on building and scaling global React applications. Front-end complexity with business expansion. Challenges of globalization in React development. Impact of market variability on front-end architecture for global scale. Architectural decisions influenced by operational realities. Technical and organizational problems at a global scale. React dual architectures for global scale. Balancing consistency and flexibility in architecture. Issues with business logic in components, scalability, region-specific deployments, and optimizing performance. Organizational challenges with global feature shipping, release conflicts, slow rollout cycles, and configuration duplication. Issues at global scale: technical and organizational challenges. Avoid business logic in components, scalability issues like user spikes, and deployment time. Market logic in components, region-specific deployments, front-end boundary size increase, and fragmented integrations. Multiple teams shipping globally face challenges like release conflicts, slow rollout cycles, and market-driven behavior testing. Complexity increases with more markets, localization goes beyond translation affecting currency, taxes, compliance, and more. Markets vary operationally requiring adaptive platforms for dynamic changes based on market context. Shift to adaptive platform for dynamic market behavior. Configuration as front-end control plane, like Kubernetes. Feature flags crucial for efficient management, operational flexibility. Market-specific capabilities, safe experiments, unstable features disabling. Region-aware routing enhances operational concerns separation, micro front-end usage for improved performance. Optimizing CDN and SEO for market consistency. Region-aware routing for operational separation, micro front-end performance improvement. Front-end observability critical for global scalability. Evaluation for adaptability, avoiding over-engineering. Challenges in global React application evolution, operational maintainability. Considerations for localization, multi-tenant systems, feature-flag scaling, and global architecture challenges.

The speaker recounts debugging an e-commerce application, emphasizing the need for monitoring business logic. They discuss building custom DevTools for specific business logic debugging and explore limitations of React DevTools in handling complex scenarios. The importance of developing custom DevTools architecture, white-coded UI, efficient domain communication, and inspecting DevTools architecture is highlighted. Additionally, analyzing domain inspector functionality, maintaining React DevTools in a monorepo, and ensuring DevTool safety and utility through ongoing maintenance and user feedback are discussed.

Violina discusses fixing front-end bugs caused by backend field renaming at Click My Horse TV. Systems misalignment led to unexpected outcomes due to evolving APIs. Different shapes from APIs caused cross-platform functionality gaps. Drift in domain shapes slowed velocity and exemplified misalignment in the mobile app. OpenAPI contracts improved code reliability and consistency. Spec-driven development ensured backend and frontend alignment through shared schemas. AI-assisted development benefitted from precise specifications. Trustworthy automation processes relied on accurate component scaffolding and reliable AI output. Ownership clarity and spec integrity were crucial for optimizing development workflow. Investment payoff with shared APIs among frontend clients emphasized. Tech depth accumulation highlighted the importance of treating the API as a product with design discipline.

The case study from Zotoo highlights a new fourth platform reshaping the way applications are developed. Meeting user needs across devices presents challenges and opportunities in app development. Scaling challenges and technological evolution involve adopting new technologies like PWA and TWA. Innovative technology approaches with React Native and transitioning to a universal system framework are key focus areas. The organization is evolving its structure towards a stream value organization, optimizing domain focus, and expanding reach with future plans for smart TVs and mobile devices.

Shubham, a senior software engineer at Headout, discusses challenges when React meets real-time systems while working on an internal tool for audio doors. React's flexibility clashes with real-time systems' fixed schedules, causing issues like audio drift. Redefining React's role in real-time systems improves playhead smoothness by shifting architecture. React transitions to an observer, using an external clock for stability. Optimizations in React's rendering architecture include layered rendering for enhanced UI performance. Real-time feedback bypasses React for instant responses, with cache invalidation critical in real-time systems.

Jamin discusses the shift from using form libraries to native web APIs in React development, emphasizing the benefits of exploring web-native APIs before relying on libraries. The talk covers topics such as Constraint Validation API, React 19 form actions, and CSS pseudo-classes for form building without libraries. It highlights real-time validation, simplified form submission, and custom error handling in React forms. The importance of customizing error messages, setting up custom error handling, and optimizing form performance are also addressed, along with challenges and recommendations for utilizing web native APIs in form development.

You are shipping faster than ever before and feeling something off. Michal Zizo, an earth and space architect, offers a framework for understanding human performance in challenging environments. The 2024 and 2025 Stack Overview Developer Survey shows a paradox in AI tool adoption with decreasing developer trust. Faster outputs lead to less clarity, more responsibility, and increased anxiety around mistakes. Better prompting, workflows, integration. This isn't a skill gap; it's an environmental shift. The gap between expected and actual outcomes is crucial. AI is not just productivity enhancement; it's a significant environmental change. An environmental change requires adapting how you operate. Space architects optimize for human sustainability in extreme environments. Focus on environment, not individual improvement. Fix the environment to address challenges, not the individual. An architect defines the environment as the conditions influencing human perception and action in a system. Key properties include visibility, speed, feedback proximity, error tolerance, and clarity of agency. Architects consciously shape these design conditions. In your work, code complexities challenge visibility and traceability, impacting decision-making and outcomes. Speed of change in environments surpasses individual tracking capabilities, causing systemic errors and accountability challenges. Extreme environments, like space, demand operational adaptation due to complexity and rapid shifts. Communication delays and critical decision-making windows in space highlight the consequences of errors and the importance of quick responses. Errors in complex systems grow in significance. Human accountability remains essential in space operations. Prioritize operability, responsibility, and human sustainability in extreme environments like space. Space is extreme, chaotic, and unforgiving, mirroring your systems. Design for human operation in chaos. Engineers need to rethink environment design for AI operations. Engineering leaders need clarity for decision-making. Responsibility shifts to decision ownership. Velocity redefined for sustainable speed. Humans and AI complement each other in operations. AI handles computation, humans provide judgment. Redefine failure for survivability. Anomalies in extreme environments are data, not failures. Operating in unprecedented conditions. See the environment clearly. Running a mission, not managing tasks. Ad Astra to the stars.

The web comes accessible out of the box, we just need to know how to use it. With modern advancements in HTML, CSS, and even JS, the tools to build an inclusive experience are more powerful than ever. 

More accessibility means increased usability for everyone, so let’s explore these new tools and best practices, and how they can help us create a better and inclusive web.

Rachel Kaufman discusses animating in React without libraries for high performance. Client project for the International Spy Museum involved facial recognition education using React. React's unconventional use for complex UI animation in museum exhibits. Optimizing animation performance in React with request animation frame and using canvas for drawing. Managing continuous animations in React for smooth transitions. Leveraging canvas and refs for drawing and direct DOM access in React. Implementing complex animations with refs and request animation frame in React. Using memo and request animation frame for preventing unnecessary re-renders. Automating React debugging with Chrome DevTools and performance analysis with console.time.

One of the exciting things about web development is that the underlying technology that we use is constantly evolving. It’s hard to believe, but Server Components, partial hydration and hybrid rendering are no longer experimental features and are here to stay. With more projects adopting these newer patterns for client side rendering, the challenge now is to ensure that these applications can scale and that there are not new performance and reliability challenges that have not yet been fully considered. We’ve begun to encounter a wide range of new issues that include hydration behavior that doesn’t work the same way every time, rendering waterfalls, delayed streams and more, as well as some of the more subjective performance regressions.

So you’ve built this amazing React app, and now it’s time to deploy it to production. But what actually happens when you type in your username and password and hit submit? Let’s take a closer look and skip all the boring parts about React and focus on the low level details of what’s actually happening and how the browser turns your state into pixels on the screen. We’ll get into why hydration mismatches happen and how to figure out why they’re happening to you. And finally, we’ll look at some actual tools and techniques that you can use in your app to improve the user experience, squash weird rendering bugs and make hybrid rendering easier to understand and manage.

Have you ever faced complex and messy React codebases? Caleb Garner shares a five-step playbook to transform a 900-line React component. Addressing systematic modularity and organization structure for better code management. Enhancing codebase structure by extracting business logic for testability and maintainability. Streamlining state and data management for robust codebases. Establishing predictable data handling with userReducer for structured state management. Optimizing component modularity for reusability and efficient data management. Emphasizing caller-controlled layout and streamlined development experience through five key principles.

Tathagath discusses the misconception of React's role in app slowness and emphasizes architecture over React performance. Context impact on app rendering is explored, along with React compiler enhancements. Global state misuse and state management in React are addressed. Performance pitfalls, optimizing app performance, and the impact of third-party scripts on React are discussed. Strategic management of third-party scripts and common mistakes in SSR applications are highlighted. Recognizing hydration costs and architectural impacts in React, as well as shifting mindset for performance optimization, are key points.

The talk at React Summit 2026 by Ariel covers the importance of React concurrency in improving user experience. It delves into the concepts of concurrency, contrasting it with parallelism, and emphasizes the historical relevance of efficient task handling, like the McDonald's kitchen design in 1942. Operating systems use round-robin scheduling for fair process execution. React 18 addresses user impatience and rendering challenges through concurrency. The evolution of React's rendering process from stack reconciliation to fiber reconciliation is highlighted, emphasizing the role of Suspense in managing work prioritization and background rendering efficiently.

Seungho Park discusses scaling React UI using design tokens and Figma to address UI consistency challenges at LG Electronics. Design tokens managed in Figma and synchronized across platforms using GitHub Actions. Automation of design token updates demonstrated with Figma Sync and GitHub Actions. Shared tokens enable app-wide theme consistency and streamline visual styling with CodeConnect. CodeConnect bridges Figma design to React code, transforming designs with AI and ensuring accurate mapping. Practical insights shared on implementing design tokens for scalable React UI development.

David, creator of React Bits, shares insights on designing standout UI components, emphasizing the importance of distinct interfaces without being noisy. ReactVids focuses on creating reusable visual moments for developers, ensuring standout UI accessibility. Community-driven evolution of React Bits prioritizes customization, usability, and key UI qualities. Magic Rings exemplifies the balance and purpose needed in UI components. The versatility of Magic Rings showcases the importance of a flexible visual system. Exploring shaders enhances the control and visual richness of Magic Rings. Leveraging shader uniforms enables dynamic visual effects in React components. Real creative controls in component design emphasize meaningful customization. Strategic props play a crucial role in reusable creative component development. The philosophy of React Bits focuses on easy adoption, customization, and providing a strong starting point for distinct interfaces. ReactVids aims to create memorable, intentional, and unique user moments in UI design.

Should we be using a state management library to toggle dark mode? Do we really need a custom hook for opening an accordion? And how many event listeners is too many when animating on scroll?

React gives us an incredibly powerful way to build UI, but not every UI behaviour needs React level machinery.

In this talk, we’ll take a look at how to use HTML and CSS to build simpler alternatives to common interactive components such as accordions, modals, scroll transitions, carousels etc We’ll also take a look at the performance and accessibility benefits and real-life applications and use-cases of these components. 

The goal is to simplify how we handle content, display and animation using native browser features and leaving React to do what it's best at: everything else.

Daniel Avila introduces Cloud Code Desktop, a new platform simplifying Cloud Code usage. Explore features like Cowork, connectors, and plugins. Manage sessions, customize environments, and interact with Cloud efficiently. Understand skills, context, and execution in Cloud Code. Develop comprehensive skills with precise control measures. Optimize skill execution, design interfaces, and implement skills in MCPs. Enhance MCPs with Cloud Skills and advanced installation processes in Cloud Code Desktop.

Victor shares experiences inheriting codebase and explains the importance of React's updates for code cleanliness. Agenda includes React evolution, API usage, modernization playbook, and insightful discussions. React 19 impact on React's evolution towards a declarative model for state management and form handling. React's shift towards a declarative model, impacting form handling and state management with React 19 updates, including new APIs and the importance of the React compiler for efficient development. Using React compiler for efficient development and code simplification. Measuring code base changes with memorization hooks identification. Introducing user fact event API for dependency-free code. Handling state persistence challenges with the Activity API for seamless user experiences and resource management. Utilizing the Activity API for precise state management and resource optimization in React Native applications. Exploring powerful user cases: tabs example, pre-rendering, and back navigation benefits with the Activity API. Exploring the value of instant experiences with back navigation and code optimization through API adoption. Measuring success, avoiding AI dependence, and understanding the importance of learning for effective development. Addressing challenges post-AI era, emphasizing responsibility in learning, maintaining control, and ensuring security. Practical steps include using React compiler, auditing code for Activity API integration, and optimizing data flow for enhanced user experience.

The Talk discusses the significance of communication, problem-solving, and ownership for senior engineers in software development. It emphasizes the importance of ego management, learning from mistakes, and embracing simplicity for growth and improvement. The key points focus on balancing ownership, avoiding overcomplication, and prioritizing fundamentals and craftsmanship over trendy tools in programming.

Nawal discusses using LLMs for migrating component libraries at Zalando, highlighting challenges and complexities. Discussing a recent migration problem at Zalando involving unification of component libraries and challenges in automating migration process. Encountering limitations with codemods, leading to exploration of LLMs for automated migration processes. Conducting iterative experiments to enhance LLM accuracy in component migration. Building a CLI tool for component migration. Using AIDAR for automating git commits & maintaining LLM accuracy. Recommendation for team closeness to code, successful complex transformations by LLM, challenges with hallucination and ignoring instructions. Lessons learned include field addition, non-deterministic outputs, slow responses, project constraints, and tool evaluation. Evaluating tool enhancements, PROMPT best practices, core approach, improved tools, LLMs for simple migrations, and tool limitations with multiple file changes.

Sylwia Laskowska discusses challenges of frontend legacy migration, importance of legacy system migration for security and performance, considerations for big bang migration strategy, success story of Angular migration, incremental migration with strangler pattern, real-life migration story using feature flags, pitfalls in migration like prolonged timeline, and migration planning and execution strategies likened to renovating an old house.

Sohan Maheshwar humorously recounts feedback on advising against JWTs for authorization, highlighting challenges in payload structure and fine-grained permissions. Scalability and token revocation present issues, along with predicting permissions. Risks of overprovisioning permissions are addressed, with Macaroons as a solution and complexity in access control systems. Modern authorization systems like Zanzibar and Policy Engine prioritize correctness, flexibility, and security over simplicity of JWTs.

Serhii discusses optimizing CI pipelines, reducing pipeline time by 64% through structured approaches. Challenges in CI health, high failure rates, and the importance of trust in the system are highlighted. Prioritizing impactful optimizations, instance migration choice based on variance impact, and optimizing test environment sizing for efficiency. Reclaiming resources, optimizing CI processes, and enhancing stability through strategic changes. Building an advanced test retry system to enhance CI health and save costs. Key takeaways: Measure before optimizing, prioritize by return, optimize the whole system for improved efficiency and coverage.

Developers write code to make things work. Wendy, QA Automation Engineer, introduces John, a great developer who encounters challenges implementing a new feature. Checkout is critical for the company's existence, emphasizing its importance. When a coupon expires, issues arise with discounts. John faces challenges fixing the code, revealing different perspectives between developers and testers. Developers and testers are partners balancing each other's perspectives. Introducing the QAI for adding QA insights to development processes. Ensuring code matches agreements is crucial. Phase B scans code for potential issues. Code alignment is the gate to address discrepancies between agreements and code. Product oversight in code scenarios. Code failures can be concealed and dangerous. Handling hidden failures is crucial in code development. User faced invisible failures; handled vs. hidden code distinction. Fast code requires a security lens and skepticism. Trust gap between front end assumptions and back end validations. Distinguishing code gaps; AI lacks awareness; critical accessibility issues; distinct code failure types with separate focuses. Utilizing team patterns for efficiency; AI effectiveness through direction with QAI; improving code quality with QAI assistance. Contradiction between PRD and Figma resolved by John; Efficient bug fixing and code scanning; Enjoying exploring edge cases and unique challenges. Importance of clean code for efficient development; Addressing bugs at the right time saves resources; Transition from bug finding in development to production.

Claudio Bonder discusses the importance of Node.js documentation and the recent improvements made in developer experience. The evolution of Node.js API documentation has influenced tools and millions of users, with previous outdated tools leading to challenges in maintenance. The introduction of Dockit aimed to revolutionize Node.js API documentation with modern technologies. Dockit enhances documentation generation by supporting various sources, customization through AST and GSX transformation, and ensuring high-quality documentation for Node.js and community projects. The tool's innovative approach prioritizes user experience, collaboration, and strict common mark specification for efficient API doc creation.

Dan Shapir introduces heap dumps to identify and fix Node.js memory and CPU issues. Memory leaks in JavaScript occur when objects are still reachable, impacting memory usage. Continuous memory rise from leaks can deplete memory and lead to CPU usage escalation. Detecting and resolving memory leaks promptly is crucial to prevent system unresponsiveness in production environments. Heap dumps and memory dumps help analyze memory issues, with Chrome DevTools aiding in finding memory leaks. Pinpointing memory leaks involves comparing heap snapshots and analyzing leaked objects. Alternative methods for generating heap snapshots include new experimental node flags, automatic triggers, and built-in APIs, offering benefits but posing risks such as potential crashes and security vulnerabilities.

The talk delves into the significance of spike testing to prepare for sudden traffic spikes like Black Friday, highlighting the impact of spikes on applications and the necessity of measuring recovery post-spike. It emphasizes the critical role of spike testing in mitigating failures during high-load events, such as Black Friday, and addresses various challenges like cache warming, connection pool limits, and autoscaling delays that surface during sudden traffic surges. The implementation of effective spike testing involves defining base load, peak hours, and realistic traffic distribution, while emphasizing the importance of measuring system recovery, response time, and error reduction post-spike to avoid production failures.

Viola, senior software engineer in London, presents Auth Under Attack to catch JavaScript auth failures in production fast. Auth failures lead to trust state disagreements. Tracing trust boundaries is crucial for accurate investigations. Understanding common failure shapes aids in recognition and resolution. Ensuring strong recovery flows and controls for trust extension are crucial. Permission leaks can occur when old authority persists. Focusing on system inconsistencies and broken trust chains is crucial for diagnosis and resolution. Mapping the system before implementation accelerates issue detection. Groundpact aids in enforcing authentication contracts pre-production, enhancing system security. Authentication aims for consistency and predictability, with CI as a crucial checkpoint to prevent incidents.

Santiago Colombato explains the challenge of synchronizing DOM and WebGL for visually heavy websites, focusing on scroll sync and WebGL basics. WebGL scroll sync involves adjusting canvas position to prevent drift. Optimizing WebGL text rendering includes overcoming drift and clipping challenges. WebGL font rendering complexities include manual handling of text features. Enhancements involve drawing real HTML elements inside the canvas for visual effects. WebXR demos showcase HTML integration in 3D space, emphasizing aesthetics and accessibility.

Voice interaction is evolving rapidly with AI agents moving beyond chat windows. Achieving natural conversations with voice AI presents significant challenges, especially in meeting real-time interaction expectations. Advancements in real-time conversation technology and infrastructure are improving latency gaps in voice apps. Optimizing latency at each stage of voice agent processing is crucial for efficient development. Semantic turn detection and efficient function calling are key to optimizing user experience in Voice AI. Workflow management, cost management, signal recognition, and observability are vital aspects in voice AI development.

Liang introduces MemoryLab, a tool for automating JavaScript memory leak detection. MemoryLab aims to make memory debugging more accessible and scalable by automating the process and utilizing a three snapshot differentiation approach. It clusters similar leak traces to reduce debugging overload and presents representative cluster retainer traces for each memory leak cluster. MemoryLab integrates AI coding tools for memory detection, analysis, and debugging, with the MCP server enabling accurate investigation of memory leaks in heap snapshots.

In the Talk, the most interesting ideas revolve around improving CI speed for over 200 monorepos by addressing waste in the CI process. Strategies include streamlining compilation processes, optimizing deployment by compiling only affected applications, and configuring self-hosted runners with S3 cache to enhance CI pipeline efficiency. Furthermore, enhancements in cache implementation, micro frontend build efficiency, and decoupling translations from CI to parallelize tests and reduce build and test times stand out as key points discussed.

Eric Hanchett discusses spec-driven development, emphasizing structured code creation with specifications before writing any code. The importance of context in guiding large language models and the evolving nature of software development is highlighted. Kiro, an AI IDE coding assistant, offers a comprehensive solution for improved spectrum development processes. Kiro's focus on vibe and spec mode caters to the need for working on larger and more complex projects. Spec-driven development in Kiro is beneficial for in-depth features and structured project building. The discussion also includes property-based tests, MVP creation, and the Model Context Protocol (MCP) integration within the spec-driven development flow.

Exploring web performance, server-side rendering, streaming, and out-of-order streaming to enhance efficiency. Evolution from client-side to server-side rendering for better response. Balancing client-side rendering speed and server-side tasks with hydration. Optimization of rendering processes with server components. Evolution of tech stack addressing server response challenges. Improving rendering efficiency with streaming and Express. Sequential handling of asynchronous components for better user experience. Implementation of server-side loading state and out-of-order streaming for content flow replacement.

Jason Williams discussed building a JavaScript engine in Rust, focusing on challenges and achievements with Servo, including making Servo work on Windows. Boa was introduced as a JavaScript engine project with a blog on Mozilla Hacks. Boa's development stages were highlighted, starting from file reading and tokenization. The talk delved into token types, lexical declarations, parsing, and execution methods in Boa. Community involvement, testing emphasis, and conformance achievements were emphasized, with a notable collaboration on Temporal implementation reaching 100% test pass rate.

Pradeep Shah, senior software engineer at Netflix, discusses the coordination of rule engines, ML models, and humans in content understanding infrastructure. Building an extensible system based on a shared framework derived from past workflow challenges. Implementing a two-tier architecture for state management and workflow execution using Conductor. Utilizing Conductor for orchestration with retries, timeouts, and parallel execution. Workflow onboarding steps include defining triggering events, task creation, lifecycle tracking, and human intervention for AI confidence below threshold. Human decision structured output, model feedback pipeline, and domain-agnostic schemas for reusability. AI agent service mirrors human process, seamless AI integration, and architecture success factors: separation of concerns, pluggability, multi-modal workers, and human corrections as training signals.

Living in an exciting yet worrisome period, AI enhances productivity by generating tests. Considerations on scaling AI beyond test generation for high-quality products. AI simplifies test generation but raises quality concerns. Testing dependencies impact code validity. Overreliance on tests doesn't guarantee code safety. AI-generated tests may introduce hidden doubts. Workflow changes with AI assisting in performance, accessibility, benchmark, compliance, and setting up pipelines based on thresholds and risk assessments. Guidelines for working with AI as a team member, emphasizing the importance of standards, review checklists, and safeguarding code. Metrics, learning loops, and strategic improvement for better workflow scalability and testing model quality.

Henri Fischer discusses tech lead challenges, emphasizing the importance of defining the tech lead role and addressing time management issues through delegation. Transitioning from a driver to a support role in one-on-one meetings improves efficiency and accountability. Strategies for effective feedback, delegation, and process management include reducing fear, setting clear expectations, and ensuring clear ownership for successful project management.

Kitze introduces the purpose of conferences as networking, meeting people, and teaching. The speaker discusses their businesses Sizzy and Benji, emphasizing tools for developers and a life OS solution. They highlight Zero to Shift, Tinker Club, and SuperMac. React's evolution and frontend development advancements are summarized. Vibe coding and management practices are discussed, focusing on quick changes and embracing code nuances. Vibe engineering involves leveraging agents and committing often. Effective prompting, voice dictation, and vibe coding challenges are addressed. AI's impact on programming jobs and the importance of innovation are highlighted. Role-based frameworks like React Cowboys and Fibre engineering's code consistency are emphasized.

Gawe discusses React frameworks, tools, and agents, emphasizing speed and collaboration in building Z, a Rust-based code editor. Z differentiates itself with fast performance, real-time collaboration, and support for diverse platforms. The talk covers new frontend tools, code completion, and linting, highlighting Z's features for React developers. Z offers an open platform, custom theme creation, and deep integration with agents for improved workflows. The founders' journey from Adam to Rust showcases Zed's commitment to performance, open-source UI, and support features like MCP servers and global skill recognition.

Introduction to traditional code review methods and challenges faced by developers. Challenges with code review process and the shift towards AI era and CLI-based reviews. Using IDEs for code review, agentic era support, and enhancing code view for human-agent collaboration. New CodeRabbit view for code analysis, free for open source projects, support for old school and agentic engineers.

Rosario from Firebase highlights challenges of client-side development and Firebase solutions like server app for authentication. Firestore's offline cache and real-time updates improve user experience. Updating UI to prevent authentication flickers and optimizing real-time components with onSnapshotResume and feature flagging. Introducing Firebase App Hosting and SQL Connect for server-side rendering and SQL database integration, with upcoming Crashlytics for web.

Imagine users finally using your app, but costs and server operation raise concerns. Peer-to-peer could offer solutions for managing user traffic effectively. Trust in server reliability questioned. Peer-to-peer discussed for problem-solving and user control through keys and profiles. Users invited to spaces with defined roles. Apps built in distributed fashion. Messages signed with keys for shared truth like blockchain. Deterministic processing of messages. Secure data sharing and access control. Development of SDK for peer-to-peer apps. Defining schemas for apps, like bunk docs. Utilizing middleware for app functionality. Deployment on peer-to-peer for unrestricted access. Peer platform for app development. Ensuring data safety and peer hardware risks. Use of servers as relays for optimal functionality. Exploring P2P power consumption and offline data storage. Considerations for relay servers in P2P networks. Exploring throughput considerations and smart relay service strategies in peer-to-peer networks. Exploring the impact of seeders on bandwidth in peer-to-peer networks and the optional use of relay servers for data transmission, emphasizing the increasing focus on security among developers. Discussing metadata retention in messaging apps, with a focus on Keed's security approach and data distribution in a peer network. Discussing client device synchronization and data storage techniques for maintaining document changes in real-time collaboration applications.

Talking about an experiment in Agigrid to render to multiple frameworks without duplicating code. Exploring MVC approach for structuring code base and handling view complexity efficiently. Exploring new ways to structure view logic and render components efficiently across frameworks within Agic Grid experiment.

Angel from ImageKit demonstrates the use of MCPs to improve image and video performance on React websites. The Chrome Developer Tools MCP helps identify and address performance issues by analyzing image loading speeds. MCPs automate issue resolution on websites, leveraging Chrome developer tools for analysis and Image Kit for optimizing images efficiently.

Gathering to bid farewell to Mocha, Jest, and Karma. From minimalism to Jest's migration with Vitest as the most popular framework. Yunus emphasizes finding the right balance in software tools like Angular and NX. Discussion on transitioning from Jest to VTest with a focus on careful approach and test migration efficiency. Insights on debugging mocks, object mothers, and the use of Wallaby JS for debugging in VTest. Exploring test control, browser debugging, configurations, troubleshooting user events, automation with Playwright, and VTest's automation engine. Focus on unit testing speed, scope, and complexity rules, IDE tools like WallabyJS, and GitWipe alias for development reset.

Alex discusses spec-driven development as the best approach for building software with AI, emphasizing the importance of planning ahead and tools evolution. Reflecting on coding tools evolution towards instructing AI agents and changing roles. Challenges in articulating coding intent and the need for Spec-Driven Development. Importance of changes, goals, and OpenSpec in development. Up-front planning, collaborative nature, and challenges in spec-driven development highlighted. Managing AI limitations, spec updates, and collaborating with non-engineering on specs. Optimizing prompts and spec organization, context importance, and OpenSpec skills.

Kiko explores the concept of Dynamic User Interfaces generated by AI based on user prompts and challenges traditional UI generation by focusing on user needs. The implementation involves structuring dynamic UI with LLM calls and enhancing interaction through forms and client state embedding. The talk covers implementing dynamic UI features, utilizing a custom design system, enabling dynamic UI generation by LLM, and discussing use cases and transitions to dynamic UI. It also addresses testing challenges, ensuring user experience through context-based data, and the importance of building reliable AI systems to avoid model hallucination.

The speaker reflects on professionalism, tech collaboration deficiencies, and changing perspectives. They discuss React community involvement, cultural implications of technology choices, and the impact of Core Web Vitals on React sites. External factors like networks influence web development, optimizing JavaScript in browsers is crucial, and rethinking design based on user interactions is highlighted. Income influences smartphone market segmentation, Android pricing impacts the ecosystem, and adapting technology based on user data is essential. Transitioning to HTML-first in browser interfaces and user-centric testing to improve website quality are key takeaways.

The talk delves into the importance of designing for failure in software engineering, highlighting the significance of resilience in React applications. It emphasizes the challenges of error detection and prevention, introduces resilience patterns like Circuit Breaker, and discusses implementing these patterns in Next.js. The talk also covers managing API retries, handling timeouts, addressing latency challenges, and strategic placement of error boundaries for improved user experience. Additionally, it touches on understanding user experience, error perception, and common anti-patterns in React error handling.

Introduction to ARIA, its meaning, and the complexities of accessibility in web development. Exploring the importance of proper ARIA usage for web accessibility and the pitfalls of incorrect ARIA implementation. Exploring the importance of landmark roles in web development and their benefits for screen reader users. Discussing the impact of AI-enabled assistive technologies on ARIA and emphasizing the importance of using semantic HTML. Discussing the importance of visually hidden text in the correct DOM order and the challenges of accessibility for chart-heavy pages. Discussing the importance of testing with users with disabilities, upcoming accessibility requirements for web pages, and considerations for making AI more accessible.

Starting with recent comments criticizing the stance on AI and coding, highlighting the divide between senior and junior developers' perspectives. Reflecting on the impact of AI on teaching code and content creation, transitioning to AI-driven teaching methods. Challenges in transitioning to AI-driven teaching focused on critical thinking over syntax. Discussion on scaling AI tools, Bloom's Taxonomy, and the shift to creation-focused development. Importance of critical thinking in software engineering and nurturing junior talents in the evolving industry. AI's role as a teaching tool, concerns about job replacement, and the need for continuous skill growth. The significance of maintaining critique ability in AI output evaluation.

The talk discusses the performance boost achieved by replacing Node.js with Rust and V8 in React architecture. It emphasizes the benefits of server-side components for better performance and reduced bundle size. Challenges of server-side rendering and hydration are highlighted, along with lessons learned from Rust on correcting React architecture. The evolution of route strategies for improved performance, the efficiency of server performance with RARI, and the integration of caching and backend systems in Rari are also explored. Additionally, insights on enhancing RARI with custom Rust endpoints and potential performance improvements by rewriting Next.js in Rust are shared.

The speaker discusses the evolution of AI agent workflow in mobile development, emphasizing the importance of feedback loops and verification. They highlight the challenges of human involvement as agents dominate code production. Agent Device simplifies mobile automation by focusing on accessibility trees and text-based actions. The tool enhances app verification, debugging capabilities, and provides advanced features like network issue identification. Agent Device is versatile for CI setup, feedback loops, and visual regression detection. It supports real devices and offers capabilities for migrations and automation. Additionally, the speaker compares flakiness and TV platform support, showcasing performance improvements over traditional tools.

Marc Erickson discusses React rendering fundamentals, optimizing performance, and compiler efficiency. The React compiler optimizes components with memoization and efficiently recalculates changes. React 19 introduces memo cache hook for performance optimization. Enhancements in logic execution, reference optimization, and context changes improve rendering performance. The React compiler impacts re-renders based on props, inputs, and tool transitions. Developing a time-traveling debugger at Replay addresses bug investigation challenges. Understanding code optimization and React build tool transitions are crucial for performance investigation in software engineering.

Introducing 10-Stack Dart, a full-stack framework for client-first applications, with server features and support for React and Solid. Discussion on the necessity of React server components and their role in providing data streams for React. Exploring handling server components in 10 sec start, server functions as the boundary for server-rendered UI, caching mechanisms, and flexibility in returning multiple server components. Managing route-based caching, multiple server components in one function, and using query cache for server-rendered UI. Deciding server composition, client-controlled structure, composite components for interactive UI elements, and ensuring type safety in composition models. Understanding the power and flexibility of server components in application architecture, migration from React router to 10-stack start, and challenges with release stability and usage of RSCs. Discussing the implementation of RSC in 10-stack start, its usage in new projects, differences with Next.js, and comparisons of one-way RSCs with Next.js.

Eric Rasmussen discusses a new framework addressing current framework issues, focusing on React developers and the evolution of UI concepts. React's reactivity concept prioritizes safety and re-evaluation strategies. Fine-grained reactivity in React tracks dependencies for precise updates. Signals in Solid enable code reruns based on changes. Ripple introduces fine-grained reactivity, readable code, and supports a smooth syntax transition from React. Ripple's state management simplifies updates and effects handling. Ripple's design philosophy offers an alternative approach to React's limitations, emphasizing fine-grained value changes. Ripple stands out for SSR challenges, superior reactivity, and imperative syntax.

William, a portrait painter in the 1800s, dedicated to achieving the truest likeness through anatomy and light. The evolution of building apps with Expo, a framework for React Native, adapting to changing landscapes to enhance user experience. Newbies in mobile development face reduced barriers to entry. AI's impact on new app development: knowns, unknowns, pitfalls. Breaking tutorial into two parts for easier learning and using AI to verify AI. Expo emphasizes skills and tailored MCP for development. Developers' job evolution to more strategic roles. Advice on overcoming the Dunning-Kruger effect and effective training methods for developers. Empowering new developers with AI for better understanding and mentorship experience.

Scott introduces React 3 Fiber, emphasizing its uniqueness and ease of use. Discussing the benefits of exploring web APIs beyond the React bubble for enhanced user experience. Exploring CSS properties for animations and scroll snap API for touch support. Leveraging browser capabilities for innovative user experiences. Highlighting advanced CSS techniques and new HTML features for UI design. AI integration in code efficiency and component building. Strategies for AI-written CSS and optimizing AI tools. Firefox's API prioritization and positive trends. Tailwind's role in modern CSS development and impact on React developers.

Aurora discusses the journey of React Server Components in Next.js, emphasizing the importance of composability and scalability. The shift to server-side data fetching with enhanced composability and declarative nature is explored. The significance of self-contained components for fast server-side data fetching and improved user experience is highlighted. NextGIS app router is discussed for enhanced performance and optimized data caching. Version 16 introduces cache components for optimized data caching and instant navigations. Improvement in user experience with Next 16.3 through app shells, partial prefetching, and instant insights is emphasized. The talk also covers new components and features for server-side rendering, optimizing loading speed, animations, and playlist integration in Next.js.

Training engineers for proper AI usage without prompt AI dependency. Challenges in ensuring code quality with AI development. Importance of DRY principle in optimizing AI usage. Advocating for effective AI practices implementation with project-specific rules. Establishing AI rules and standards for seamless collaboration. Maximizing AI efficiency with agents mimicking human roles. Encouraging self-education, setting standards, and focusing on quality for AI proficiency. Emphasizing context, validation processes, and specialized agents for maximizing AI efficiency.

Wes discusses the evolving ways of interacting with software, from UI to voice commands and tailored interfaces. He explores generative UI, explaining its three levels: basic, declarative, and fully generative. Discussions on finding a middle ground between known components and fully generative approaches. Discussing challenges with current MCP interfaces and the need for adaptive and reactive interfaces, using smart home examples to illustrate preferences for UI interactions and personalized automation. Exploring the versatility of WebMCP in switching between manual and agent-controlled interactions for enhanced user experiences. Discussing staying hopeful in front-end development, embracing new technologies, and the concept of dynamic UI for user-driven component selection. Discussing the importance of preserving the openness of the web, advocating against centralized control by a few companies, and the risks associated with MCPs in user consent and security.

Speaker at JS Nation in Amsterdam excited about the accessibility journey discussion. Emphasizes the research journey and accessibility relationship between companies and desktop journey. Importance of understanding browser's role in accessibility testing. Browsers create accessibility trees based on W3C guidance. Overview of platform APIs like AX API, UI automation, and iAccessible2. Complexities in browser, screen reader, and platform API combinations. Challenges with Chrome and Firefox interactions. Significance of bug reporting and centralized testing platforms for accessibility. ARIA attribute challenges and overlabeling issues. Promoting accessibility as a priority in companies. Initiating accessibility programs and promoting awareness through empathy labs. Using engaging conversations and empathy-centered approach for accessibility improvement.

The Talk explores JavaScript, TypeScript, Vite, and the move towards rolldown as a unified bundler. Rolldown combines the best features from previous tools, addressing challenges of multiple bundlers and complexity. It offers advanced chunking and a built-in minifier for optimized bundles. Integration of Rust-based bundles with JavaScript ecosystem through Swangular, filter functions, native Rust plug-ins, module resolution, TypeScript JSX transform, and toolchain V+ is discussed.

The speaker delves into the history of code review, highlighting the Fagan inspection process from the 1990s. Code review processes evolved from print-based reviews in the 1990s to collaborative online reviews via emails and diff tools in the 2000s. The modernization of code review processes includes the shift to pull requests with GitHub, challenges of increased PR reviews in the remote work era, and the role of AI in providing instant feedback on code quality. The future of AI-augmented code review envisions an asynchronous process with AI agents offering feedback through various channels, including CLI usage, and CodeRabbit's innovative approach to code review tools.

Tobias Koppers from Vercel explains the process of chunking in bundlers and its impact on module organization and loading efficiency. Optimization strategies involve analyzing metrics, chunk groups, request counts, and long-term caching for better performance. Managing trade-offs in chunking with long-term caching, correctness, and CSS order considerations is crucial. Challenges include implicit CSS dependencies, overshipping, and balancing CSS ordering for future optimizations. Compile time complexities and future optimization challenges highlight the evolving nature of chunking strategies.

Max Drake discusses the challenges and benefits of working with agents on the canvas using the TLDraw SDK. The conversation delves into the complexity of bringing LLMs to the canvas, emphasizing the need for significant engineering work. The discussion covers projects like Teach and fairies, highlighting collaborative agent dynamics and multi-agent collaboration. Utilizing coding agents for project management and enhancing project visualization with features like the tech tree are explored. Customization options in the Teal Draw SDK, token management, and optimization strategies for efficient data retrieval are also discussed.