Señors at Scale - Software Engineering & Tech Leadership

What if every app's data lived in one shared, open database that no company owns? Dan Abramov says that future already exists, and he spent two years building it.

Season 3 of Señors at Scale opens with one of the most recognizable names in frontend. Dan Abramov is the co-creator of Redux, spent nearly a decade on the React core team at Meta, writes overreacted.io, and spent the last couple of years as an engineer at Bluesky working on the app and the AT Protocol. He is now at Vercel working on Next.js.

In this episode Dan explains AT Protocol from first principles: why it is a specification and not a framework, how it splits hosting from apps, why your followers are not your data, and why he thinks Mastodon is a feudal kingdom passing messages on horses. He walks through migrating his own hosting to Eurosky, what it costs to run your own data server, and where a developer should start building. Then we get into Next.js, Turbopack vs Vite, the React Compiler, and why the creator of Redux has not needed a state manager in five years.

Key Topics:

- What AT Protocol is and why it is being brought into the IETF

- The "everything folder": one repository per user, shared across all apps

- AT Proto vs Mastodon and why message passing between instances does not scale

- How a post from someone with 10 million followers actually flows through the network

- Hosting, relays, PLC identity and the three things in your "passport"

- How the Bluesky app itself is built (Go backend, React Native web frontend)

- How companies make money when users own their data

- Migrating your data hosting to Eurosky and the paper cuts along the way

- did:plc vs did:web and what happens if you lose your domain

- Why followers, likes and reposts are just links between JSON records

- Running your own PDS on a VPS or Cloudflare Workers for close to free

- Getting started: PDSLS, Tap, Constellation and building without a backend

- Apps Dan wants to see on AT Proto and why cloning existing products is not enough

- Vercel, Next.js and what Dan wants to fix

- Turbopack vs Vite and the "no bundling in dev" bet

- React Compiler as fine grained reactivity

- Redux as a to-do list: where state should actually live

- Book recommendation: Terence Tao's Analysis I (and its Lean companion)

CONNECT WITH DAN

🦋 Bluesky: https://bsky.app/profile/danabra.mov

🐙 GitHub: https://github.com/gaearon

🌐 Blog: https://overreacted.io

🌐 Website: https://danabra.mov

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/

📸 Show Instagram: https://www.instagram.com/senorsatscale/

📸 Dan's Instagram: https://www.instagram.com/neciudev

ADDITIONAL RESOURCES

- AT Protocol: https://atproto.com

