Señors at Scale - Software Engineering & Tech Leadership

Dan Neciu
  • 0.0 (0)
  • Technology
  • Updated Weekly

A software engineering podcast for senior developers, staff engineers, and tech leads who build and scale systems in production. Hosted by Neciu Dan, Señors @ Scale features deep, technical conversations with engineering leaders from companies like Google, AWS, Microsoft, Cloudflare, Datadog, and Snyk. Every week, we sit down with Staff Engineers, Principal Engineers, and technical leaders to unpack the real challenges of frontend architecture, micro frontends, React and Vue at scale, design systems, security, reliability, and technical leadership. No fluff, no surface-level takes. Just hard-

  1. Sep 27

    Performance at Scale with Ryan Townsend (Cloudflare) | Black Friday, Edge Caching, Cache Hit Ratios

    You can't optimize what you don't measure. So why do so many teams still guess? In this episode of Señors at Scale, I sit down with Ryan Townsend, Principal Product Manager for Performance at Cloudflare. Ryan has spent 20+ years building for the web and a decade as a CTO. He co-founded Shift Commerce, an enterprise-scale headless SaaS e-commerce platform built on Ruby on Rails that handled billions in yearly revenue. Before that, he was CTO of Matalan Direct, which grew out of one of Shopify's fastest-growing businesses. We talk about why "Rails doesn't scale" was always a myth and how learning Rails in 2005 felt like AI feels today. Ryan also explains how he learned to let go of the code as a leader, using guardrails, weekly demos, and T-shaped engineers. Then we get deep into performance: why real user data beats Lighthouse on your MacBook, how one "no performance impact" personalization script cost seconds at P90, and how Shift hit 99%+ cache hit ratios using inventory tiers and edge personalization. Key Topics: - Why "Rails doesn't scale" was always a myth - Resume-driven development and why startups over-hire CTOs - Why deep experience plus AI is a superpower, and the junior talent pipeline problem - Letting go of the code: guardrails, weekly demos, and async leadership - T-shaped engineers and spreading context across teams - Adopting Scrum properly, training with Jeff Sutherland, and removing impediments - Cutting CI from 40 minutes to 3 - Real user monitoring vs synthetic testing - The render-blocking personalization script that cost seconds at P90 - 99%+ cache hit ratios, inventory tiers, and personalizing cached pages at the edge - Preparing for Black Friday traffic spikes CONNECT WITH RYAN 💼 LinkedIn: https://www.linkedin.com/in/ryantownsend/ 🦋 Bluesky: https://bsky.app/profile/twnsnd.com 🐙 GitHub: https://github.com/ryantownsend 🌐 Website: https://twnsnd.com FOLLOW & SUBSCRIBE 🎙️ Podcast: https://neciudan.dev/senors-at-scale 📬 Newsletter: https://neciudan.dev/subscribe 💼 Dan's LinkedIn: https://www.linkedin.com/in/neciudan 💼 Señors at Scale LinkedIn: https://www.linkedin.com/company/senors-scale/ 📸 Señors at Scale Instagram: https://www.instagram.com/senorsatscale/ 📸 Dan's Instagram: https://www.instagram.com/neciudev ADDITIONAL RESOURCES 📘 The Phoenix Project by Gene Kim, Kevin Behr, and George Spafford ⚡ Cloudflare Speed docs: https://developers.cloudflare.com/speed/ 🐢 Ryan's slowest site in the world (web perf practice repo): https://github.com/ryantownsend/slowest-site-in-the-world #WebPerformance #Cloudflare #RubyOnRails #Ecommerce #CoreWebVitals #EngineeringLeadership #SeniorsAtScale 💬 What's the biggest performance win you've found by actually measuring instead of guessing?

  2. Sep 20

    Design Systems at Scale with Szymon Chudy (Netflix) | Hawkins, Paved Roads, AI Migrations

    What does it take to run a design system that 2,000+ applications depend on, when every team is free to walk away from it? a Software Engineer on Netflix's Hawkins team, which uses the design system In this episode of Señors at Scale, Dan sits down with Szymon Chudy, Software Engineer at Netflix on the Hawkins team, the design system used by thousands of engineers across Netflix's internal tools. Before Netflix, Szymon grew from Senior to Staff Frontend Engineer at Lokalise, where he co-owned the design system and led frontend direction across teams. Before tech, he was a professional guitarist with over a thousand concerts and two platinum albums. Szymon explains why he sees a design system as enablement rather than a component library, why he believes the source of truth lives in code and not in Figma, and how Netflix's "freedom and responsibility" culture forces the Hawkins team to think like a product team that has to earn adoption. We get into the UI paved road, shipping codemods and AI skills with every breaking change, running an alpha, beta and GA release across thousands of apps, and what an on-call incident looks like for a design system. We also talk about when you should not build a design system, what a visual refresh really involves under the hood, and whether the Netflix culture from No Rules Rules holds up from the inside, including informed captains, farming for dissent and the keeper test. Key Topics: - What a design system really is: enablement, not just components - Source of truth: Figma, code, or a separate component definition - Why markdown specs and LLMs don't solve the determinism problem - Hawkins Consumer vs Hawkins Professional at Netflix - Design police vs full freedom, and the case for a paved road in the AI era - Why design systems are slower than product, and why that's a feature - "Legal hacking": letting teams diverge with clear boundaries - Shipping skills, MCPs and context so agents can use your design system - Adoption rate as the success metric - Codemods, AI skills and human in the loop for major migrations - Alpha, beta, GA: releasing breaking changes to thousands of apps - On call for a design system: what counts as an incident - You may not need a design system - Netflix culture: freedom and responsibility, informed captains, the keeper test 🔗 FOLLOW SZYMON 💼 LinkedIn: https://www.linkedin.com/in/szymonchudy/ 🐦 X/Twitter: https://x.com/szymonchudy 🦋 Bluesky: https://bsky.app/profile/chudy.me 🌐 Website: https://chudy.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/senors-scale/ 📚 ADDITIONAL RESOURCES - Szymon's blog: https://chudy.me/blog - Lenny's Podcast with Elizabeth Stone (Netflix CPTO) on systems thinkers: https://www.lennysnewsletter.com/p/netflix-cpto-on-ai-and-the-future - No Rules Rules by Reed Hastings and Erin Meyer - The Culture Map by Erin Meyer - Grokking Web Application Security by Malcolm McDonald - Grokking Algorithms by Aditya Bhargava - The Pelican Brief by John Grisham #DesignSystems #Netflix #Hawkins #Frontend #React #Figma #PlatformEngineering #DeveloperExperience #AIAgents #Codemods #WebDevelopment #SoftwareEngineering #SenorsAtScale

  3. Sep 13

    Agentic Systems at Scale with Vilva Athiban (Omio) | MCP, Orchestration Agents, LLM Cost Optimization

    What does an agentic AI system look like when it has to work 100% of the time for millions of travelers, not just in a demo? Vilva Athiban is Lead AI Engineer at Omio, one of Europe's leading travel platforms. In June 2024, Omio picked him and one other engineer to start an AI team reporting directly to the CEO and CTO. He had no ML background. All he knew was how to call an LLM API. Since then he has built Omio's internal AI platform, the MCP integrations that connect agents to company systems, and Omio.ai, a consumer-facing agent product built entirely on MCP with no agent framework. In this episode Vilva walks through the full evolution of the architecture: LangChain, then LangGraph for control, then no framework at all. He explains the difference between supervisor and orchestration agents, why bigger models turned out cheaper than mini models at scale, how they cap tool calls and cache prompts to control cost, why guardrails ended up with the legal team, and why he thinks loop engineering will die in a few months. We also cover harnesses and context compaction, whether RAG is dead, how to pick models in 2026, fine-tuning, and what a JavaScript engineer should learn to move into AI. Key Topics: - From JavaScript engineer to Lead AI Engineer with no ML background - LangChain vs LangGraph, and why Omio's backend is now 100% MCP - Supervisor agents vs orchestration agents - Bigger models with medium thinking were cheaper than mini models - Capping tool calls, summarizing tool responses, prompt caching - Guardrails are subjective: the whale hunting debate - The agent is only as powerful as the tools you give it - What MCP is and why it replaced RAG for Omio - Harnesses, memory, and context compaction in Claude Code - Loop engineering: a sugar-coated while loop - How to choose models in 2026 (big, mini, nano) - Why fine-tuning is coming back in 2027 - Are developers cooked? The autocomplete that writes 15 files - How JavaScript engineers can become AI engineers - The token bubble, budgets, and the move to open source models CONNECT WITH VILVA 💼 LinkedIn: https://www.linkedin.com/in/vilvaathiban/ 🐦 X: https://x.com/vilvaathibanpb 🐙 GitHub: https://github.com/vilvaathibanpb 🌐 Website: https://www.vilvaathiban.com/ FOLLOW & SUBSCRIBE 🎙️ Podcast: https://neciudan.dev/senors-at-scale 📧 Newsletter: https://neciudan.dev/subscribe 💼 Dan on LinkedIn: https://www.linkedin.com/in/neciudan 💼 Señors at Scale on LinkedIn: https://www.linkedin.com/company/senors-scale/ 📸 Señors at Scale on Instagram: https://www.instagram.com/senorsatscale/ 📸 Dan on Instagram: https://www.instagram.com/neciudev ADDITIONAL RESOURCES - Anthropic Learn: https://www.anthropic.com/learn - Model Context Protocol: https://modelcontextprotocol.io - Omio: https://www.omio.com #AIEngineering #MCP #AgenticAI #LLM #LangChain #LangGraph #SoftwareEngineering #AIAgents 💬 Have you hit the point where a bigger model was cheaper than a mini model in production? Tell me in the comments.

  4. Sep 7

    Decentralized Social Media at Scale with Dan Abramov (Vercel) | AT Protocol, Bluesky, Redux, React

    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.

  5. Aug 1

    Accessibility at Scale with Craig Abbott (TetraLogical) | WCAG, Screen Readers, Design Systems

    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.

  6. Jul 26

    Versatility at Scale with Carmen Huidobro (CTO, Incredible Bee) | 17 Years Freelancing, Automation, Ethical AI

    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.

  7. Jul 19

    CI/CD at Scale with Marko Gaćeša (Semaphore) | Semaphore, Product Engineering, Agent Native

    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.

  8. Jul 12

    AI Harness at Scale with Maxim Salnikov (Microsoft) | GitHub Copilot, Agent Ops, Context Engineering

    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 👇

See All (52)

About

A software engineering podcast for senior developers, staff engineers, and tech leads who build and scale systems in production. Hosted by Neciu Dan, Señors @ Scale features deep, technical conversations with engineering leaders from companies like Google, AWS, Microsoft, Cloudflare, Datadog, and Snyk. Every week, we sit down with Staff Engineers, Principal Engineers, and technical leaders to unpack the real challenges of frontend architecture, micro frontends, React and Vue at scale, design systems, security, reliability, and technical leadership. No fluff, no surface-level takes. Just hard-

Information

You Might Also Like