Skip to content
⚡ LIVE From Lizard to Wizard · Wednesday, August 5 · LIMITED SEATS Save my seat →
Episode 3 56 minutes

Pragmatism at Scale – With Tudor Barbu

Key Takeaways from our conversation with Tudor Barbu

Tudor Barbu

Principal Engineer at Logify

In this episode of Señors @ Scale, host Neciu Dan sits down with Tudor Barbu — Principal Engineer at Logify, former Tech Lead at Personio and engineer at Skyscanner and DaVinta — to unpack 20+ years of engineering decisions, debugging scars, and career evolution.

Main Takeaways from my conversation with Tudor:

🧠 Code has no value unless it delivers value.
Tudor shares how he moved from chasing clean architecture to delivering user impact—even if that meant hardcoding entire frontend flows temporarily.

🔧 When layout shifts hurt users, ship the fix—even if it's ugly.
He tells the story of a frontend layout shift issue that would’ve taken weeks to solve “properly.” Instead? They hardcoded the UI, shipped it in 2 days, and kept the abstraction layer ready for the future backend rewrite.

🪲 Octal bugs still happen.
One of his earliest prod bugs? Prefix-padding dates with 0 triggered octal parsing in JavaScript, breaking downstream calculations. It only happened on the 8th or 9th of each month. Debugging that was a nightmare.

📖 Nobody teaches you to read code.
Tudor believes most engineers are taught how to write—but not how to understand legacy code. He interviews with this in mind: giving messy-ish codebases and looking for signal in how candidates adapt.

🤖 Mentoring in the AI era starts with "don't vibe code."
His advice for juniors: reverse-engineer. Don't rely on vibes or autocomplete. Use AI, but understand the shape of the problem. Learn architecture. Learn how systems fit together.

⚙️ Good delegation is a skill.
We talk about how Tudor approaches delegation as a Principal Engineer: how to hand off ownership without micromanaging, and why clear expectations and regular syncs matter more than fancy tooling.

🎤 Also in this episode:

  • Vue vs React hot takes
  • The “compile it in my head” interview disaster
  • A Vim plugin that came back as a fork
  • When a cleaning lady caused a prod outage by unplugging a server

Episode Length: 56 minutes of real talk on engineering growth, technical humility, and practical leadership

🏆 SOLD OUT IN SINGAPORE · ATHENS · LONDON

From Lizard to Wizard

4-hour remote system design intensive.
Chat apps, microfrontends, BFF, SDUI, event-driven, observability.

€299 4-HOUR INTENSIVE
Save your seat →

Spots are vanishing. Don't be the one who waited.

💡 More Recent Takeaways

Monorepos at Scale with Santosh Yadav
Episode 40

Señors @ Scale host Neciu Dan sits down with Santosh Yadav, principal developer advocate at CodeRabbit and one of only around 80 GitHub Stars in the world. Santosh started hating C in 2004, fell for C# by 2008, and turned a year of open source contributions to Angular and NgRx into a stack of community titles — Google Developer Expert, GitHub Star, Nx champion, and Microsoft MVP. As a staff engineer at Celonis he led the move of 20-plus apps to module federation and drove Nx adoption across 30-plus teams when the product grew from four apps to thirty. From the year-long incremental migration off a single deployable unit, to why polyrepos can't give AI tools the context they need, to how Nx's affected graph and build caching tame a 20-million-line monorepo, to running code review for free for open source at CodeRabbit, this is the monorepo conversation grounded in someone who actually shipped one at scale.

Routing at Scale with Nicolas Beaussart-Hatchuel
Episode 39

Señors @ Scale host Dan Neciu sits down with Nicolas Beaussart-Hatchuel, staff engineer at Payfit and one of the maintainers of TanStack Router. Nicolas's path started with C macros to auto-generate his student paper headers and frontend learned by building phishing login pages for practice, took him through an iframe-based AngularJS-to-Angular 2 micro frontend migration at a web radio platform, into open source contributions across NX, ESLint, Vite and Hasura, and finally to maintaining one of the most ambitious routers in the React ecosystem. From why TanStack Router exists, to migrating Payfit's 300-route, 1.5-million-line codebase off React Router v5 using the strangler pattern, to collapsing 25 polyrepos and five different micro frontend strategies into a single modular monolith, this is the routing conversation most engineers never get.

Redux at Scale with Mark Erikson
Episode 38

Señors @ Scale host Neciu Dan sits down with Mark Erikson, maintainer of Redux and senior front-end engineer at Replay.io, where he works on a time-traveling debugger. Mark's path started with a 286 he got at eight years old, ran through a computer science degree, four years teaching English in China, embedded software at Northrop Grumman emulating legacy CPUs in old aircraft, and a chain of projects — GWT, jQuery, Backbone — that led him to React and Redux. From the @deprecated backlash that had people insulting him on the internet, to why the Redux core hasn't meaningfully changed since 2016, to what RTK Query actually solves, the underused listener middleware, building source maps into React's own build pipeline, and how Replay's recordings now hand debugging over to AI agents — this is the Redux conversation grounded in two decades of shipping software.

TanStack Query at Scale with Dominik Dorfmeister
Episode 37

Señors @ Scale host Dan Neciu sits down with Dominik Dorfmeister — better known as TkDodo — the maintainer of TanStack Query and a software engineer at Sentry. Dominik's path started at a technical high school in Vienna, ran through JVM backend work in Java and Scala, and turned to frontend around the introduction of TypeScript. During the pandemic lockdowns in Austria he started answering questions in the TanStack Discord, got addicted to the instant gratification of helping people, and slowly turned that into a blog, a first code contribution six to eight months later, and eventually maintainership of TanStack Query. From tracked queries and the chaotic version-three-to-four rename, to the version-five mistake he still dreads, to ripping 28,000 lines of dead code out of Sentry with Knip and building Sentry's new design system, this is the open source maintenance conversation most developers never get to hear.

📻 Never Miss New Takeaways

Get notified when new episodes drop. Join our community of senior developers learning from real scaling stories.

💬 Share These Takeaways

Share:

Want More Insights Like This?

Subscribe to Señors @ Scale and never miss conversations with senior engineers sharing their scaling stories.