『Señors at Scale』のカバーアート

Señors at Scale

Señors at Scale

著者： Dan Neciu
無料で聴く

このコンテンツについて

 Welcome to Señors at Scale, the podcast where seasoned engineers spill the secrets, successes, and facepalms of building and maintaining software at scale. Join host Neciu Dan as we sit down with Staff Engineers, Principal Engineers, and other senior technologists to dive deep into the hard-won lessons of distributed systems, technical leadership, and scaling products that refuse to stay small. From war stories in incident response to behind-the-scenes architecture decisions, each episode brings a mix of practical insights, hard truths, and a healthy dose of dev humor. If you’ve ever wrangDan Neciu
エピソード
  • State Management at Scale with Daishi Kato (Author of Zustand)

    State Management at Scale with Daishi Kato (Author of Zustand)
    2025/12/14
    In this episode of Seniors at Scale, host Dan Neciu dives deep into the world of state management with Daishi Kato, the prolific open-source author and maintainer behind three of the most widely used libraries in modern React: Zustand, Jotai, and Valtio. Daishi also shares insights into his new project, Waku, a framework built around React Server Components.Daishi has spent nearly a decade building modern open-source tools that expertly balance simplicity with scalability. He shares how the announcement of React Hooks got him excited and led him to pick global state as his field to explore, as it was "more like logic" and "off look and feel".We break down the core philosophies and technical trade-offs between his state management trifecta:Zustand (Zastan): Described as a single global store or global variable. It is minimal, and its philosophical difference from Redux is that it doesn't use reducers.Jotai (Jyotai): Defined as a set of atom definitions, structured more like functions than a single global store. Daishi explains how the concept evolved from a need to avoid JavaScript proxies and selectors for better rendering optimization.Valtio (Valtio): This library is fundamentally based on just using JavaScript objects. It re-introduces proxy-based reactivity because Daishi realized that proxies were now "recognized" and acceptable in the community. We discuss its hook-based API, which differentiates it from MobX's observer pattern.The conversation then moves to the future of React development with Waku, which Daishi started as an experiment to learn how state management interacts with React Server Components. He explains Waku is suited for small-to-medium-sized web applications and static sites and discusses his vision for it to coexist with, rather than beat, Next.js.What makes Zustand, Jotai, and Valtio different: Global Store vs. Atom Definitions vs. JavaScript Objects.The philosophical difference between Zustand and Redux: Redux is reducers, Zustand is not.How Jotai's atom concept evolved and its goal of render optimization without selectors.Why Valtio embraced proxies and how its hook-based API differs from MobX.The origin story of Waku as an experiment with React Server Components.How React 18's useSyncExternalStore made Zustand even smaller.The challenge of maintaining four popular open-source libraries, with Waku being the current focus.Daishi’s strategy for rejecting feature requests for minimal libraries like Zustand: "We reject everything".Why Daishi prefers a competitive community over a built-in React state manager.Which of his libraries (Jotai) is best suited for use within Waku, as it is an abstraction of state that works on both client and server.If you're managing global state in React, interested in the internals of popular open-source tools, or curious about the future with React Server Components, this episode is a must-listen.Follow & Subscribe:📸 Instagram: https://www.instagram.com/senorsatscale/📸 Instagram: https://www.instagram.com/neciudev🎙 Podcast URL: https://neciudan.dev/senors-at-scale📬 Newsletter: https://neciudan.dev/subscribe💼 LinkedIn: https://www.linkedin.com/in/neciudan💼 LinkedIn: https://www.linkedin.com/company/se%C3%B1ors-scale/Additional Resources🌐 Daishi's Libraries: https://github.com/pmndrs🌐 Waku: https://github.com/dai-shi/waku🌐 SICP Book: Structure and Interpretation of Computer Programs#react #zustand #jotai #valtio #waku #statemanagement #javascript #opensource #softwareengineering #frontend #webdevelopment #señorsatscaleDon’t forget to like, comment, and subscribe for more engineering stories from the front lines.
    続きを読む 一部表示
    35 分
  • Domain Driven Design at Scale with Vlad Khononov (O'Reilly and Pearson Author)

    Domain Driven Design at Scale with Vlad Khononov (O'Reilly and Pearson Author)
    2025/12/13

    In this episode of Señors @ Scale, Dan sits down with Vlad Kononov, software architect, keynote speaker, and author of Learning Domain-Driven Design and Balancing Coupling in Software Design.

    Vlad has spent more than twenty years helping teams untangle legacy systems, rebuild failing architectures, and bring clarity to messy business domains. His work spans greenfield systems, enterprise refactors, and the ambiguous environments where most real software actually lives.

    This conversation cuts through the hype around DDD and microservices, focusing on the mechanics of bounded contexts, coupling, business alignment, and architectural evolution. We talk about why ubiquitous language reduces project failure, how bounded contexts emerge from social structures rather than diagrams, why most teams misuse aggregates, and how to spot “pain signatures” inside a system and trace them back to unclear domain boundaries. Vlad explains how subdomains evolve over time, how good designs quietly become counterproductive, and how accidental complexity appears at every layer of a system.

    We also dig into the real model behind coupling—strength, distance, and volatility—and how teams can use it to design systems that stay adaptable under pressure. Vlad breaks down why many microservice rewrites fail, when DDD actually makes sense, and why refactoring should start with understanding the business rather than carving out services at random.

    The episode ends with a discussion about AI and architecture, and how LLMs make domain-driven design more important rather than less. Vlad explains why clear domain vocabulary and modular boundaries help both engineers and AI reason about a system without being overwhelmed by complexity.

    If you’re building complex systems, leading platform or architecture teams, or struggling with a legacy codebase that keeps pushing back, this episode offers a practical, experience-driven guide to designing systems that scale with the business.

    Chapters

    00:00 Intro and Vlad’s Background
    01:42 Why DDD Was Written and Who It Was For
    04:02 When Aggregates Finally Made Sense
    05:42 Ubiquitous Language as the Core of DDD
    07:31 Why Software Projects Fail
    08:52 The Biggest Misconception About DDD
    10:13 Common Anti-Patterns in Domain Design
    12:12 Greenfield vs Brownfield DDD
    14:03 How to Begin Refactoring a Monolith
    15:25 Mapping Subdomains: Core, Supporting, Generic
    19:25 When Companies Do DDD Without Knowing
    20:39 When DDD Fails and Lessons Learned
    22:41 Why Defining Boundaries Is Hard
    25:56 Accidental Complexity in Large Systems
    27:32 Microservices, Myths, and Pain
    30:29 What Coupling Really Means
    33:17 Strength, Distance, and Volatility
    39:07 How Vlad Documents Architecture
    41:37 Event Storming as the Source of Truth
    44:01 How AI Changes System Design
    48:28 How to Enforce Ubiquitous Language
    51:00 Book Recommendations
    53:33 Closing Thoughts

    Follow and Subscribe:
    Instagram: https://www.instagram.com/senorsatscale/
    Instagram: https://www.instagram.com/neciudev
    Podcast: https://neciudan.dev/senors-at-scale
    Newsletter: https://neciudan.dev/subscribe
    LinkedIn: https://www.linkedin.com/in/neciudan
    LinkedIn: https://www.linkedin.com/company/se%C3%B1ors-scale/
    続きを読む 一部表示
    57 分
  • Modern CSS at Scale with Bramus (Chrome Developer Relations Engineer ,CSS and Web UI, at Google)

    Modern CSS at Scale with Bramus (Chrome Developer Relations Engineer ,CSS and Web UI, at Google)
    2025/11/23

    In this episode of Señors @ Scale, Dan sits down with Bramus Van Damme, Chrome Developer Relations Engineer at Google, and one of the driving forces behind View Transitions, Scroll-Driven Animations, Anchor Positioning, and CSS Custom Functions.Bramus brings a rare perspective from inside the browser engine itself. From helping shape CSS specs at the standards level to building the demos and tooling that developers rely on every day, he has a front-row seat to how modern UI engineering is evolving.We go deep into how the new CSS works in practice — beyond the marketing, straight into the mechanics of performance, rendering, and real-world API design.We break down how these capabilities actually work:How View Transitions calculate DOM deltas and morph shared elements across pages,How Scroll-Driven Animations run on the compositor instead of the main thread,How Anchor Positioning finally fixes popovers, tooltips, and dropdowns without JavaScript,and how CSS Custom Functions and Mixins push the language closer to a full programming environment.Bramus also explains the browser-internals most teams never see — interop, working with the CSS Working Group, and the engineering cost behind features that take 5 to 10 years to land across engines.The conversation goes beyond features into the realities of framework timing, React’s virtual DOM, when animations fall back to the main thread, and why modern CSS is becoming the foundation for UI systems at scale.If you’re building modern frontends, maintaining a design system, or leading platform engineering for UI, this episode is a masterclass in what the next generation of the web actually looks like.Chapters00:00 The Journey into Web Development01:02 Best Practices for View Transitions07:46 What Chrome DevRel Actually Does10:33 How Browser Features Get Prioritized13:38 Why Styling Forms Has Been Broken for Years17:18 Inside View Transitions and Cross-Document Animations22:11 Motion, Accessibility, and Reducing Overuse23:44 Integrating Browser Features with React, Vue, and Frameworks27:46 The Popover API and Pattern-Driven Standards30:48 How React and Chrome Collaborated on View Transitions31:46 The State of Scroll-Driven Animations34:25 Triggered Animations and What’s Coming Next35:50 Why JS Scroll Handlers Cause Jank37:17 GPU-Accelerated vs Main-Thread Animations40:10 The Coolest Demo: Scroll-Driven View Transitions44:24 Anchor Positioning and De-JSifying UI Patterns48:23 Developer Feedback, Interop, and Spec Evolution51:19 Custom Functions and the Future of CSS as a Language54:58 Mixins, Preprocessors, and Platform Evolution56:43 Books, Blogs, and Where Bramus Learns58:11 Closing Thoughts and Call for FeedbackFollow & Subscribe:📸 Instagram: https://www.instagram.com/senorsatscale/📸 Instagram: https://www.instagram.com/neciudev🎙 Podcast URL: https://neciudan.dev/senors-at-scale📬 Newsletter: https://neciudan.dev/subscribe💼 LinkedIn: https://www.linkedin.com/in/neciudan💼 LinkedIn: https://www.linkedin.com/company/se%C3%B1ors-scale/Additional Resources🌐 Bramus’ Blog: https://www.bram.us🌐 View Transitions Demos: https://view-transitions.chrome.dev🌐 Scroll-Driven Animations Course: https://scroll-driven-animations.style/🌐 Anchor-Tool by Una: https://anchor-tool.com#css #webdevelopment #frontend #javascript #chrome #softwareengineering #uiux #devtools #animations #react #performance #softwarearchitecture #señorsatscaleDon’t forget to like, comment, and subscribe for more engineering stories from the front lines.
    続きを読む 一部表示
    54 分
まだレビューはありません