- "There are no instances in AT Proto" (Dan's blog post): https://overreacted.io

- PDSLS repository explorer: https://pdsls.dev

- Tangled (GitHub on AT Proto): https://tangled.org

- Terence Tao, Analysis I Lean companion: https://github.com/teorth/analysis

#ATProtocol #Bluesky #DanAbramov #React #Redux #NextJS #Decentralized #OpenWeb #WebDevelopment #SoftwareEngineering #SeñorsAtScale

💬 Would you move your data hosting off Bluesky's default servers? Or does owning your own JSON not matter to you? Let me know below.

Your product passes every automated accessibility check. Does that mean anyone can actually use it?

Craig Abbott is a Principal Accessibility Specialist at TetraLogical and the former Head of Accessibility at the UK's Department for Work and Pensions, one of the largest government departments in the country, where he built a dedicated accessibility practice from nothing and open sourced the DWP Accessibility Manual. He has over 15 years in user centred design, previously working as a designer and design manager, and has led accessibility work across the public sector and at Elastic.

In this episode we get into what "sustainable accessibility" actually means, why culture is harder to change than capability, and how to stop accessibility from walking out the door when the one passionate person leaves. Craig breaks down his three C's framework (compliance, culture, capability), the screen reader testing stack he actually recommends, and what you can realistically automate in a CI pipeline with Playwright, Cucumber and Guidepup.

We also get into the uncomfortable stuff. Automated tools only catch around 40% of issues. A page can pass WCAG with two pixel text and invisible links. And with 95.8% of the top million websites failing automated checks, the LLMs writing your front end code were trained on all of it. Craig is autistic and ADHD, and he closes on cognitive accessibility, the WCAG AAA gap, and why designing for neurodivergent users is still mostly ignored.

Key Topics:

- What sustainable accessibility means and why third party audits alone don't get you there

- Building an accessibility practice from scratch inside a 100,000 person organisation

- The three C's: compliance, culture and capability, and why culture is the hardest

- Embedding accessibility so it survives when the champion leaves

- JAWS vs NVDA vs VoiceOver vs TalkBack, and why the "worse" reader is the better test

- Running screen readers in VMs and BrowserStack without expensive licences

- Accessibility acceptance tests in CI with Playwright, Cucumber and Guidepup

- Why compliant does not mean usable, with two pixel fonts and invisible links as proof

- Shifting accessibility left into design and research, not throwing it at developers

- Why you cannot detect screen reader users in your analytics

- The three highest impact things: automated tools, keyboard only, structured content

- Why CSS and design systems aren't opinionated enough

- AI-generated front-end code and the 95.8% problem

- Whether AI browsing replaces screen readers, and why LLM interfaces are inaccessible too

- Designing for neurodivergence, WCAG AAA, and the COGA guidance

CONNECT WITH CRAIG

💼 LinkedIn: https://www.linkedin.com/in/abbott567/

🐦 X: https://x.com/abbott567

🦋 Bluesky: https://bsky.app/profile/craigabbott.bsky.social

🌐 Website: https://www.craigabbott.co.uk

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/

📸 Show Instagram: https://www.instagram.com/senorsatscale/

📸 Dan's Instagram: https://www.instagram.com/neciudev

ADDITIONAL RESOURCES

TetraLogical: https://tetralogical.com

WebAIM Million report: https://webaim.org/projects/million/

W3C Cognitive Accessibility (COGA): https://www.w3.org/WAI/cognitive/

Guidepup: https://www.guidepup.dev/

axe-con: https://www.deque.com/axe-con/

#accessibility #a11y #webdevelopment #wcag #frontend #inclusivedesign #softwareengineering #neurodiversity #designsystems #senorsatscale

💬 Has your team ever shipped something fully compliant that users still couldn't use? Tell me about it in the comments.

Is versatility the skill that actually survives the AI shift?

In this episode of Señors at Scale, I sit down with Carmen Huidobro, CTO at Incredible Bee in Vienna. Carmen has spent 17 years in tech, almost all of it freelancing, working across Objective-C, Ruby on Rails, the web, mobile, hardware, and even ABAP in an SAP consultancy. Along the way, she spent five years in developer relations and developer education, and now leads engineering on long-lived macOS products like Renamer.

Her argument is that the debate about generalists versus specialists misses the point. What matters is being an expert at adapting: recognizing patterns, carrying solutions across stacks, and dropping into unfamiliar environments without bringing chaos with you. Niches are not going away, but the durable skill is the one that moves between them.

We also get into the part most teams get wrong: how to ship AI without betraying the people who use your software. Carmen walks through adding a local LLM to a twenty-year-old Mac app using Mistral and a llama.cpp runtime, why the model downloads on demand instead of shipping in the binary, and why it is opt-in rather than opt-out. Plus, the refugee hackathon app she built in 2016 that the City of Vienna still runs today, why she will not take money from junior developers for bootcamps, and what she calls "white guy-driven development".

Key Topics:

- Why versatility beats both generalism and specialization

- Seventeen years of freelancing across stacks, platforms, and industries

- SAP, ABAP, and why niche expertise never disappears

- Building an ethical AI toolkit: Mistral, llama.cpp, and on-device inference

- Adding an LLM to a legacy macOS app without breaking user trust

- Opt in over opt out, and why you should never take features away

- Deciding what should be automated and what should not

- Pushing back when investors demand AI in the product

- Where2Help: the 2016 refugee hackathon project in Vienna still runs

- Why the junior developer market broke and what bootcamps can still fix

- Stop telling women they have imposter syndrome

- What AI will never teach you about solving problems

CONNECT WITH CARMEN

🌐 Website: https://carmenh.dev

🐦 X: https://x.com/hola_soy_milk

🐙 GitHub: https://github.com/hola-soy-milk

🐘 Mastodon: https://hola-soy-milk.online/

FOLLOW & SUBSCRIBE

🎙️ Podcast: https://neciudan.dev/senors-at-scale

📬 Newsletter: https://neciudan.dev/subscribe

💼 My LinkedIn: https://www.linkedin.com/in/neciudan

🏢 Show LinkedIn: https://www.linkedin.com/company/senors-scale/

📸 Show Instagram: https://www.instagram.com/senorsatscale/

📸 My Instagram: https://www.instagram.com/neciudev

ADDITIONAL RESOURCES

Incredible Bee: https://incrediblebee.com

Bad Website Club: https://badwebsite.club

Distribute Aid: https://distributeaid.org

#Versatility #Freelancing #Automation #EthicalAI #LocalLLM #Mistral #macOS #OpenSource #SoftwareEngineering #CTO #Podcast #SenorsAtScale

💬 Are you betting on going deep or going wide right now? Tell me in the comments.

Is testing, not coding, the real bottleneck of the AI era?

Marko Gaćeša is Head of Product at Semaphore, the agent native CI/CD platform built for coding agents: fast, affordable, enterprise-ready, and fully open source. A serial entrepreneur and technologist, Marko founded Dry Tools, served as Chief Product Officer at Alchemy Cloud, and has spent his career building high-quality software across domains such as medical equipment and industrial automation before entering the crowded CI/CD market.

In this episode, Marko breaks down what it takes to build a product for developers: why flaky tests are the worst enemy of fast delivery, how SemAI uses skills and agents to automate everything from GitHub Actions migration to flaky test analysis, and why the future developer experience lives inside your coding agent, not in a browser tab. We also go deep on the product side: running experiments with feature flags, pricing a CI/CD platform when a "minute of CI" means something different everywhere, product-led growth versus B2B sales, and structuring lean product teams when your engineers are the domain experts.

Key Topics:

- What Semaphore does and why CI/CD matters

- Testing is the biggest bottleneck in the age of coding agents

- What "agent native" CI/CD really means

- Flaky tests and how SemAI helps agents debug them

- Migrating from GitHub Actions automatically

- How Semaphore achieves faster and cheaper builds

- Running product experiments on infrastructure tools

- Pricing strategy in the CI/CD market

- Should AI agents trigger deployments?

- Product team structure in developer tools

- Book recommendations for product-minded engineers

CONNECT WITH MARKO & SEMAPHORE

💼 Marko on LinkedIn: https://www.linkedin.com/in/markogacesa/

🌐 Semaphore: https://semaphore.io/

🐦 Semaphore on X: https://x.com/semaphoreci

🐙 Semaphore on GitHub: https://github.com/semaphoreio

💼 Semaphore on LinkedIn: https://www.linkedin.com/company/semaphoreci

FOLLOW & SUBSCRIBE

🎙️ Podcast: https://neciudan.dev/senors-at-scale

📬 Newsletter: https://neciudan.dev/subscribe

📸 Instagram: https://www.instagram.com/senorsatscale/

📸 Dan's Instagram: https://www.instagram.com/neciudev

💼 Dan's LinkedIn: https://www.linkedin.com/in/neciudan

💼 Show LinkedIn: https://www.linkedin.com/company/senors-scale/

ADDITIONAL RESOURCES

- Semaphore open source repo: https://github.com/semaphoreio/semaphore/

- Semaphore CI/CD benchmark: https://semaphore.io/semaphore-ci-cd-benchmark-performance-and-cost-analysis

- Semaphore docs: https://docs.semaphore.io/

- Books mentioned: Hug Your Haters by Jay Baer, plus Inspired, Empowered, and Transformed by Marty Cagan and the Silicon Valley Product Group

#CICD #Semaphore #ProductEngineering #AgentNative #DevTools #DeveloperExperience #AIAgents #SoftwareEngineering

💬 Would you let an AI agent trigger your production deployments? Tell us in the comments.

Everyone can buy the same GitHub Copilot licenses. So what actually makes a company AI native?

In this episode of Señors at Scale, Dan Neciu sits down with Maxim Salnikov, AI Dev Tools Solution Engineer at Microsoft, where he leads AI native development enablement for over 100 enterprise customers of Microsoft and GitHub in Norway. Maxim has been building for the web since the late 90s and now spends his days inside real enterprise dev teams, watching how AI adoption succeeds and fails across finance, energy, agriculture, and pure software companies.

Maxim breaks down why AI adoption is a change management problem, not a technology problem, and why buying licenses is the easy part. We get into the anatomy of an AI harness, the internal layer that ships with tools like Copilot and Claude Code, and the external layer that successful companies build on top for their own codebases. He also makes the case for two new job titles emerging inside dev teams: context engineers and agent ops.

Key Topics:

- Why startups outpace enterprises in AI adoption, and how to close the gap

- Handling AI skeptics: why one bad experience in 2023 shouldn't be the final verdict

- Code as a secondary artifact: the harness is what you actually build

- Internal vs external harness layers, and how the VS Code team builds its own tools

- Context engineers and agent ops: the new roles appearing in team topology

- The AI superheroes anti-pattern and why it doesn't scale

- Managing agent skills like dependencies with APM (Agent Package Manager)

- How to become an AI native engineer: orchestration over one-to-one chat

CONNECT WITH MAXIM

💼 LinkedIn: https://www.linkedin.com/in/webmax/

🐦 X: https://x.com/webmaxru

🐙 GitHub: https://github.com/webmaxru

🌐 Sessionize: https://sessionize.com/maxim-salnikov/

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

📖 Agentic SDLC Handbook (free book mentioned in the episode)

📦 APM (Agent Package Manager)

#AINativeDevelopment #GitHubCopilot #ContextEngineering #AIHarness #SoftwareEngineering #Microsoft #AgenticAI #DeveloperProductivity

💬 Is your team building its own harness on top of AI dev tools, or running them out of the box? Drop a comment 👇

What if your app's state didn't live in memory, but in the URL?

François Best is a freelance web developer, open sourcer, and founder of 47ng, where he builds web applications with a privacy-first approach. He is the creator of nuqs, the type-safe search param state manager for React with over 10,000 GitHub stars, used by companies like Sentry, Supabase, Vercel, and Clerk.

In this episode, François shares the full story of nuqs, from a woodworking calculator he built during the pandemic to a framework-agnostic library supporting Next.js, React Router, Remix, and TanStack. We dig into the internals: the async update queue, browser rate limits on the History API, throttling and debouncing, render count budgets, and the end-to-end test suite that keeps it all stable across frameworks.

We also go beyond the library. François breaks down the recent npm supply chain attacks, explains how staged publishing and reproducible builds protect maintainers, shares how AI agents changed his workflow (including a Cypress to Playwright migration done by Claude Code on Christmas Day), and makes the case for running local AI models when your code can't leave the building.

Key Topics:

- What nuqs is and the origin story behind it

- URL as the source of truth and the async scheduling engine

- Browser rate limits, throttling, and debounce semantics

- Framework adapters: Next.js, React Router, Remix, TanStack

- End-to-end testing across frameworks and render count budgets

- What state belongs in the URL (and what doesn't)

- Hidden nuqs features: loaders, serializers, URL keys, standard schema

- The npm supply chain attacks and how to defend as a maintainer

- AI agents in open source: migrations, RFC prototyping, slop PRs

- Local AI models for privacy-conscious companies

CONNECT WITH FRANÇOIS

🐙 GitHub: https://github.com/franky47

🦋 Bluesky: https://bsky.app/profile/francoisbest.com

🌐 Website: https://francoisbest.com

FOLLOW & SUBSCRIBE

🎙️ Podcast: https://neciudan.dev/senors-at-scale

📬 Newsletter: https://neciudan.dev/subscribe

📸 Instagram: https://www.instagram.com/senorsatscale/

📸 Dan's Instagram: https://www.instagram.com/neciudev

💼 Dan's LinkedIn: https://www.linkedin.com/in/neciudan

💼 Show LinkedIn: https://www.linkedin.com/company/senors-scale/

ADDITIONAL RESOURCES

- nuqs: https://nuqs.dev

- nuqs on GitHub: https://github.com/47ng/nuqs

- TkDodo's blog: https://tkdodo.eu/blog

- Aurora Scharff's blog: https://aurorascharff.no

#React #nuqs #TypeScript #URLState #NextJS #OpenSource #WebDevelopment #SoftwareEngineering #SenorsAtScale

💬 What state do you keep in the URL, and have you ever rolled your own search param sync? Tell us in the comments.

What happens to frontend engineering when software stops being deterministic?

In this episode of Señors at Scale, Dan Neciu sits down with Susanna Wong, Staff Software Engineer at Typeform and Google Developer Expert in Web Technologies since 2020. Susanna's path is anything but typical: she studied engineering in the US, spent close to seven years as an architect and computational designer at firms like Arup, then pivoted back into software, building Kedro and Kedro-Viz at QuantumBlack before moving into AI features at V7 and now Typeform.

Susanna breaks down the shift from training your own ML models to building on top of LLMs, what Web AI and offline browser models really offer, and the cross-browser hurdles still blocking local-first AI. She also takes us inside Typeform's multi-agent system, how the team thinks about evals for non-deterministic features, and why WebMCP could change how all of us build websites.

Key Topics:

- From architecture and computational design to frontend AI

- Building Kedro and Kedro-Viz at QuantumBlack

- Why training your own models gave way to the LLM baseline

- Web AI, offline models, and on-device inference

- The cross-browser problem with local-first AI

- Typeform's multi-agent system: LangChain, A2A, MCP tools

- Evals as unit tests for non-deterministic AI features

- Offline vs online evals and tracking drift in production

- WebMCP: bringing the web to agents

💼 LinkedIn: https://www.linkedin.com/in/susanna-wong-london/

🐦 X: https://x.com/studioswong

🌐 Talks: https://www.youtube.com/watch?v=JcLZGfXKk8c

FOLLOW & SUBSCRIBE

🎙️ Podcast: https://neciudan.dev/senors-at-scale

📩 Newsletter: https://neciudan.dev/subscribe

💼 Show LinkedIn: https://www.linkedin.com/company/senors-scale/

📸 Show 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

- Kedro: https://kedro.org

- WebMCP / React Paris talk on the agent web

- Typeform AI: https://www.typeform.com

#WebAI #WebMCP #SoftwareEngineering #Frontend #AIAgents #Evals #StaffEngineer #Typeform #MachineLearning #Podcast #SenorsAtScale

💬 Are you building with offline browser models yet, or still calling the API for everything? Let me know below.

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? 💬

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 → world
• Test parties, dogfooding, and catching weirdness before users do
• Protogen, CDF, and how Canva moves data between frontend and backend
• Operational transforms for real-time collaboration
• The Performance Decay Cycle and why "performance sprints" are broken
• Fast by Default: making speed everyone's responsibility, not just engineering
• Perceived performance, AI loading states, and the Pac-Man tape loader lesson
• Async 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.

In this episode of Señors @ Scale, Dan sits down with Daniel Roe, leader of the Nuxt Core team at Vercel, for an in-depth conversation about building and scaling with Nuxt, Vue's most powerful meta-framework.

Daniel shares his journey from the Laravel world into Vue and Nuxt, revealing how he went from being a user to becoming the lead maintainer of one of the most important frameworks in the JavaScript ecosystem. We explore the evolution of Nuxt, the philosophy behind its developer experience, and how understanding user pain points shapes every feature decision.

The conversation dives deep into the technical aspects that matter when building at scale: rendering strategies and when to choose static over server-side rendering, the revolutionary Nitro server engine and how it transforms backend flexibility, data fetching patterns and best practices for performance, and the module ecosystem that empowers developers to extend Nuxt in powerful ways.

Daniel explains why "always go for static rendering if you can" isn't just advice — it's a performance philosophy. He breaks down how Nuxt makes it easier to be your own target audience as a framework developer, and why contributing to open source is ultimately about joy and giving back to the community.

Whether you're building with Nuxt, considering it for your next project, or just curious about how modern frameworks are designed with developer experience at their core, this episode offers invaluable insights from someone shaping the future of Vue development.

Chapters

00:00 Introduction and Daniel's Background

03:45 From Laravel to Vue and Nuxt

08:20 Becoming a Nuxt Core Team Member

12:30 The Evolution of Nuxt and Developer Experience

18:15 Understanding User Pain Points

24:00 Rendering Strategies: Static vs Server-Side

29:45 The Nitro Server Engine Revolution

35:20 Data Fetching Best Practices

41:10 The Power of Nuxt Modules

46:30 Contributing to Open Source

51:00 The Future of Nuxt

53:52 Outro

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

🌐 Nuxt: https://nuxt.com

💬 Daniel Roe on GitHub: https://github.com/danielroe

🚀 Vercel: https://vercel.com

#nuxt #vue #javascript #webdevelopment #frontend #serverless #nitro #vercel #opensource #developerexperience #señorsatscale

Don't forget to like, comment, and subscribe for more engineering stories from the front lines.

How is your team using Nuxt or Vue to scale? Share below 👇

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.

🎙 About the Podcast:

Join host Neciu Dan as he sits down with Stefano Magni, a senior front-end engineer and tech lead at Preply, to explore the intricacies of building a robust design system and the journey of working in public.

Stefano shares his insights on the importance of skills, reputation, and networking in shaping a successful career. Discover how his experiences from building Flash mini-games to architecting React-based systems have influenced his approach to engineering excellence.

In this episode, they discuss:

The pivotal moment that led Stefano to work in public

How Preply's design system impacts user experience

The balance between perfectionism and pragmatism in engineering

The role of data-driven decisions in Preply's culture

Best practices for managing large codebases without tests

Stefano also shares his journey from a Flash developer to a leader in the design system space, emphasizing the value of sharing knowledge and building a strong professional network.

Chapters:

00:00 Introduction to Stefano Magni and Preply

05:12 The Importance of Public Work

12:45 Building a Design System at Preply

18:30 Balancing Perfectionism and Pragmatism

25:00 Data-Driven Culture at Preply

32:15 Managing Large Codebases Without Tests

40:00 The Journey from Flash to React

47:30 Networking and Reputation in Tech

55:00 Closing Thoughts and Future Plans

📚Links & Resources:

📸 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/

#designsystem #frontend #engineeringexcellence #preply #networking #publicwork #softwaredevelopment #señorsatscale

Don’t forget to like, comment, and subscribe for more engineering stories from the front lines. How is your team approaching design systems and public work? Share below 👇

In this episode of Señors @ Scale, Erik Grijzen, Principal Software Engineer at New Relic, joins Dan to share his journey from web designer to principal architect and what it really takes to scale UI development across dozens of teams. Erik walks us through how New Relic built one of the first large-scale micro-frontend architectures before the term even existed, designing tooling that lets teams ship independently—from CLI bootstrapping to runtime composition. He explains how to manage hundreds of deploys a day without breaking the platform, and how observability keeps complex systems reliable when they inevitably fail.We dive deep into observability at scale—how metrics, logs, traces, and business data blend to show what’s happening inside distributed systems, and why visibility isn’t just for developers anymore but a business priority tied to uptime, revenue, and customer trust.Erik also shares what technical leadership looks like at New Relic: influencing without authority, scaling architecture through culture, and using processes like RFCs and change documents to make better decisions. He emphasizes writing before building, POCs before roadmaps, and the mindset shift from coding features to guiding direction.The episode closes with a thoughtful discussion on burnout, balance, and habits for longevity in engineering—from sports and shutdown rituals to books like A Philosophy of Software Design and 4,000 Weeks.Whether you’re an architect, staff engineer, or team lead scaling a complex frontend platform, this episode is packed with real lessons on architecture, observability, and leadership at scale.Chapters00:00 Introduction to Erik Grijzen and His Journey08:48 Building a Unified Platform at New Relic13:34 Challenges and Solutions in Micro-Frontend Development18:47 How Observability Works Behind the Scenes32:02 Organizing Teams Around Domains36:38 Testing in Micro Frontends43:38 Technical Leadership and Management49:38 Effective Processes for Teams54:05 Decompressing and Work-Life Balance---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[https://newrelic.com/blog](https://newrelic.com/blog)[https://micro-frontends.org/](https://micro-frontends.org/)[https://web.stanford.edu/~ouster/cgi-bin/book.php](https://web.stanford.edu/~ouster/cgi-bin/book.php)[https://oliverburkeman.com/books/4000-weeks/](https://oliverburkeman.com/books/4000-weeks/)#microfrontends #observability #softwarearchitecture #newrelic #frontend #softwareengineering #leadership #teammanagement #engineeringculture #señorsatscaleDon’t forget to like, comment, and subscribe for more engineering stories from the front lines. How is your team scaling architecture and observability? Share below 👇

In this episode of Señors @ Scale, Kateryna Porchienova, Senior Engineering Manager at Buffer, joins Dan to talk about her journey into programming, the craft of UI animation, and why accessibility should be a standard — not an afterthought.Kateryna shares how her very first app, built in high school, ended up helping children with disabilities learn from home — sparking a lifelong commitment to inclusion in tech. She walks us through best practices for accessibility, from learning to use a screen reader to understanding semantic HTML and ARIA roles.We also dive into the tooling side — from React Aria and Radix to Storybook and Lighthouse — and discuss how AI can both help and hurt accessibility efforts. Kateryna explains the most common mistakes developers make (like overusing ARIA labels), why animation and motion preferences matter for users’ health, and how to advocate for accessibility within engineering teams and company culture.The episode closes with her favorite book recommendations on product development and communication, underscoring how great engineering is as much about people as it is about code.🎯 Whether you’re a frontend developer, design system engineer, or tech lead, this episode is packed with real stories, practical takeaways, and thoughtful lessons from years of building inclusive products at scale.Chapters00:00 Introduction to Katarina Porchienova02:40 The Importance of Animation in UI Design05:23 Katarina's Journey into Programming09:02 Exploring Accessibility in Development11:43 Best Practices for Accessibility14:18 Tools and Libraries for Accessibility Testing17:09 The Role of AI in Accessibility20:44 Common Mistakes in Accessibility Implementation24:14 Advocating for Accessibility in Companies30:37 Recommended Books and Closing Thoughts---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/---Here are some additional resources to dive deeper into the topic and learn more:- If you are just starting with accessibility, this free course on Udacity is awesome: 🔗 [Web Accessibility Course / Udacity](https://www.udacity.com/course/web-accessibility--ud891)- A11ycasts series on YouTube is great for bite-sized content on accessibility and screen-reader tutorials🔗 [A11ycasts with Rob Dodson](https://www.youtube.com/watch?v=HtTyRajRuyY&list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g)- [Adrian Roselli blog](https://adrianroselli.com/posts) is an awesome resource for deep dives on specific topics and details- [Web Content Accessibility Guidelines (WCAG) 2.1](https://www.w3.org/TR/WCAG/)- [ARIA Authoring Practices Guide (APG)](https://www.w3.org/WAI/ARIA/apg/) is super useful for developing different widgets- [HTML Accessibility API Mappings](https://www.w3.org/TR/html-aam/) to see how native HTML elements map to accessibility tree- [Aria Live Regions documentation](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions) to learn more about announcements and live regions- [A11Y support](https://a11ysupport.io/) shows support for various ARIA attributes across different screen readers#accessibility #webdevelopment #frontend #uiux #animation #buffer #reactaria #softwareengineering #a11y #engineeringculture #señorsatscaleDon’t forget to like, comment, and subscribe for more engineering stories from the front lines.How is your team building accessibility into your workflow? Share below 👇

In this episode of Señors @ Scale, Adrian Marin, founder of AVO and host of FriendlyRB, joins Dan to share his journey into programming and his deep commitment to the Ruby ecosystem.Adrian walks us through his transition from a non-technical background into software development and how he fell in love with Ruby on Rails for its elegance and productivity. He explains why everything in Ruby is an object, what makes Rails still the fastest way to build apps, and how Hotwire redefines frontend development with minimal JavaScript.We also dive into the tools and frameworks shaping today’s developer experience: the rise of Tailwind CSS, why Adrian built AVO to make internal tooling in Rails as smooth as Laravel Nova, and how the Ruby ecosystem continues to thrive with innovative libraries and first-party tools.Beyond code, Adrian shares how community and creativity intersect in tech — from organizing FriendlyRB in Romania to inventing a Ruby Passport that lets conference-goers collect stamps and connect with peers across events.🎯 Whether you’re a Rubyist, Rails engineer, or curious about how productivity frameworks scale, this episode is packed with insights, stories, and lessons from the trenches.---Chapters00:00 Introduction to Adrian Marin and His Journey04:33 The Early Days of Programming06:58 Nostalgia for the Old Web Development Days08:53 Evolution of Web Development Tools12:45 The Impact of AI on Development14:11 The Rise of Tailwind CSS15:16 Adrian's Love for Tailwind CSS20:46 Transitioning from PHP to Ruby on Rails29:35 Building AVO: A Toolkit for Internal Tools34:31 Understanding Hotwire in Rails36:29 Understanding Client-Server Interactions39:30 The Ruby Ecosystem and Community Engagement44:36 Creating Memorable Conferences46:10 Innovative Networking: The Ruby Passport54:46 Getting Started with Ruby on Rails01:06:24 Balancing Work and Family Life01:07:42 Recommended Reads for Developers---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/---#rubyonrails #ruby #rails #hotwire #tailwindcss #avo #softwaredevelopment #developercommunity #webdevelopment #engineeringculture #señorsatscaleDon’t forget to like, comment, and subscribe for more engineering stories from the front lines. Are you building with Rails at scale? Share your experience below 👇

In this episode of Señors @ Scale, Andreas Panopoulos — Staff Software Engineer at Hack the Box and co-organizer of Vue.js Athens — joins Dan to share his journey from building jQuery landing pages to leading frontend teams powered by Vue.Andreas walks us through the evolution of Vue.js, from version 2 to 3, and how features like the Composition API and TypeScript support transformed developer experience. He shares what it was like to rewrite Hack the Box’s Academy platform on Nuxt 3, why Vue scales for millions of users, and what performance practices every frontend team should keep in mind.We also dive into the human side of engineering: why understanding the basics of JavaScript is essential even when using frameworks, how public speaking and community organizing can accelerate growth, and why keeping things simple often beats overengineering.Along the way, Andreas reflects on lessons learned from his early career, his transition to staff engineer, and the role of community in shaping modern engineering culture.🎯 Whether you’re a Vue enthusiast, frontend engineer, or developer community organizer, this episode is packed with practical insights and stories from the trenches.Chapters00:00 Introduction to Andreas Panopoulos02:56 Andreas's Journey into Programming09:52 Transitioning to Frontend Development17:52 Current Role at Hack the Box21:41 Vue 2 vs Vue 3: A Developer's Perspective26:13 Lessons Learned from Early Career30:21 Transition to Staff Engineer34:46 Project Updates and Future Plans35:54 Understanding Hack the Box38:25 Security Practices in Development39:47 Performance and User Experience42:03 Vue's Popularity in Athens46:12 Business Logic and Frameworks47:27 Challenges in Finding Speakers52:26 Public Speaking Experiences56:34 Relaxation and Personal Interests58:00 Book RecommendationsFollow & 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/#vuejs #vue3 #nuxt #frontenddevelopment #javascript #hackthebox #softwareengineering #webdevelopment #engineeringculture #señorsatscaleDon’t forget to like, comment, and subscribe for more engineering stories from the front lines. Are you using Vue at scale in your team? Share your experience below 👇

In this episode of Señors @ Scale, Faris Aziz — Staff Front-End Engineer at Small PDF, international speaker, and co-founder of ZurichJS — joins Dan to talk about scaling both frontend architecture and engineering culture.Faris shares his unconventional journey from CrossFit trainer to software engineer, and how personal projects became his gateway into tech. He opens up about the realities of working on applications serving 30 million+ users, why BFF architecture is such a powerful pattern for managing data between front-end and back-end, and the hidden pitfalls of performance when building with React and Next.js.We also dig into the human side of architecture: how observability, error management, and developer experience shape reliable systems; why ownership and accountability drive better outcomes than process checklists; and how stress can be reframed when you work in a culture of trust.And beyond code, Faris reflects on community: what it takes to co-found a thriving JavaScript meetup in Zurich, why meetups are “mini start-ups,” and how community building fuels personal and professional growth.🎯 Whether you’re a frontend engineer, engineering manager, or developer community organizer, this episode is packed with architectural insights and real-world lessons from the trenches.---Chapters00:00 Introduction to Faris Aziz and His Journey05:46 From Fitness to Coding: The Bootcamp Experience08:33 Building Personal Projects and Learning by Doing11:28 The Impact of Global Work Culture on Engineering14:24 Co-founding ZurichJS: Building Community in Tech19:57 Technical Insights: React vs. Next.js at Scale25:38 Scaling Challenges in Data Representation31:35 Understanding the BFF Architecture40:44 Authentication and Security in BFFs43:30 Comparing BFF with GraphQL and TRPC49:09 Innovative UI Approaches in Application Development51:27 A Day in the Life of a Staff Engineer52:13 Strategic Engineering at Scale55:46 Managing Stress and Engineering Culture01:01:06 Finding Balance in High-Stakes Environments01:05:37 Book Recommendations and Personal Insights---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/#frontend #nextjs #bffarchitecture #javascript #react #softwaredevelopment #engineeringculture #techevents #zurichjs #webdevelopment #señorsatscaleDon’t forget to like, comment, and subscribe for more engineering stories from the front lines. Have you ever built — or struggled with — frontend architecture at scale? Share your experience below 👇

In this episode of Señors @ Scale, Aris — founder of CityJS and longtime community builder — joins Dan to talk about the journey from small local meetups to organizing one of the fastest-growing global JavaScript conferences.Aris shares his unlikely path into programming, starting as a basketball-loving student in Greece with no computer at home, to innovating on the job with early Java projects, and eventually embracing frontend frameworks like Angular, React, and Vue. Along the way, he reflects on the competitive yet collaborative nature of programming, the evolution of the frontend ecosystem, and why choosing the “best” framework often depends less on hype and more on context.We dig into the heart of community building: why meetups matter beyond the pizza, how to create opportunities for first-time speakers, and the hidden challenges of finding sponsors and keeping attendees engaged. Aris also opens up about the leap from organizing monthly gatherings to running large-scale international conferences, and why he believes conferences should be treated as professional training — not optional perks.🎯 Whether you’re a frontend developer, a meetup organizer, or simply curious about what it takes to build thriving developer communities, this conversation offers a rare inside look at the messy, human, and rewarding world of tech events.Chapters00:00 Introduction and Name Origins04:14 Aris's Journey into Programming06:56 First Job and Early Experiences09:32 Transition to Frontend Development12:23 Framework Preferences and Ecosystem14:56 Meetups and Community Building17:44 The Importance of Networking20:11 Organizing Meetups and Conferences22:54 Creating Opportunities for New Speakers25:41 Challenges in Meetup Attendance27:32 Sponsorship Strategies for Meetups34:28 Transitioning from Meetups to Conferences39:37 The Value of Conferences for ProfessionalsFollow & 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/#javascript #conferences #developercommunity #frontend #meetups #cityjs #softwareengineering #techevents #communitybuilding #señorsatscale #webdevelopmentDon’t forget to like, comment, and subscribe for more engineering stories from the front lines. Have you ever spoken — or wanted to speak — at a tech meetup or conference? Share your experience below 👇

In this episode of Señors @ Scale, Eric Rasmussen — creator of Redux Form and React Final Form, now Principal Product Engineer at Attio — joins Dan to talk about building open source at scale, developer experience, and the lessons learned from two decades of shipping frontend software.Eric shares his journey from early experiments with BASIC and FoxPro to designing Attio’s secure SDK ecosystem, which enables third-party developers to extend a next-generation CRM. Along the way, he opens up about the pitfalls of feature creep in open source, the evolution from Redux Form to React Final Form, and how AI is already reshaping documentation.We dive into why developer ergonomics matter more than ever, how strict design systems preserve product quality, and what it really takes to manage breaking changes when your code runs in thousands of apps. Eric also offers practical advice for juniors looking to break into open source, as well as insights on testing strategies, state machines, and the libraries he can’t live without.🎯 Whether you’re maintaining a popular open source library, building SDKs for other developers, or just curious about the hidden costs of “yes” in software design, this conversation is full of hard-won lessons from the trenches.Chapters00:00 Introduction to Eric Rasmussen and His Journey05:34 Early Programming Experiences and First Job08:01 Transition to Principal Engineer at Atio10:37 Understanding Atio's CRM and Its Market Position13:08 Developer Experience and Building for Other Developers15:29 The Role of Documentation in Developer Tools18:03 SDK Development and Framework Choices20:30 Building a Secure and Custom Runtime22:54 Managing Breaking Changes and Developer Feedback25:28 The Creation of Redux Form and Its Impact27:59 Testing Strategies for SDKs and Components33:48 Building a Design System35:27 React Final Form: Evolution and Insights41:11 The Journey from Redux to React Final Form46:08 Choosing State Management Solutions48:10 Overused Libraries and Tools54:25 Advice for Junior Developers59:32 Book Recommendations and Closing Thoughts01:04:25 OutroFollow & 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/#opensource #reduxform #reactfinalform #frontend #developerexperience #sdk #documentation #designsystems #softwareengineering #señorsatscale #techtalks #webdevelopmentDon’t forget to like, comment, and subscribe for more engineering stories from the front lines. What’s your favorite open source library — and how has it shaped your work? Share below 👇Don’t forget to like, comment, and subscribe for more engineering stories from the front lines.

In this episode of Señors @ Scale, Front-End Engineer and ADPList Top 100 Mentor Eduardo Aparicio-Cardenas joins Dan to talk about mentorship, career growth, and leadership at scale — from debugging real-world performance issues to guiding engineers through promotions and burnout.Eduardo shares lessons from 15+ years building web products, why perception often matters more than output for promotions, and how curiosity and frustration can be powerful motivators for learning. He breaks down what makes a strong tech lead, how to run compelling mock interviews, and why knowledge sharing is the ultimate multiplier for both mentor and mentee.They also discuss system design interviews (and why front-end design is often overlooked), strategies for breaking down problems, and what it truly means to grow from senior to staff to principal engineer.🎯 Whether you're mentoring juniors, preparing for a promotion, or just trying to be a better communicator on your team, this episode is packed with practical advice for engineers navigating their careers.Get in touch with Eduardo here https://eduardo-aparicio-cardenes.website, https://medium.com/@byeduardoac and if you are looking for a mentor: https://adplist.org/mentors/eduardo-dev or https://eduardo-aparicio-cardenes.website/mentor-profileChapters00:00 Journey to Front-End Engineering11:11 Transitioning to Happening and Current Projects18:51 Becoming a Mentor and Sharing Knowledge19:14 The Journey of Mentorship23:37 Understanding Mentee Needs28:18 The Importance of Sharing Knowledge31:43 Personal Growth and Agency36:13 Navigating Promotions and Perception39:16 Navigating Project Expectations in Tech Companies41:56 The Role of a Tech Lead44:39 Effective Communication in Tech47:18 Interview Strategies for Success49:54 System Design Insights52:22 Handling Burnout and Career Growth54:48 Recommended Reads for ProfessionalsFollow & 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/#softwareengineering #mentorship #frontend #career #promotion #systemdesign #burnout #staffengineer #leadership #señorsatscale #techtalks #webdevelopmentDon’t forget to like, comment, and subscribe for more engineering stories from the front lines. Have you had a mentor who changed the course of your career? Share your story below 👇

In this engaging conversation, Jose Calderon, a lead software engineer at JP Morgan Chase, shares his journey into software engineering, his passion for Java and the Spring ecosystem, and the importance of documentation and decision-making in software architecture.

He discusses the evolving role of AI in coding, offers tips for learning Java, and emphasizes the significance of mentoring future engineers.

The conversation also touches on crafting engaging conference talks, testing strategies for enterprise software, and the balance between refactoring and rewriting code. Jose concludes with book recommendations and insights into the gaming world as a form of relaxation.

Takeaways

• Jose's journey into software engineering began with a passion for fixing computers and playing games.
• Java's ecosystem is robust, with a strong community and rapid evolution.
• Documentation of architectural decisions is crucial for future reference and understanding.
• AI tools can enhance productivity but should not replace fundamental coding skills.
• Unit tests should serve as documentation for code behavior.
• The choice between refactoring and rewriting code depends on the stability and control of the existing system.
• Chaos engineering helps teams prepare for unexpected failures in production environments.
• Mentoring future engineers is essential for fostering a strong tech community.
• Crafting engaging conference talks involves storytelling and relatable analogies.
• Gaming can serve as a form of relaxation and mental recharge for developers.

Sound Bites

"You can build whatever you want and play around."

"The world is your oyster with Java."

"You can simplify and still be effective."

Keywords

software engineering, Java, Spring, coding, technology, software architecture, mentoring, conference talks, decision making, testing strategies, chaos engineering, AI in coding, book recommendations, gaming

🎙️ In this episode of Señors @ Scale, Principal Engineer Tudor Barbu (ex-Personio, Skyscanner) shares two decades of software engineering lessons — from hacking on cassette-based machines to leading platform efforts in modern frontend teams.

We talk debugging horror stories, the evolution of tech roles post-pandemic, and the shift from chasing technical perfection to delivering user value. Tudor breaks down what it means to be a pragmatic engineer, how he interviews for adaptability, and why ownership (not just code) drives results.

Whether you're mentoring juniors, scaling architecture, or just tired of reading octal bugs — this one’s for you.

Summary

In this conversation, Angel Paredes, an engineering manager at Datadog, shares his journey from being a student with a passion for art to becoming a successful engineer and manager in the tech industry. He discusses the differences between the tech environments in Madrid and Barcelona, his transition to engineering management, and the importance of team dynamics and leadership. Angel also delves into the evolving landscape of engineering roles, the challenges of interviewing in tech, and shares valuable book recommendations for personal and professional growth.

Takeaways

Angel's journey reflects the importance of finding one's passion in engineering.

The tech environments in Madrid and Barcelona have distinct characteristics.

Transitioning to management doesn't mean stopping coding; it's about balancing both.

Effective team management requires understanding individual motivations and challenges.

The future of engineering roles may shift towards product management and AI integration.

Interviews in tech are evolving, moving away from traditional algorithms to more practical assessments.

Cheating in interviews is a growing concern, especially with AI tools.

Cultural fit is crucial, but it should not overshadow technical skills in hiring.

Continuous learning and adaptation are essential in the fast-paced tech industry.

Books on management can provide valuable insights and frameworks for personal growth.

In this kickoff episode of Señors @ Scale, host Neciu Dan sits down with Danilo Velasquez — Staff Engineer at Adevinta and longtime frontend performance obsessive. They unpack the real battles behind Web Vitals, micro frontends, and the growing complexity of modern frontend work.

Danilo shares war stories like:

• Supporting Internet Explorer 6 in production (yes, really)

• Building a homegrown Lighthouse bot to track 100+ pages every 15 minutes

• How Core Web Vitals became the trigger for SEO incidents

• Why platform work is often the highest-leverage role

• When React “won the war” (and why he still prefers Vue)

• How a setTimeout(0) hack saved his team’s performance

It’s a candid, technical, and surprisingly human look at engineering at scale — packed with lessons for frontend leads, staff engineers, and anyone optimizing in the wild.

🎧 Whether you're wrestling with architecture decisions, debugging layout shifts, or mentoring your next hire — this one's for you.