Agentic development feels like magic to some teams and overhyped to others. Harnesses like Claude Code or Codex have been built around the local loop, the way things have always been done: a single developer changing code before opening a PR. Inside real organizations, agents hit walls: re...

Today's discussion covers challenges posed by AI models becoming more adept at deception, hidden AI thought processes, addressing coding agent security risks, the future of agent deployment and security, real-time monitoring and security policies, developer experience and automated systems, model behavior analysis and agency projection, product offering and developer risk reduction, futuristic concepts and developer risk management, data storage and risk severity management, deception in model behavior and user security, policy transparency and model adaptation, model failure monitoring and safety considerations.

Frontend and backend are often treated as opposite worlds, each with its own tools, constraints, and claims about which side is harder. But are they really so different?Modern frontend applications increasingly resemble distributed systems. Multiple tabs drift out of sync. Shared caches re...

What if your React app could understand users without sending their data anywhere?Modern browsers can now run meaningful machine learning locally. This talk shows how to use in-browser ML to build React interfaces that personalize, adapt, and respond in real time, while staying fast, priva...

We built a product fully on TanStack Query and skipped adding a state management layer. It worked for a while, then it broke in ways we didn’t expect.This talk dives into how TanStack Query works, what we got wrong, and how to use it properly. From missing optimistic updates to confusing s...

Vladimir Novik discusses the evolution of AI systems in coding, highlighting the shift in job requirements and challenges faced in scaling systems. Challenges in swarm orchestration include reducing reliability due to compounding errors and structural challenges in transitioning to a swarm system. Orchestrator Coding focuses on system properties over tools for code evolution. Enforcing architectural decisions and mechanical enforcement are crucial for system reliability. Orchestration disciplines prioritize dispatch, isolation, and durable handoffs, emphasizing autonomous systems and event-triggered actions. Mastery of orchestrated workflows involves resilience, autonomy, and disciplined manual and automated workflows. Advanced workflow techniques stress exact commands, linear workflow skills, caution in commits, and iterative improvement strategies. Automation enhancement strategies aim to overcome cost and parallelism challenges. Coding transformation journey involves validating and evolving code with orchestration. Model orchestration layers and architecture comparisons highlight the importance of model evaluation and verification gates. Tool comparisons and orchestrator communication strategies improve system orchestration. Architecture enforcement mechanisms utilize multiple layers and tools for code analysis and infrastructure testing.

Talking about using heap dumps to find and fix Node.js memory and CPU problems. Starting with a horror story of server crashes and memory leaks in Node.js environment. Exploring why memory leaks occur in JavaScript and how garbage collection works in programming languages. Memory leaks can occur in garbage collected environments. Understanding how garbage collection works in JavaScript and general programming languages. Exploring the mark and sweep phases of garbage collection to identify and reclaim unreachable objects. The garbage collection process involves two phases: mark and sweep. Objects not reachable from roots are marked for removal. The issue arises when objects can still be reached, causing memory leaks like with unbound caches. Memory leaks can occur due to global references or unclosed hooks causing objects to remain in memory, leading to potential memory overflow. Memory usage fluctuates due to garbage collection cycles, which prevent memory leaks by releasing unused memory. A memory leak leads to increasing memory and CPU usage, potentially causing system unresponsiveness. Pinpointing memory leaks is challenging as they affect the entire application, often appearing in production environments. Heap and memory dumps help analyze memory issues, generated in multiple ways like DevTools and command line. Exploring memory usage through Node.js application launch, debug mode, and heap snapshot analysis in Chrome DevTools. Exploring memory snapshots and pinpointing memory leaks by creating diffs between snapshots to identify leaked objects and their references for easy fixes. Exploring different methods for generating memory snapshots, including CLI flags, experimental node flags, and API usage, to efficiently identify memory leaks and manage heap dumps in Node.js environments. Discussing security considerations, challenges in memory leak detection, utilizing heap dumps for resolution, and emphasizing the importance of data security and verification in fixing memory leaks.

We used to explain our bugs to rubber ducks. Now, the duck talks back, writes code, and occasionally lies to our faces.

LLMs are incredible tools. They can cure "blank screen syndrome," instantly write boilerplate, and explain weird legacy code. But treating them like senior engi...

Almost a decade ago, React’s rendering algorithm was rebuilt, and with that it brought about new tools, ideas, and ways of building UI. But those tools arrived incrementally and were adopted in isolation, often framed as “optimizations” rather than part of a unified model. So are they truly indep...