Avsnitt
-
What does it actually take to run one of the biggest newsletters in the React ecosystem, week after week, for over six years?
In this episode of Seรฑors at Scale, Dan Neciu sits down with Sebastian Lorber, creator of This Week in React, the newsletter read by over 45,000 developers every week, and a core maintainer of Docusaurus at Meta. Sebastian has worked with React since late 2013, spent years as an independent consultant, and slowly turned a side project into his full indie hacker income.
Sebastian pulls back the curtain on the entire operation: how a French newsletter aimed at landing consulting gigs became an English curation powerhouse, the exhaustive weekly workflow across 2,000 X profiles and 500+ RSS feeds, and the Gmail size limit that quietly shapes every issue. We get into the unglamorous economics too, why French sponsors couldn't make it sustainable, how he prices and manages four ad slots a week, and why click counts are far more misleading than most sponsors think.
The conversation also covers the human side of curation: walking back mistakes with link proxies, staying friends with maintainers while breaking their unannounced work, the slow decline of social reach, and why he checks React feature flags before telling anyone a feature is "shipped." Plus a candid look at the recent TanStack compromise, trusted publishing, and why it gives a false sense of safety.
Key Topics:
- Starting a French newsletter to attract consulting clients
- Pivoting to English and converting an X audience
- The exhaustive weekly curation workflow (X lists, RSS, InnoReader)
- The Gmail truncation limit and how it shapes each issue
- Why French sponsors couldn't make it sustainable
- Managing four sponsors a week with Sponsy
- Why click metrics are misleading (Apple, corporate security scanners, UTM)
- Paid acquisition on X, Instagram, Reddit and what actually converts
- Treating subscribers like a stream, not a possession
- Checking React flags before announcing features
- React Server Components, the activity component, and Docusaurus
- The TanStack compromise, trusted publishing, and NPM security
GUEST LINKS
๐ผ LinkedIn: https://www.linkedin.com/in/sebastienlorber/
๐ฆ X: https://x.com/sebastienlorber
๐ GitHub: https://github.com/slorber
๐ This Week in React: https://thisweekinreact.com/
FOLLOW & SUBSCRIBE
๐๏ธ Podcast: https://neciudan.dev/senors-at-scale
๐จ Newsletter: https://neciudan.dev/subscribe
๐ผ Show LinkedIn: https://www.linkedin.com/company/senors-scale/
๐ธ Instagram: https://www.instagram.com/senorsatscale/
๐ค My LinkedIn: https://www.linkedin.com/in/neciudan
๐ธ My Instagram: https://www.instagram.com/neciudev
ADDITIONAL RESOURCES
This Week in React: https://thisweekinreact.com/
Docusaurus: https://docusaurus.io/
Sponsy: https://getsponsy.com/
#ThisWeekInReact #Newsletter #ReactJS #Docusaurus #OpenSource #IndieHacker #ContentCuration #SoftwareEngineering #ReactServerComponents #NPMSecurity
๐ฌ Do you still read tech newsletters, or has AI and social changed how you keep up with the ecosystem? Let me know in the comments.
-
Poly repos were good when we needed separation. But in the age of AI, do we still need it? Santosh Yadav doesn't think so.
In this episode of Seรฑors at Scale, I sit down with Santosh Yadav, Principal Developer Advocate at CodeRabbit, Google Developer Expert for Angular, GitHub Star, Nx Champion, and Microsoft MVP. Santosh has spent years deep in the monorepo world, including leading the move to Module Federation and driving Nx adoption across 30+ teams during his time as a staff engineer at Celonis.
We get into why monorepos are quietly becoming an AI superpower, how context changes everything when AI tools can read your dependency graph, and what it actually takes to migrate 20+ apps off polyrepos. Santosh also pulls back the curtain on CodeRabbit: how they handle context engineering for code review, why they run evals against 40+ models, their AI slop detector for open source, and how the team reacted when the big labs shipped their own code reviewers.
Key Topics:
- Becoming a GDE, GitHub Star, and Nx Champion (and what each actually gives you)
- Migrating 20+ apps to Module Federation at Celonis
- Monorepo vs Polyrepo in the age of AI
- Why AI tools thrive on monorepo context
- What Nx really is and when you need it
- Inside CodeRabbit: context engineering, model evals, and the AI slop detector
- Sponsoring open source with $1M+ in commitments
- How startups survive when the big labs ship competing features
GUEST LINKS
๐ผ LinkedIn: https://www.linkedin.com/in/santoshyadavdev/
๐ฆ X: https://x.com/SantoshYadavDev
๐ GitHub: https://github.com/santoshyadavdev
๐ Website: https://www.santoshyadav.dev/
FOLLOW & SUBSCRIBE
๐๏ธ Podcast: https://neciudan.dev/senors-at-scale
๐จ Newsletter: https://neciudan.dev/subscribe
๐ผ Show LinkedIn: https://www.linkedin.com/company/senors-scale/
๐ธ Instagram: https://www.instagram.com/senorsatscale/
๐ค My LinkedIn: https://www.linkedin.com/in/neciudan
๐ธ My Instagram: https://www.instagram.com/neciudev
ADDITIONAL RESOURCES
CodeRabbit: https://www.coderabbit.ai/
Nx: https://nx.dev/
#Monorepo #Nx #ModuleFederation #AICodeReview #CodeRabbit #Angular #DeveloperExperience #OpenSource #SoftwareEngineering #StaffEngineer
What's your take, are monorepos the right move in the age of AI, or is polyrepo still worth defending? ๐ฌ
-
Saknas det avsnitt?
-
What do you do when React Router v5 is blocking your React 18 upgrade, your frontend spans 25 repos, and you have 5 different micro frontend strategies running in the same app?
In this episode of Seรฑors at Scale, Dan Neciu sits down with Nicolas Beaussart-Hatchuel, Staff Engineer at PayFit and maintainer of TanStack Router. Nicolas shares the full story of migrating a 1.5 million-line codebase from React Router v5 to TanStack Router using the strangler pattern, without big-bang migrations and without stopping 18 engineers from shipping 15-20 PRs a day.
We also dive into the origin story of TanStack Router, why PayFit killed micro frontends entirely and moved back to a single monorepo, how building the whole app at once saved 25MB of JavaScript, and why his MCP experiments performed worse than simply letting AI agents read the code. Plus: what it really takes to go from senior to staff engineer.
Key Topics:
- How Nicolas got into coding and his first iframe-based micro frontend migration
- The origin story of TanStack Router and URL-as-state
- Migrating 1.5M lines from React Router v5 to TanStack Router
- The strangler pattern applied to frontend migrations
- Faking React Router providers to sync two routers on one URL
- Consolidating 25 repos into one monorepo
- Secret dependencies, Yarn v1 pain, and standardizing on Vite
- Why dropping per-library builds saved 25MB of JavaScript
- TypeScript Go in editors and its RAM cost
- MCP servers vs agents reading code directly
- Internal DevRel: winning engineers over with social proof
- Going from senior to staff: system design and finding problems worth solving
- What's next: TanStack Start v1 and parallel routes
Connect with Nicolas:
๐ผ LinkedIn: https://www.linkedin.com/in/beaussan/
๐ฆ X: https://x.com/beaussan
๐ GitHub: https://github.com/beaussan
๐ Website: https://beaussan.io
FOLLOW & SUBSCRIBE:
๐๏ธ Podcast: https://neciudan.dev/senors-at-scale
๐ฌ Newsletter: https://neciudan.dev/subscribe
๐ผ Dan's LinkedIn: https://www.linkedin.com/in/neciudan
๐ผ Show LinkedIn: https://www.linkedin.com/company/senors-scale/
๐ธ Instagram: https://www.instagram.com/senorsatscale/
๐ธ Dan's Instagram: https://www.instagram.com/neciudev
ADDITIONAL RESOURCES:
- TanStack Router: https://tanstack.com/router
- Engineering Management for the Rest of Us by Sarah Drasner
- Scaling Fast by Swizec Teller
- Swizec's newsletter: https://swizec.com
#TanStackRouter #React #Monorepo #MicroFrontends #FrontendArchitecture #TypeScript #StaffEngineer #SenorsAtScale
๐ฌ Have you ever had to migrate a router in a live codebase? What pattern did you use? Drop it in the comments.
-
What happens when the person maintaining one of the most widely used libraries on the internet tells you AI is coming for debugging, too?
Mark Erikson is the maintainer of Redux, creator of Redux Toolkit, and a senior front-end engineer at Replay.io, where he works on a time-traveling debugger. He's been shipping software since 2008, from emulating legacy CPUs in old aircraft at Northrop Grumman to modernizing a Redux codebase used by millions of developers. And remarkably, Redux has always been a free-time project for him.
In this episode, Dan sits down with Mark to trace the full arc of Redux: how it started as a 2015 conference demo on time travel, how it conquered (and then over-saturated) the React ecosystem, and how Redux Toolkit and RTK Query reshaped the way people actually use it today. We also get into one of the most fascinating technical stories in the episode, how Mark got source maps into React's build pipeline and what happened next.
Then we look forward. Mark walks through how Replay records the entire browser, how Replay MCP gives AI agents the same time travel debugging tools a human would have, and a real example where an agent went from fumbling for 15 minutes to finding a root cause in under two.
Key Topics:
- The origin of Redux and how it killed off the other Flux libraries
- What Redux Toolkit solves and the persistent "boilerplate" myth
- RTK Query vs React Query design tradeoffs
- The listener middleware and a two-year API design journey
- Getting source maps into React's build pipeline
- How Replay records and replays the entire browser
- Replay MCP and AI agents that auto-investigate failing tests
GUEST LINKS
๐ผ https://www.linkedin.com/in/markerikson
๐ฆ https://twitter.com/acemarke
๐ https://github.com/markerikson
๐ https://blog.isquaredsoftware.com
๐ฆ https://bsky.app/profile/acemarke.dev
FOLLOW & SUBSCRIBE
Instagram: https://www.instagram.com/senorsatscale/
Dan's Instagram: https://www.instagram.com/neciudev
Podcast: https://neciudan.dev/senors-at-scale
Newsletter: https://neciudan.dev/subscribe
Dan's LinkedIn: https://www.linkedin.com/in/neciudan
Show LinkedIn: https://www.linkedin.com/company/senors-scale/
ADDITIONAL RESOURCES
Redux: https://redux.js.org
Redux Toolkit: https://redux-toolkit.js.org
Replay: https://replay.io
Mark's blog post on the listener middleware and source maps work: https://blog.isquaredsoftware.com
#Redux #ReactJS #JavaScript #StateManagement #WebDevelopment #FrontEnd #SoftwareEngineering #OpenSource #Debugging #ReduxToolkit
๐ฌ What's the one thing you used to think AI would never be able to do for you as an engineer?
-
What does it actually feel like to maintain a library used by millions of developers every day?
In this episode of Seniors at Scale, Dan sits down with Dominik Dorfmeister, better known as TkDodo, the creator and maintainer of TanStack Query and a software engineer at Sentry. Dominik has spent over a decade building frontend tooling and has become one of the most trusted voices in the React and TypeScript ecosystem.
Dominik shares how he got into open source during the pandemic lockdowns, simply by answering questions in Discord, and how that habit grew into maintaining one of React's most widely adopted libraries. He talks candidly about the breaking change that went wrong, why major versions are "the pain of his existence," and what he has learned about shipping changes to a community that only shows up with feedback after release.
The conversation also digs into his work at Sentry, where he used Knip to remove 28,000 lines of dead code, and his team's work building a new design system within a 10-year-old, million-line codebase.
Key Topics:
- Getting into open source by answering community questions
- Becoming the maintainer of TanStack Query
- Tracked queries and the first big performance feature
- Why major version releases are so painful
- The version 4 to 5 breaking change that went wrong
- Epoch versioning as an alternative to semver
- Using Knip to find and remove dead code
- Building a design system in a large, legacy codebase
- What is planned for TanStack Query version 6
Guest: Dominik Dorfmeister (TkDodo)
๐ Blog: https://tkdodo.eu/blog
๐ฆ BluSky: https://bsky.app/profile/tkdodo.eu
๐ GitHub: https://github.com/TkDodo
FOLLOW & SUBSCRIBE
๐ผ LinkedIn: https://www.linkedin.com/company/senors-scale/
๐ Podcast: https://neciudan.dev/senors-at-scale
๐จ Newsletter: https://neciudan.dev/subscribe
๐ธ Instagram: https://www.instagram.com/senorsatscale/
Connect with Dan:
๐ผ LinkedIn: https://www.linkedin.com/in/neciudan
๐ธ Instagram: https://www.instagram.com/neciudev
ADDITIONAL RESOURCES
TanStack Query: https://tanstack.com/query
Knip: https://knip.dev
Sentry: https://sentry.io
TkDodo's blog: https://tkdodo.eu/blog
#ReactJS #TanStackQuery #OpenSource #FrontendDevelopment #SoftwareEngineering #WebDevelopment #TypeScript #Sentry
๐ฌ What is your take: should libraries do fewer, bigger major versions, or more frequent, smaller ones? Let us know in the comments.
-
What happens to "edge cases" when your product serves 250 million people every month?
In this episode of Seรฑors at Scale, I'm joined by Den Odell, Staff Software Engineer at Canva and author of "Performance Engineering in Practice" (Manning, 2026). Den works on Canva's Pro Design group, building inside one of the largest React/TypeScript codebases on the planet, serving 250M+ monthly users across 190+ countries.
Before Canva, Den spent 9 years at Volvo Cars architecting their Offer Selector and Car Configurator (powering vehicle purchases across 70+ markets), and 13 years at AKQA leading global frontend engineering for Nike, MINI, and Nokia. He's authored three books, the latest of which introduces the Fast by Default framework, a methodology for treating performance as a design decision from day one rather than a panic fix at the end.
We get into how Canva ships safely at a planetary scale (feature flags, dogfooding, geofenced rollouts, test parties), the protobuf-based RPC layer powering their frontend/backend communication, async-first culture across global timezones, and why most teams are stuck in what Den calls the Performance Decay Cycle.
Key Topics:
Why bugs scale with your user base (and what to do about it)Canva's release pipeline: staff โ beta โ geofenced regions โ worldTest parties, dogfooding, and catching weirdness before users doProtogen, CDF, and how Canva moves data between frontend and backendOperational transforms for real-time collaborationThe Performance Decay Cycle and why "performance sprints" are brokenFast by Default: making speed everyone's responsibility, not just engineeringPerceived performance, AI loading states, and the Pac-Man tape loader lessonAsync work culture when "the sun never sets on the Canva Empire"Building for crazy big goals (what does Canva look like at 1 billion users?)GUEST SOCIALS๐ผ LinkedIn: https://www.linkedin.com/in/denodell๐ฆ X/Twitter: https://x.com/denodell๐ GitHub: https://github.com/denodell๐ Website: https://denodell.com
FOLLOW & SUBSCRIBE๐ Podcast: https://neciudan.dev/senors-at-scale๐ง Newsletter: https://neciudan.dev/subscribe๐ผ Show LinkedIn: https://www.linkedin.com/company/senors-scale/๐ธ Instagram: https://www.instagram.com/senorsatscale/๐ผ Dan's LinkedIn: https://www.linkedin.com/in/neciudan๐ธ Dan's Instagram: https://www.instagram.com/neciudev
ADDITIONAL RESOURCES๐ Performance Engineering in Practice (Manning, 2026): https://www.manning.com/books/performance-engineering-in-practice๐ง Code listings on GitHub: https://github.com/denodell/performance-engineering-in-practiceโ๏ธ Den's blog: https://denodell.com/blog๐ The Product-Minded Engineer (Drew Hoskins, O'Reilly): mentioned in episode
#Frontend #Canva #FeatureFlags #Dogfooding #PerformanceEngineering #SoftwareEngineering #WebDevelopment #StaffEngineer #ReactJS #TypeScript #Podcast #SenorsAtScale
๐ฌ What's the worst "edge case turned major incident" you've shipped to production? Drop it in the comments.
-
What does engineering at Meta actually look like from the inside? Spoiler: almost nothing you know from outside applies.
In this episode, Dan sits down with Evyatar Alush, Software Engineer at Meta in Tel Aviv and the creator of EmojiPicker React (600K+ weekly downloads) and Vest. Evyatar's journey is one of the most unusual on the show: no degree, no high school diploma, learned JavaScript on Code Academy during military night shifts in a server room, then talked his way into Fiverr, scaled to Front End Platform Lead, and got recruited into Facebook in 2019.
We get into what it's actually like inside Meta's frontend infrastructure: Hack instead of PHP, Flow instead of TypeScript, Relay instead of Apollo, Sapling instead of Git, stacked diffs instead of pull requests, and a custom everything (testing frameworks, ORMs, dev servers, data centers). We also cover his open source philosophy, why he builds his own libraries instead of pulling dependencies, the supply chain risks of modern npm, and how AI-assisted code is reshaping open source maintainer work.
Key Topics:
- Learning to code on military night shifts with zero CS background
- Joining Fiverr with one year of experience and bluffing through the interview
- Building Fiverr's notification system, in-app inbox, and toast library
- Creating EmojiPicker React from a Fiverr internal tool
- The "Unmask" manifesto and starting Fiverr's frontend infrastructure team
- Designing the Front Ants team by faking the trappings of a real team
- Building micro-frontends that bridge a Ruby on Rails monolith and React
- Saying no to Facebook on the first email
- Interviewing at Meta in London (and the Dan Abramov interview)
- The Calibra/Diem crypto wallet team during COVID
- Hack vs PHP, Flow vs TypeScript, Relay vs Apollo, Sapling vs Git
- Stacked diffs and why ex-Meta engineers miss them
- Why "move fast and break things" is dead at Meta
- Code review, dev mod servers, and end-to-end testing at scale
- Open source maintenance in the AI era and Cursor-generated PRs
- Why he owns the "context" package on npm
GUEST: Evyatar Alush
๐ผ LinkedIn: https://www.linkedin.com/in/evyataralush-5b760866
๐ GitHub: https://github.com/ealush
๐ EmojiPicker React: https://github.com/ealush/emoji-picker-react
๐ Vest: https://vestjs.dev
FOLLOW & 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/senors-scale/
ADDITIONAL RESOURCES
- EmojiPicker React: https://www.npmjs.com/package/emoji-picker-react
- Vest (form validation): https://vestjs.dev
- Sapling (Meta's source control): https://sapling-scm.com
- The Hack language: https://hacklang.org
- Flow: https://flow.org
- Relay: https://relay.dev
- The Design of Everyday Things by Don Norman
- Never Split the Difference by Chris Voss
#Meta #Facebook #Frontend #ReactJS #HackLang #Flow #Relay #Sapling #StackedDiffs #OpenSource #EmojiPickerReact #Vest #SoftwareEngineering #SenorsAtScale
๐ฌ What's your take on Meta's "everything in-house" engineering culture? Would you rather work with familiar tools or relearn engineering from scratch for better internal infrastructure?
-
What does it actually take to build production React Native apps in 2026, and where does Expo fit in?
In this episode of Seรฑors at Scale, Dan sits down with Kadi Kraman, software developer at Expo, who has spent over six years in the React Native ecosystem, wearing every hat from IC to director. Kadi shares the story of how she went from writing C++ in a maths degree to becoming one of the early React Native engineers at Formidable, and eventually joining Expo to work on the platform itself.
We dig into what makes React Native genuinely competitive with native iOS and Android development today, why Expo Go is now just for prototyping, how EAS workflows and fingerprint-based repacks dramatically speed up CI, the real story on OTA updates (and where the legal gray area sits), and what's still missing from the ecosystem. Kadi also gives a rare look at the new Expo agent for vibe-coding mobile apps, the case for React Native brownfield, and her honest take on Lynx as competition.
Key Topics:
- Why React Native + Expo is faster than native Xcode/Android Studio workflows
- The mental shift from web to native (display points, gestures, pixel density)
- Expo Go vs development builds, and why the recommendation has changed
- EAS workflows, repack jobs, and project fingerprints
- React Native performance, list rendering, and the React Compiler
- OTA updates: when to use them, when not to, and what the stores actually allow
- Debugging strategies (expo-doctor, native logs, AI-assisted log analysis)
- Brownfield React Native and embedding RN screens into existing native apps
- Lynx, competition, and the future of cross-platform mobile
- Career advice on imposter syndrome, applying anyway, and finding talk topics
GUEST: Kadi Kraman, Software Developer at Expo
๐ผ LinkedIn: https://www.linkedin.com/in/kadikraman/
๐ฆ Twitter/X: https://x.com/kadikraman
๐ GitHub: https://github.com/kadikraman
๐ Website: https://kadikraman.com/
FOLLOW & SUBSCRIBE
๐๏ธ Podcast: https://neciudan.dev/senors-at-scale
๐ฉ Newsletter: https://neciudan.dev/subscribe
๐ผ LinkedIn (Show): https://www.linkedin.com/company/senors-scale/
๐ผ LinkedIn (Dan): https://www.linkedin.com/in/neciudan
๐ธ Instagram (Show): https://www.instagram.com/senorsatscale/
๐ธ Instagram (Dan): https://www.instagram.com/neciudev
ADDITIONAL RESOURCES
- Expo: https://expo.dev/
- Kadi's "From Web to Native with React" blog post: https://expo.dev/blog
- EAS Workflows: https://docs.expo.dev/eas-workflows/get-started/
- Expo Doctor: https://docs.expo.dev/more/expo-cli/#expo-doctor
- Expo Fetch (streaming support): https://docs.expo.dev/versions/latest/sdk/expo/
#ReactNative #Expo #MobileDevelopment #JavaScript #iOS #Android #EAS #ExpoRouter #SoftwareEngineering #SeรฑorsAtScale
๐ฌ What's your biggest pain point building React Native apps today, and have EAS workflows changed your CI setup?
-
Can you really run state-of-the-art machine learning models directly in the browser, with no server, no API calls, and full privacy by default?
In this episode, Nico Martin, Open Source Machine Learning Engineer at Hugging Face and Google Developer Expert in AI and Web Technologies, walks through how Transformers.js makes on-device AI a reality. Nico's journey is anything but conventional. He started as a ski and windsurf instructor, taught himself web development on the side, spent years as a freelancer (including five at a bank building e-banking front ends), and recently landed what he calls his dream job at Hugging Face.
We unpack what Hugging Face actually is (the GitHub for machine learning), how Transformers.js brings the Python Transformers API to the browser, and the real engineering challenges of running models on whatever hardware your users happen to have. Nico explains quantization, ONNX as the standard for portable model architectures, the role of tokenizers, how text becomes tensors, and why WebGPU matters for running larger models client-side.
We also dig into the bigger picture: privacy-preserving AI, the difference between open weights and truly open source models, agents and MCP, and what front-end developers should actually learn to stay relevant in an AI-first world.
Key Topics:
- What Hugging Face is and the role of the Hub, Transformers, and Diffusers
- Transformers.js: bringing Python Transformers API to JavaScript and the browser
- The biggest challenge of browser ML: running on unknown client hardware
- Quantization explained (Q4, 4-bit vs 16/32-bit) and how it compresses models
- ONNX and ONNX Runtime Web: the standard for portable model architectures
- Open weights vs open source models and why the distinction matters
- Tokenizers, token IDs, and why each model needs its own tokenizer
- From text to tensors: pre-processing, inference, and post-processing
- Text embeddings explained through a simple animal feature analogy
- WebGPU and what it unlocks for in-browser inference
- Agents, tool calling, MCP, and how context windows get consumed
- Advice for developers who want to break into AI and ML engineering
๐ FOLLOW NICO
๐ผ LinkedIn: https://www.linkedin.com/in/nicodotdev/
๐ฆ X/Twitter: https://twitter.com/nic_o_martin
๐ฆ Bluesky: https://bsky.app/profile/nico.dev
๐ GitHub: https://github.com/nico-martin
๐ Website: https://nico.dev
๐๏ธ 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/senors-scale/
๐ ADDITIONAL RESOURCES
- Transformers.js: https://huggingface.co/docs/transformers.js
- Hugging Face: https://huggingface.co
- ONNX: https://onnx.ai
- ONNX Runtime: https://onnxruntime.ai
- WebGPU: https://www.w3.org/TR/webgpu/
- Utopia for Realists by Rutger Bregman
#MachineLearning #AI #HuggingFace #TransformersJS #WebML #OnDeviceAI #WebGPU #ONNX #JavaScript #Frontend #WebDev #SenorsAtScale #OpenSource
๐ฌ Would you trust on-device AI over cloud-based models for sensitive data? Share your thoughts in the comments!
-
What does it actually take to scale a frontend from 15 people in a converted flat to a 1,800-person unicorn, and then migrate the whole thing to microfrontends without breaking anyone's week?
In this episode, Dan sits down with Giorgio Polvara, Staff Engineer at Perk (formerly TravelPerk) and the original creator of @testing-library/user-event (1M+ weekly npm downloads). Giorgio joined TravelPerk as employee #15, set up the frontend foundations that still power the product today, left to try engineering management at Toptal, realized he missed building, and came back as Staff.
They get into the microfrontend migration that replaced a monolithic React app with vertically-split single-page apps served at the infrastructure layer, the rebrand that changed the name, domain, logo, and colors simultaneously, and the philosophy that ties it all together: you're not building features, you're improving a system that happens to produce features.
Key Topics:
- Scaling a frontend team from 7 engineers to a full platform tribe
- Why 20% refactoring time is the wrong model
- Monolith to microfrontends: SingleSPA vs the vertical-split architecture they built
- Managing shared dependencies with pnpm, Syncpack, and Vite plugin packages
- Contract testing with Pact vs runtime schema validation with Zod
- Rebranding an entire product behind a feature flag, without leaking the design
- Why Giorgio tried engineering management and went back to IC
- Staff engineer advice: propose five solutions, expect one to land
๐ FOLLOW GIORGIO
๐ผ LinkedIn: https://www.linkedin.com/in/polvara
๐ GitHub: https://github.com/Gpx
๐ npm: https://www.npmjs.com/package/@testing-library/user-event
๐๏ธ 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/senors-scale/
๐ ADDITIONAL RESOURCES
- A Philosophy of Software Design by John Ousterhout
- Out of the Tar Pit (Moseley & Marks)
- No Silver Bullet (Fred Brooks)
- @testing-library/user-event: https://www.npmjs.com/package/@testing-library/user-event
- SingleSPA: https://single-spa.js.org
- Vite: https://vitejs.dev
- Pact (contract testing): https://pact.io
- Zod: https://zod.dev
#staffengineer #microfrontends #frontendarchitecture #perk #travelperk #reactjs #softwarearchitecture #engineeringleadership #devtools #softwaredesign #senorsatscale
๐ฌ How does your team handle the tension between shipping features and keeping the system healthy? Drop a comment ๐
-
How do you deploy federated front ends to the edge in 150 milliseconds? In this episode, Zack Chapple, CEO and Co-founder of Zephyr Cloud, and Nestor Lopez, Platform Engineer at Zephyr Cloud, break down everything developers need to know about micro frontends, module federation, and deploying at global scale without the infrastructure pain.
Zack's journey started at a consulting company working with enterprises like SAP to add module federation support to Angular, which eventually revealed all the pain points of scaling federated architectures. That led to Medusa, then to Zephyr Cloud, the platform he describes as "Kubernetes for the front end." Nestor's path started eight years ago with Sencha.js and iframes, long before module federation existed, and brought him to Zephyr through open source contributions to TRPC and other projects.
We cover why module federation is "Docker for the front end," how Zephyr deploys with one line of code and no CI/CD pipeline, their reverse tree shaking technique that recomposes federated bundles into a monolith at the edge, how Nestor deployed 5,200+ micro frontends as a single video, their federated MCP server for enterprise AI orchestration, and a TC39 proposal to fix ESM module unloading in V8. We also talk about pricing, open source contributions, and what it's really like to build a startup with four kids.
Whether you're an enterprise team trying to ship frontend independently across dozens of teams, or a solo developer who just wants to deploy without setting up a CI/CD pipeline, this conversation covers the full spectrum.
Key Topics:
- Micro frontends explained through the microservices and Kubernetes analogy
- Module federation as "Docker for the front end" and Zephyr as the orchestration layer
- End-to-end walkthrough: from bundler to global edge deploy in ~150ms
- No repo required, Zephyr hooks into any bundler and deploys on build
- Reverse tree shaking: monolith performance with micro frontend dev experience
- The Chrome extension for hot-swapping MFEs in any environment
- Federated MCP servers built on module federation for enterprise AI
- TC39 proposal to fix ESM module unloading and enable live HMR on Node.js
- Bring your own cloud: Cloudflare, AWS, Fastly
- Pricing: free for solo, $19/seat for teams, org-wide for enterprise
- Mobile support through Metro and desktop through Tauri
- Open source contributions and financially supporting projects like RSPack, SWC, and Tailwind
๐ FOLLOW ZACK
๐ผ LinkedIn: https://www.linkedin.com/in/zackarychapple/
๐ฆ X/Twitter: https://x.com/Zackary_Chapple
๐ GitHub: https://github.com/zackarychapple
๐ FOLLOW NESTOR
๐ผ LinkedIn: https://www.linkedin.com/in/nstlopez/
๐ฆ X/Twitter: https://x.com/nstlopez
๐ Blog: https://nstlopez.com
๐๏ธ 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/senors-scale/
๐ ADDITIONAL RESOURCES
- Zephyr Cloud: https://zephyr-cloud.io
- Module Federation: https://module-federation.io
- RSPack: https://rspack.dev
- Hono: https://hono.dev
- shadcn/ui: https://ui.shadcn.com
#MicroFrontends #ModuleFederation #ZephyrCloud #Frontend #WebDev #PlatformEngineering #DevEx #EdgeComputing #Kubernetes #SenorsAtScale #OpenSource #Startup
๐ฌ What's the most painful deployment workflow you've ever had to deal with? Share your stories in the comments!
-
William Morgan is the CEO of Buoyant and the creator of Linkerd, the world's first service mesh and a CNCF graduated project powering production Kubernetes infrastructure at thousands of companies. Before founding Buoyant, William spent nearly four years at Twitter as a software engineer and engineering manager, where he shipped core platform features like the Twitter photo service and embed timelines โ and watched the legendary monolith-to-microservices transformation unfold firsthand.
In this episode, we cover what it was like engineering at Twitter during the fail whale era, how decomposing a monolith introduces entirely new networking challenges, why William invented the term "service mesh," and how Linkerd gives platform teams reliability, security, and observability without developers having to think about it.
Whether you're a platform engineer running Kubernetes in production, an SRE trying to make sense of service-to-service communication, or a developer curious about what infrastructure teams actually do โ this conversation is packed with hard-won lessons from a decade of building critical open source infrastructure.
๐ธ Key Topics:
- Engineering at Twitter in 2010: the Rails monolith, Scala rewrite, and microservices transformation
- How replacing function calls with network calls changes everything
- What a service mesh is and why the term had to be invented
- Control plane vs data plane architecture
- Why Linkerd rewrote its proxy from Scala/JVM to Rust
- Latency-aware load balancing, mTLS, and protocol detection
- Multi-cluster communication and mesh expansion to VMs
- Common service mesh implementation mistakes
- Linkerd vs Istio: William's honest take
- Open source sustainability and enterprise monetization
- The enterprise sales journey from engineer to CEO
- Book recommendations: Hyperion, Gideon the Ninth, The Book of the New Sun
๐ FOLLOW WILLIAM
๐ผ LinkedIn: https://www.linkedin.com/in/wmorgan/
๐ฆ X/Twitter: https://x.com/wm
๐ Buoyant: https://buoyant.io
๐๏ธ 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รฑors-scale/
๐ ADDITIONAL RESOURCES
- Linkerd: https://linkerd.io
- Buoyant: https://buoyant.io
- Linkerd Getting Started: https://docs.buoyant.io
- Linkerd GitHub (Proxy): https://github.com/linkerd/linkerd2-proxy
- Hyperion by Dan Simmons
- Gideon the Ninth by Tamsyn Muir
- The Book of the New Sun by Gene Wolfe
- Simon Willison's Blog (AI/LLMs): https://simonwillison.net
#Linkerd #ServiceMesh #Kubernetes #Rust #CloudNative #Buoyant #CNCF #Microservices #Infrastructure #PlatformEngineering #SoftwareEngineering #SenorsAtScale
๐ฌ What's the most complex networking issue you've debugged in a microservices environment? Share your war stories in the comments!
-
You can never build anything faster than your slowest database query. In this episode, Tyler Benfield, Staff Software Engineer at Prisma, breaks down everything developers need to know about database performance, from why your queries are slow to how Prisma scales Postgres to handle billions of requests on bare metal infrastructure.
Tyler's path into databases started at Penske Racing, writing trackside software for NASCAR pit stops, and eventually led him deep into query optimization, connection pooling, and building Prisma Postgres from the ground up. We cover the most common ORM anti-patterns, why indexes are the single biggest performance lever most developers ignore, how Prisma Accelerate turns database connections into HTTP calls, and why Tyler thinks the SQL query language itself is fundamentally broken for modern web apps.
Whether you're a frontend developer afraid to touch the database or a backend engineer scaling past your first million users, this conversation is packed with practical, immediately actionable advice.
๐ธ Key Topics:
- ORMs vs raw SQL vs query builders and when to use each
- The most common Prisma anti-patterns that tank your app performance
- How database indexes actually work (the address book analogy)
- Connection pooling, serverless runtimes, and the problem Prisma Accelerate solves
- Scaling Postgres on bare metal with memory snapshots and scale-to-zero
- Per-query pricing and why Prisma charges differently than other providers
- NoSQL vs SQL and when Postgres can handle both
- Why SQL is a bad query language for nested relational data
- The future of AI agents and databases, MCP servers, and ephemeral environments
๐ FOLLOW TYLER
๐ผ LinkedIn: https://www.linkedin.com/in/tylerbenfield/
๐ฆ X/Twitter: https://x.com/rtbenfield
๐ฆ Bluesky: https://bsky.app/profile/rtbenfield.dev
๐ Website: https://tylerbenfield.me
๐๏ธ 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รฑors-scale/
๐ ADDITIONAL RESOURCES
- Prisma ORM: https://www.prisma.io
- Prisma Postgres: https://www.prisma.io/postgres
- The Design of Everyday Things by Don Norman
- The Design of Future Things by Don Norman
- Designing Data-Intensive Applications by Martin Kleppmann
- Aaron Francis (database education): https://aaronfrancis.com
#Prisma #Postgres #DatabasePerformance #ORM #TypeScript #ServerlessDatabase #ConnectionPooling #SQLOptimization #WebDevelopment #SoftwareEngineering #FullStack #DatabaseIndexes #SenorsAtScale
๐ฌ What's the worst database performance issue you've ever debugged? Share your war stories in the comments!
-
TanStack Form gets over a million downloads per week. Corbin Crutchley is the person behind it. But this conversation goes way beyond forms and frameworks.
Corbin started coding professionally at 16, worked minimum wage at a charter school, taught himself Angular through sheer persistence, and eventually became a GitHub Star, Microsoft MVP, author of The Framework Field Guide, and VP of Engineering at Immersive Homes. Along the way, he built one of the most beloved open source form libraries in the JavaScript ecosystem and founded Playful Programming, a nonprofit that teaches people how to code for free.
In this episode, we get into the real stuff: how he joined TanStack through a 30-minute conversation with Tanner Lindsley that turned into an invitation to lead a project, what it actually feels like to maintain a library that millions of projects depend on, why he almost quit open source after a wave of rude issues, and how he thinks about versioning as a social contract with your users. We also talk about framework agnostic architecture, why he wrote a free book that teaches React, Angular and Vue at the same time, the open source funding problem, and his transition from IC to VP of Engineering at Immersive Homes (which started with a game of Magic: The Gathering). He closes with something deeply personal about mental health in tech that I think everyone needs to hear.
๐ RESOURCES MENTIONED
- TanStack Form: https://tanstack.com/form
- TanStack: https://tanstack.com
- The Framework Field Guide: https://playfulprogramming.com/collections/framework-field-guide
- Playful Programming: https://playfulprogramming.com
- Diataxis Documentation Framework: https://diataxis.fr
- Will Larson's Books (An Elegant Puzzle, Staff Engineer): https://lethain.com
- Engineering Management for the Rest of Us by Sarah Drasner
- Shoe Dog by Phil Knight
๐ FOLLOW CORBIN
- GitHub: https://github.com/crutchcorn
- LinkedIn: https://www.linkedin.com/in/corbincrutchley
- Bluesky: https://bsky.app/profile/crutchcorn.dev
- Twitch: https://twitch.tv/crutchcorn
๐๏ธ FOLLOW & SUBSCRIBE
๐ธ Podcast Instagram: https://www.instagram.com/senorsatscale๐ธ Dan's Instagram: https://www.instagram.com/nicudan๐ฐ Newsletter: https://senorsatscale.substack.com๐ผ Dan's LinkedIn: https://www.linkedin.com/in/nicudan๐ Website: https://neciudan.dev
#SoftwareEngineering #OpenSource #TanStack #TanStackForm #JavaScript #TypeScript #ReactJS #Angular #Vue #FrameworkAgnostic #GitHubStar #VPofEngineering #EngineeringLeadership #TechLeadership #MentalHealthInTech #WebDevelopment #SenorsAtScale
-
What happens when one developer's tools account for 0.7% of all NPM downloads? In this episode, Andrey Sitnik, creator of PostCSS, Autoprefixer, and Browserlist, and lead engineer at Evil Martians, shares the full story behind the CSS tools that millions of developers depend on every day.
From writing PostCSS in CoffeeScript to architecting its event-based plugin system in version 8, Andrey walks us through the technical decisions, ecosystem politics, and open source philosophy that shaped modern CSS tooling. We also dig into why he intentionally designed Browserlist's query language to fight browser discrimination, how Tailwind's donation accidentally forced the PostCSS 8 release, and why he believes the tech industry's biggest problems aren't technical at all.
๐ธ Key Topics:
- The origin story of PostCSS and why Autoprefixer was the gateway
- Plugin architecture from day one: designing for ecosystem growth
- Managing painful major releases across a massive plugin ecosystem
- Why rewriting tools in Rust isn't always the performance win you think
- Browserlist's hidden philosophy: shaping developer behavior through language design
- The Tailwind donation that triggered the PostCSS 8 release
- Why the hardest problems in open source are political, not technical
- CSS tooling in the age of LLMs: complexity control over automation
- Social media, values, and what the tech industry lost in the 2010s
- Dark transhumanism: sci-fi book recommendations from a systems thinker
โฑ Chapters:
00:00 - Intro
00:53 - How Andrey started programming and his Wikipedia roots
02:59 - The origin of PostCSS and Autoprefixer
06:26 - Why PostCSS was built as a plugin system from day one
08:20 - The relationship between PostCSS and Sass/Less communities
11:04 - Managing the PostCSS 8 major release and migration strategy
14:57 - From CoffeeScript to ES modules: PostCSS's language journey
16:08 - Why rewriting in Rust isn't always the answer
19:15 - The hardest problems aren't technical
21:51 - Event-based plugin architecture deep dive
23:20 - What Andrey would do differently today
24:14 - Is PostCSS still needed? CSS tooling in the future
27:51 - Browserlist: fighting browser discrimination through design
31:41 - AI, open source, and the values crisis in tech
38:51 - The Open Claw controversy and open source experiments
40:18 - The social media reader Andrey wishes existed
44:24 - Book recommendations: dark transhumanism and beyond
๐ Resources & Links:
- Andrey Sitnik: https://evilmartians.com/martians/andrey-sitnik
- The history of PostCSS (article): https://evilmartians.com/chronicles/what-we-learned-from-creating-postcss
- PostCSS: https://postcss.org
- Browserlist: https://browsersl.ist
- CSSTree (faster JS-based PostCSS alternative): https://github.com/csstree/csstree
- CSSTree author's talk on how he built it: https://www.youtube.com/watch?v=itxpfoo1daM
- Lightning CSS (Rust-based PostCSS replacement): https://lightningcss.dev
- Slow Reader (Andrey's social media reader project): https://github.com/hplush/slowreader
- Evil Martians: https://evilmartians.com
๐ Dark Transhumanism Reading List:
1. "Permutation City" by Greg Egan
2. "Lena" by qntm (short horror story in wiki format): https://qntm.org/mmacevedo
3. "The Quantum Thief" by Arsรจne Lupin
4. "Blindsight" by Peter Watts
๐ Follow & Subscribe:
๐ธ Podcast Instagram: https://www.instagram.com/senorsatscale
๐ธ Dan's Instagram: https://www.instagram.com/nicudan
๐ฐ Newsletter: https://senorsatscale.substack.com
๐ผ Dan's LinkedIn: https://www.linkedin.com/in/nicudan
๐ Website: https://neciudan.dev
#SeniorsAtScale #PostCSS #Browserlist #Autoprefixer #OpenSource #CSSTooling #EvilMartians #WebDevelopment #FrontendEngineering #SoftwareEngineering #TechLeadership #PluginArchitecture #DeveloperTools
-
What does a robotics graduate, a Microsoft MVP, and a Vercel DX Engineer have in common? They're all Aurora Scharff, and she's on a mission to change how developers think about React.
In this episode, Aurora takes us through her unconventional path from studying Robotics and Intelligent Systems at the University of Oslo to becoming one of the most active voices in the React community. From her early days building Angular frontends at a fintech startup to leading a major public sector frontend rebuild with Next.js at Crayon Consulting, Aurora has seen it all. Now at Vercel, she's focused on developer experience, and as React Certification Lead at certificates.dev, she's shaping how the industry validates React skills.
We go deep on React Server Components, what they actually change about how you build apps, why the mental model shift trips up even experienced developers, and how Next.js App Router fits into the picture. Aurora also shares real stories from rebuilding legacy systems for the Norwegian government, her honest take on Vercel vs Azure deployments, and why she thinks certifications matter more than ever in an AI-driven world.
๐ธ Topics Covered:
- Transitioning from robotics and Angular to the React ecosystem
- React Server Components: how they simplify data fetching and improve performance
- The mental model shift developers need to make with async server components
- Next.js App Router vs Page Router and why the migration is worth it
- Deploying Next.js on Vercel vs Azure: trade-offs and gotchas
- Handling vulnerabilities and upgrades in production Next.js apps
- Rebuilding legacy public sector systems with modern web tech
- Creating the React certification at certificates.dev
- Common React mistakes: deriving state and other pitfalls
- New React features: view transitions, suspense, and what's coming next
- Public speaking tips and building a content creation workflow
- Becoming a Microsoft MVP and contributing to the developer community
๐ Chapters
00:00 Introduction to Aurora Scharff
01:56 Transition from Robotics to Web Development
03:22 Journey from Angular to React
06:40 Understanding React Server Components
09:23 Mental Model Shifts with Server Components
10:41 Exploring Next.js and Its Features
11:33 Deployment Strategies: Vercel vs Azure
14:43 Handling Vulnerabilities in Next.js
15:47 Next.js App Router vs Page Router
16:54 New Features in React Ecosystem
18:46 Rebuilding Legacy Systems
20:45 Testing Practices in Next.js
22:23 Creating React Certifications
29:07 The Importance of Certifications
29:52 Common Mistakes in React Development
31:36 Aurora's Speaking Journey
36:14 Content Creation Process for Talks
37:33 Balancing Work and Side Projects
40:23 Advice for Aspiring Speakers
42:24 Becoming a Microsoft MVP
43:47 Excitement in the React Ecosystem
44:59 Future Plans and Upcoming Projects
45:33 Recommended Movies and Closing Thoughts
๐ Connect with Aurora:
- LinkedIn: https://www.linkedin.com/in/aurorascharff-a86b88188
- Website: https://aurorascharff.no
๐๏ธ 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รฑors-scale/
#ReactJS #NextJS #ReactServerComponents #WebDevelopment #SoftwareEngineering #Vercel #DeveloperExperience #TechPodcast #SeniorsAtScale #JavaScript #FrontendDevelopment #Microsoft MVP #ReactCertification #AppRouter #TechLeadership
-
What does it actually take to be a developer advocate? And how do you measure the impact of developer relations when everyone seems to disagree on the metrics?
In this episode, Daniel Afonso, Senior Developer Advocate at PagerDuty, walks us through his journey from writing prank bash scripts as a 10-year-old in Portugal to becoming one of the most active voices in the European DevRel community. Daniel breaks down how developer relations sits at the intersection of engineering, marketing, sales, and product, and shares hard-won lessons on what makes DevRel programs succeed or fail.
We also go deep on developer experience, covering the three pillars every SDK and API team should optimize for: reducing cognitive load, fast feedback loops, and keeping developers in flow state. Plus, Daniel shares his take on on-call culture, why postmortems matter, and the books that shaped his career.
๐ธ Topics Covered:
Growing up drawn to tech and competing in national programming competitions in Portugal
Transitioning from backend (Java, C++, .NET) to frontend and falling in love with React
How blogging, learning in public, and meetups built the foundation for a DevRel career
Developer Relations explained: the Venn diagram of engineering, marketing, sales, and product
Measuring DevRel impact: from vanity metrics to Developer Relations Qualified Leads
Why DevRel programs fail: unreasonable expectations, pitch-fest conference talks, and missing business alignment
The three pillars of developer experience: cognitive load, fast feedback loops, and flow state
How React's JSX and Solid's signals represent great DX initiatives in practice
Staying technical as a developer advocate through side projects, code reviews, and community work
On-call culture: reducing alert fatigue, owning your services, and changing the "I hate on-call" mindset
Book recommendations: Thriving on Overload, How to Win Friends and Influence People, The Phoenix Project
Chapters:
00:00 Introduction to Developer Advocacy
01:15 Daniel's Journey into Programming
07:28 Transitioning to Front-End Development
12:49 The Path to Developer Relations
18:43 Understanding Developer Relations
22:53 Measuring the Impact of DevRel
26:45 Common Pitfalls in DevRel Programs
30:39 Marketing and Developer Relations Missteps
33:47 Avoiding Developer Pitfalls at Events
35:53 Staying Technical in Non-Technical Roles
40:06 Defining Great Developer Experience
46:56 The Importance of Documentation
52:41 On-Call Experiences and Incident Management
01:02:12 Book Recommendations and Personal Favorites
01:06:52 Wrap Up
๐ Follow & Subscribe:
YouTube: https://www.youtube.com/@neciudan
Spotify: https://open.spotify.com/show/senorsatscale
Apple Podcasts: https://podcasts.apple.com/podcast/senors-at-scale
LinkedIn: https://www.linkedin.com/in/neciudan
Newsletter: https://neciudan.dev
๐ Guest Links:
Twitter: https://twitter.com/danielafonso
LinkedIn: https://linkedin.com/in/danielafonso
PagerDuty: https://pagerduty.com/
๐ Resources Mentioned:
Thriving on Overload - https://www.amazon.com/Thriving-Overload-Strategies-Manage-Information/dp/XXXXXX
React Documentation - https://reactjs.org/docs/getting-started.html
Cloudflare Use Effect Postmortem - https://blog.cloudflare.com/postmortem-incident-XXXXXX
SolidJS - https://solidjs.com/
Frictionless by Abhinoda & Nicole Forsgreen
The Phoenix Project
How to Win Friends and Influence People by Dale Carnegie
#DevRel #DeveloperExperience #DeveloperAdvocacy #SoftwareEngineering #PagerDuty #OnCall #DX #TechPodcast #SeniorsAtScale #DeveloperRelations #OpenSource #TechLeadership
-
How do you build an engineering organization from zero to 700 professionals? What happens when your biggest leadership lesson comes from a broken leg and a Border Collie?
In this episode of Senors @ Scale, I sit down with Lucian Popovici, a force multiplier in tech leadership with 20+ years of experience scaling engineering organizations at Ericsson, Deutsche Bank, and Deloitte Digital. Lucian is the founder of Bridging Innovation, an enterprise strategy advisory and AI consultancy, and Bridging Gaps, a pro bono mentoring community of 80+ senior tech leaders that has delivered over 3,000 hours of free mentoring to 400+ professionals in Romania.
Lucian shares the raw, unfiltered story of his transition from Java developer to engineering director, including the panic attacks he didn't acknowledge, the "control freak" feedback that changed everything, and why he believes informal leadership matters more than titles. We go deep on how AI is reshaping team structures (from 10-person teams to 5), why junior developer roles are disappearing, why Romania's IT industry needs to shift from body leasing to product thinking, and his bold take that project managers should "die" as a role. Whether you're scaling your first team or building your hundredth, this conversation is packed with hard-won wisdom.
๐ธ KEY TOPICS DISCUSSED
- Scaling engineering organizations from scratch at Deutsche Bank, Deloitte Digital, and beyond
- The brutal transition from developer to leader and why most people aren't prepared
- Manager vs. leader: why less ego and more empathy changes everything
- Why flat organizations beat pyramid schemes of managers
- How AI is cutting team sizes in half and eliminating junior roles
- The Romanian IT industry's transformation from outsourcing to product and consultancy
- Why 85% more time is now spent on code reviews than writing code
- Fractional CIO/CTO roles and why SMBs desperately need them
- Building a pro bono mentoring community of 80+ senior leaders
- AI readiness: why most companies fail at AI implementation before they even start
- The startup ecosystem in Romania and why this is the best time for non-technical founders
- Why project managers should disappear (but product managers never will)
- The engineering mindset vs. role segregation in modern teams
- Adaptability and curiosity as the core leadership skills for 2030
โฑ๏ธ CHAPTERS
00:00 Introduction to Lucian Popovici
02:22 From Developer to Leader: The Brutal Transition
06:27 Manager vs. Leader: Ego, Empathy, and Flat Orgs
09:28 Scaling Organizations (Without a Playbook)
11:23 How AI Is Reshaping Team Structures
16:02 Is Romania's IT Industry Scaling Down?
24:40 The "Control Freak" Feedback That Changed Everything
29:37 How Bridging Gaps Started (The Border Collie Story)
36:30 From Corporate to Entrepreneur: Bridging Innovation
45:59 The Future of Engineering Roles and Leadership
๐ FOLLOW LUCIAN
๐ผ LinkedIn: https://www.linkedin.com/in/lucianpopovici/
๐ Bridging Innovation: https://bridging-innovation.com
๐ค Bridging Gaps: https://bridging-gaps.ro/
๐ Blog: https://lucianpopovici.com
๐๏ธ 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รฑors-scale/
๐ ADDITIONAL RESOURCES
- HowToWeb Conference: https://www.howtoweb.co
- Ascendis Training: https://www.ascendis.ro
#EngineeringLeadership #ScalingTeams #TechLeadership #AI #SoftwareEngineering #StartupRomania #EngineeringManagement #ProBonoMentoring #FractionalCTO #AgileLeadership #DevOps #TeamScaling #SenorsAtScale
๐ฌ Have you made the jump from developer to leader? What was your biggest challenge? Share in the comments!
-
What makes a great tech lead? It's not just technical chopsโit's the soft skills that scale your impact beyond your own keyboard.
In this episode, I sit down with Anemari Fiser, an engineering leader, O'Reilly author, and coach who's spent over a decade helping engineers make the leap from individual contributor to technical leader. Anemari has led teams at ThoughtWorks through massive transformations (think monolith-to-microservices, datacenter-to-AWS migrations), coached 500+ engineers, and trained 300+ tech leads worldwide.
Her new book, "Leveling Up as a Tech Lead," distills years of hands-on experience into practical frameworks for the hardest role in tech. We explore why so many senior engineers struggle with the transition, how to measure success when you're no longer shipping code, and the collaboration techniques that actually work in real-world teams.
This conversation goes deep on the unglamorous but essential work of technical leadershipโfrom running effective 1-on-1s to delegation that empowers rather than bottlenecks, from defining what success means for you to navigating the brutal tech lead job market.
๐ธ KEY TOPICS DISCUSSED
- The journey from software engineer to product directorโand what she learned along the way
- Why soft skills, not just technical expertise, determine your impact at scale
- The critical difference between senior engineers and tech leads
- How to transition from "doing the work" to "enabling the work"
- Why your success as a tech lead depends entirely on your team's success
- The accountability framework that drives consistent growth in others
- How to get people out of their comfort zones without breaking trust
- The power of intentional growth vs. accidental learning
- Measuring impact when you're not writing code anymore
- Why 1-on-1s are your secret weapon (and how to run them effectively)
- The delegation playbook that removes pressure while empowering your team
- Networking strategies that actually work in today's tech job market
- How to interview for tech lead rolesโand spot the red flags
- The collaboration techniques that scale teams beyond individual heroics
โฑ๏ธ CHAPTERS
00:00 Introduction to Anemari Fiser
00:58 Early Career: From University to First Tech Job
04:09 Balancing Work and University in Romania
09:00 First Job Experiences and Learning to Code
12:02 The Importance of Accountability in Leadership
16:07 Strategies for Encouraging Growth in Others
20:03 Intentional Growth and Getting Out of Your Comfort Zone
20:56 Scaling Soft Skills in Tech
23:57 Senior Engineer vs. Tech Lead: What's the Difference?
26:55 Making the Transition from Senior Engineer to Tech Lead
29:40 Expanding Your Team's Impact Beyond Your Own Work
31:01 The Tech Lead Role Across Different Companies
32:32 Balancing Hands-On Technical Work with Leadership
34:29 Defining Success as a Tech Lead
38:10 Measuring Impact and Setting Personal OKRs
42:07 Guiding Junior Engineers: Teaching vs. Enabling
43:51 Job Hunting Strategies in the Current Tech Market
46:10 Why Networking is Your Best Job Search Tool
50:52 Interviewing for Tech Lead Roles: Green Flags and Red Flags
53:28 Key Takeaways from "Leveling Up as a Tech Lead"
๐ RESOURCES MENTIONED
- Anemari's Book: "Leveling Up as a Tech Lead" (O'Reilly) - https://www.amazon.com/[BOOK-LINK]
- Crucial Conversations by Kerry Patterson
- The Culture Map by Erin Meyer
- The Manager's Path by Camille Fournier
- Continuous Deployment by Valentina Servile
- The Silent Patient by Alex Michaelides
๐ FOLLOW ANEMARI
- LinkedIn: https://www.linkedin.com/in/anemari-fiser
- Website: https://anemarifiser.com
๐๏ธ 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/
-
MicroFrontends at Scale with Florian Rappl | The Art of Modular Architecture
What if you could build web applications where teams could deploy independently without breaking each other's code? In this episode, we sit down with Florian Rapplโauthor of "The Art of Micro Frontends," creator of the Piral framework, and Microsoft MVPโto explore how micro frontends are transforming how we build scalable web applications.
Florian shares hard-won lessons from over a decade of building distributed systems, from smart home platforms to enterprise portals for some of Germany's largest companies. We dive deep into the philosophy behind Piral, why modular architecture isn't just about using multiple frameworks, and how micro frontends might be the key to unlocking AI-powered development workflows.
๐ธ Key Topics Discussed:
- The evolution from monolithic frontends to true modular architecture
- Why loose coupling is more important than multi-framework support
- How Piral solves the orchestration problem that Module Federation doesn't
- The "inverse dependency" pattern that makes micro frontends resilient
- Building enterprise portals that scale across hundreds of teams
- Server-side rendering and SEO challenges in micro frontend architectures
- Why Cloudflare Workers and edge computing are game-changers for MFEs
- The future of AI-assisted development in modular codebases
- Lessons learned from smart home systems, customer portals, and production deployments
Whether you're an architect evaluating micro frontends for your organization or a developer curious about modular patterns that actually work in production, this conversation offers battle-tested insights you won't find in the documentation.
โฑ๏ธ Chapters:
00:00 - Introduction & Welcome
01:31 - The Origin Story of Piral
04:30 - The Micro Frontend Landscape in 2019
08:05 - Piral vs Module Federation: Understanding the Difference
12:15 - The Inverse Dependency Pattern
18:20 - Building Enterprise Portals at Scale
25:40 - Server-Side Rendering & SEO Challenges
35:10 - Cloudflare Workers & Edge Computing for Micro Frontends
45:25 - Cross-Framework Components & the Converter API
52:30 - Discovery Services & Dynamic Module Loading
58:15 - AI-Assisted Development & Modular Architecture
1:04:01 - Book Recommendations
๐ Resources Mentioned:
- Piral Framework: https://piral.io
- The Art of Micro Frontends (2nd Edition) by Florian Rappl
- Building Micro-Frontends (2nd Edition) by Luca Mezzalira
- Physics of the Future by Michio Kaku
- Release It! by Michael T. Nygard
- Continuous Delivery by Jez Humble & David Farley
๐ Follow Florian:
- LinkedIn: [Add Florian's LinkedIn]
- Twitter/X: [Add Florian's Twitter]
- GitHub: [Add Florian's GitHub]
๐๏ธ Follow & 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รฑors-scale/
#MicroFrontends #WebDevelopment #SoftwareArchitecture #Piral #ModuleFederation #ScalingSoftware #EnterpriseArchitecture #JavaScript #React #DevOps
๐ฌ What's your experience with micro frontends? Have you tried Piral or other frameworks? Let us know in the comments!
---
Seรฑors @ Scale is a podcast exploring the technical decisions, architectural patterns, and scaling strategies that power modern software systems. Each episode features deep conversations with engineers, architects, and technical leaders building software that serves millions.
- Visa fler
