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.

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.

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.

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.

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.

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.

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.