Talk on React Native as a Gaming UI System in Unreal Engine, covering the integration journey, importance in mobile app development, and current methods of game UI creation. Innovative approach of rendering UI in games using a browser headlessly onto a texture. Challenges and benefits of using React Native for game UIs, including handling JavaScript overrides and showcasing a demo. Exploration of applying shaders to React Native UI in a gaming context and invitation to engage with React Native on Unreal Engine for future game development.

The Talk delves into the impact of LLMs on engineering workflows, emphasizing the shift towards AI for code writing efficiency. It highlights the importance of problem-solving abilities and product development in hiring practices. LLMs enhance productivity for developers, designers, and product managers, enabling faster iterations and collaboration. Efficient product workflows are achieved through simultaneous UI and code work using Builder.io. Task delegation is streamlined with async agents and Builder bots, optimizing project editing and code management. Integration with tools like VS Code and Figma streamlines design and code editing, enhancing collaboration and workflow automation.

Bree discusses the evolution of React styling with React 19, Tailwind, and server-side rendering components, emphasizing static CSS generation. The shift towards native CSS and CSS modules for better scalability and control, and the rise in popularity of Tailwind CSS for its utility-first approach. Challenges in React styling implementations include runtime libraries, streaming UI, scalable theming, and overhead reduction. Panda CSS emerges as a potential successor to Tailwind CSS, offering a blend of CSS and JS experience. Styling decisions in 2025 are philosophical, with Tailwind for speed, Panda CSS for complex design systems, and CSS modules for stability.

Introducing Node.js security overview, defining vulnerabilities, non-vulnerabilities, and preventive measures. Discussing Node.js API input validation, real vulnerabilities like HTTP server crashes, and the importance of Node.js security in widely used platforms. Discussing the importance of Node.js maintenance, the introduction of experimental permissions in Node.js 20, and the seatbelt philosophy to protect against malicious code. Discussing the importance of maintaining up-to-date Node.js versions and using tools like npx isMyNodeVulnerable for security checks. Discussing the importance of Node.js security releases, funding, and dependency vulnerability assessment for a safer Node.js environment. Using Node.js Dependency Vulnerability Assessment to evaluate and address potential vulnerabilities, ensuring automated security checks and updates for a safer Node.js environment. Automating Node.js security release process, including configuration files for dependencies, extensive testing across various environments, and creating security release issues and blog posts automatically. Support for various environments, extensive testing with over 55 suites and 5,000 unit tests, automation efforts to streamline processes, and the establishment of a maintenance threat model for enhanced security measures. For a single pull request, it takes six hours to run tests, automation efforts in progress, maintenance threat model to address security risks, permission model roadmap, ongoing discussions on security reports, and plans for the Node.js Collaborator Summit. Active community involvement in Node.js security development, four security releases from 2024 to 2026 addressing various vulnerabilities, end-of-life version strategy with Node.js 16 and 18 having high weekly downloads, and the approach to issuing CVEs for end-of-life versions. Node.js project's strategy adjustment for CVEs to include end-of-life versions, importance of Node.js threat model, trust boundaries, and developer responsibilities. Node.js protection against network data, upgrade recommendations for different Node.js versions, and upcoming changes in Node.js release schedule.

The Talk delves into agent decoding in Cloud Code, emphasizing the importance of planning, acting, and verifying changes systematically. It explores maximizing efficiency through Cloud Code acting as an agent, reasoning, reading, writing code, and using tools for successful outcomes. The discussion covers enhancing task planning, utilizing subagents for specialized assistance, and optimizing tool use with MCP integration. It introduces Cloud Skills, plugins for team collaboration, and efficient tool utilization with parallel workflows. The concept of non-interactive agents, guided autonomy, and steps for experiencing agent decoding are also highlighted.

Simon explains the necessity of a custom React Native DevTools plugin framework due to the limitations of existing tools like Flipper and the lack of plugin support in React Native DevTools. Szymon Chmal, React Native expert at Callstack, explains the constraints of the custom DevTools framework plugin and the unique characteristics of React Native DevTools. The implementation involves bundling code via npm & Metro, using Chrome DevTools protocol for communication, and customizing DevTools frontend and middleware with Rosenite. Further customization includes injecting middleware for UI, adding custom scripts for dynamic content, accessing DevTools UI API for creating custom panels, bridging communication between plugins, and exploring the Resonight network activity plugin for inspecting headers and responses.

Marco Ippolito discusses the complexities of configuring NodeJS features and the need for a centralized config file. He explains the challenges of managing multiple flags for different features and demonstrates how to enhance developer experience by using specific flags to address TypeScript integration and testing procedures. The text discusses the challenges of managing multiple configuration flags in NodeJS and introduces the concept of using node options as an alternative to passing numerous flags directly after the node command. Node options provide a solution for managing configuration flags in NodeJS, simplifying the command structure and enabling the use of .mfile for configuration settings. I sent a PR to introduce the experimental config file feature in Node.js, including two major flags: experimental default config file and experimental config file, allowing customization of configuration settings through JSON files with version-matched schemas for IDE support and auto-completion. V8 flags in Node.js provide customization options, with a priority hierarchy among CLI, Node options, and config files, excluding no-op flags. Node 25 introduces new namespaces for test configuration, watch settings, and permissions, simplifying the configuration process and enhancing developer experience. Node.js JSON configuration offers convenience with a built-in JSON parser and plans for more namespaces and explanatory text in the JSON schema to simplify configuration management.

Ken Wheeler discusses the evolving software landscape, emphasizing the shift towards higher efficiency and less typing in job roles. The evolution of coding practices from manual formatting to automated tools like Prettier is compared to advancements in construction tools for efficiency. The use of AI for work efficiency and financial benefits, alongside considerations about the future of software engineers in light of AI advancements, is highlighted. Adapting to industry shifts, embracing new technologies like React, and leveraging early AI adoption for career growth are key points. Transitioning to higher-level roles by combining domain knowledge with AI for decision-making and seizing new opportunities is emphasized.