Today's guest is Gonçalo Silva, CTO of Doist, the company behind Todoist and Twist.

This interview is an incredible behind the scenes about one of the most peculiar companies in tech.

Because Doist is bootstrapped, profitable, has no office and has about 100 employees that are spread across about 40 countries. Yet, or maybe for this reason, they created one of the world's most beloved productivity tools, used by more than 25 million users and they're up against billion-dollar companies with hundreds of millions of funding.

So how do they pull this off? Let's find out.

(00:00) Preview

(01:15) Introduction

(04:26) What does Doist looks like?

(06:48) The perfect number of people

(09:44) Remote and async-first

(15:59) Asynchronous threats

(18:34) Todoist engineering teams

(21:06) Continuity or chaos

(28:18) A team for every platform

(29:21) Product management

(31:37) Product development process

(34:03) Merging top-down strategies and bottom-up feedbacks

(38:16) AI in product engineering

(46:34) Team level AI practices

—

You can also find this at:

• 📬 Newsletter: https://refactoring.fm

• 🎧 Spotify: https://open.spotify.com/show/7Luds9dmzZDoDC8Q7EMbSw

• 📱 Apple: https://podcasts.apple.com/us/podcast/refactoring-podcast/id1719137305

—

For inquiries about sponsoring the podcast, or appearing as a guest, email: [email protected]

Today's guest is Thiago Ghisi!Thiago is former director of engineering at Nubank and with a long and successful tech career in companies like ThoughtWorks, Apple and more. But right now, he's on a sabbatical and he's been for more than six months.So get ready for an incredible chat where we talked about your identity as an engineering leader, psychology, Claude Code and more.(00:00) Preview(01:01) Introduction(03:25) Quitting the job(10:32) Planning during a sabbatical(14:03) Detaching from your work identity(20:31) Measuring progress(26:03) Finding yourself: Claude Code and second brain(33:34) The biggest revelations(45:22) Thiago's next chapter—You can also find this at:• 📬 Newsletter: https://refactoring.fm• 🎧 Spotify: https://open.spotify.com/show/7Luds9dmzZDoDC8Q7EMbSw• 📱 Apple: https://podcasts.apple.com/us/podcast/refactoring-podcast/id1719137305—For inquiries about sponsoring the podcast, or appearing as a guest, email: [email protected]

Today's guest is Matt McClernan, CEO of Augment Code!

With Matt, we went through the findings of our own research that we developed together with Augment, surveying more than 400 engineering teams about how they're using AI.

And we went through many topics, from the differences between personal and team adoption, challenges, how documentation looks like a secret weapon, how to manage context in AI coding, and much more. And then we talked about the future, how the UX of AI coding is changing with IDEs, CLI tools and agents, and what the future might bring.

(00:00) Preview

(01:26) Introduction

(02:16) Personal vs Team AI Adoption

(09:25) The journey of AI adoption

(13:06) The role of documentation

(18:13) AI and Context: the Augment secret sauce

(25:44) Helping AI with context

(28:17) Quality control in AI coding

(36:30) Companies and AI in the near future

(45:54) The state of UX in writing code

(51:54) The scope of Augment

—

This episode is brought to you by Snyk! Join a live session with Vandana Verma Sehgal, OWASP Leader and Staff Developer Advocate at Snyk, on Thursday, December 11, at 11am ET

Register at https://go.snyk.io/12-11-owasp-top-10-isc2.html?utm_source=newsletter&utm_medium=so-sp&utm_campaign=dm_im-refactoring_wbn_251211_owasp-top-10&utm_term=refactoring&utm_content=ad&ref=plug.dev

—

You can also find this at:

• 📬 Newsletter: https://refactoring.fm

• 🎧 Spotify: https://open.spotify.com/show/7Luds9dmzZDoDC8Q7EMbSw

• 📱 Apple: https://podcasts.apple.com/us/podcast/refactoring-podcast/id1719137305

—

For inquiries about sponsoring the podcast, or appearing as a guest, email: [email protected]

Today's guest is Rob Zuber, CTO of CircleCI!With Rob, we talked about software delivery, the impact of AI, and how to build great product engineering teams. And next, we discuss trade-offs between standardization versus flexibility in software organizations, and lessons learned from our respective past mistakes.(00:00) Preview(01:22) Introduction(03:33) Industry Changes and AI's Impact on Development(08:59) The Bell Curve of Metrics and Team Performance(12:09) From Engineering Metrics to Business Outcomes(14:31) Building Effective Small Teams(25:35) Experience vs. Curiosity(37:18) Scaling Challenges and Technology Decisions(49:26) Organizational Standards and Leadership Philosophy—This episode is brought to you by Codacy! Codacy helps developers save time in code reviews, so developers can focus on other things.Start your free trial and get 20% off your first 3 months at codacy.com/refactoring—You can also find this at:• 📬 Newsletter: https://refactoring.fm• 🎧 Spotify: https://open.spotify.com/show/7Luds9dmzZDoDC8Q7EMbSw• 📱 Apple: https://podcasts.apple.com/us/podcast/refactoring-podcast/id1719137305—For inquiries about sponsoring the podcast, or appearing as a guest, email: [email protected]

Today's guest is Hywel Carver! Hywel is co-founder and CEO of Skiller Whale, which provides live team coaching for software engineering teams. With Hywel, we got deep into what makes traditional developer training awful, what engineers truly learn and what they should learn. Then we explored how to measure the impact of learning and how AI may possibly change both how learning works and our own skills.(00:00) Preview(01:15) Introduction(02:22) Hywel's journey in tech(06:20) Spreading good learning(07:55) Training as a compliance(09:34) The effectiveness of learning(12:42) Training with an expert(18:02) Knowledge, Skill and Wisdom(24:16) How Skiller Whale works?(30:26) The outcomes(34:53) Finding the proper learning method(40:12) Measuring learning value(46:54) AI, humans and code bases—You can also find this at:• 📬 Newsletter: https://refactoring.fm• 🎧 Spotify: https://open.spotify.com/show/7Luds9dmzZDoDC8Q7EMbSw• 📱 Apple: https://podcasts.apple.com/us/podcast/refactoring-podcast/id1719137305—For inquiries about sponsoring the podcast, or appearing as a guest, email: [email protected]

Today's guest is Darragh Curran! 

Darragh is the CTO of Intercom, which is one of the world's leading customer service products with more than 600 million users.

With Darragh, we talked about how AI poses at the same time an existential risk and an incredible opportunity for Intercom, and how this led them to the decision of creating a completely separate product and deflect most team resources to it. 

Then we discussed how AI is being adopted inside Intercom itself to achieve Darragh's ambitious goal of doubling the team's productivity.

And finally, we explored Darragh's own role as CTO and what he believes he needs to get right to make all of this happen. 

(00:00) Preview

(01:31) Introduction

(02:19) How Intercom changed with AI

(07:02) Intercom and Fin

(11:37) AI productivity gains

(16:36) Measuring productivity increase

(25:06) Experience and AI

(31:02) AI in large and legacy systems

(32:47) The CTO role in an AI framework

(38:56) Good for human = Good for AI

(42:03) Improving AI models: Fin's case

(45:03) How Fin improved so fast

(49:08) One big challenge

—

You can also find this at:

• 📬 Newsletter: https://refactoring.fm

• 🎧 Spotify: https://open.spotify.com/show/7Luds9dmzZDoDC8Q7EMbSw

• 📱 Apple: https://podcasts.apple.com/us/podcast/refactoring-podcast/id1719137305

—

For inquiries about sponsoring the podcast, or appearing as a guest, email: [email protected]

Today's guest is Meg Adams!Meg is Senior Director of Engineering for the New York Times. With Meg, we talked about her fantastic journey in tech, from management in sales and retail, to learning software development from scratch, to management again, but this time in technology. And then we especially talked about Neuro Leadership, what it is, how you can apply it in practice in your team processes, and how things are different for ICs versus managers, and how you scale all of this to your whole organization.(01:22) Introduction(01:38) Meg's journey in tech(06:03) Managing skills in individual contribution(09:32) What is Neuroleadership?(11:06) Neuroleadership in tech(14:12) The SCARF model(21:18) Applying the SCARF(27:29) Designing good communication(30:42) Psychological safety(35:10) Identifying a threat(38:28) Making SCARF model part of a culture(41:27) A good example: Meg's time at Etsy—This episode is brought to you by Augment Code! Augment Code is the only AI engineering platform built for real engineering teams.Learn more at augmentcode.com!—You can also find this at:• 📬 Newsletter: https://refactoring.fm• 🎧 Spotify: https://open.spotify.com/show/7Luds9dmzZDoDC8Q7EMbSw• 📱 Apple: https://podcasts.apple.com/us/podcast/refactoring-podcast/id1719137305—For inquiries about sponsoring the podcast, or appearing as a guest, email: [email protected]

Today's guest is Birgitta Böckeler!

Birgitta is is a distinguished engineer and global lead for AI-assisted software delivery at ThoughtWorks. Her full-time work is to figure out how engineering teams can make the most out of AI.

With Birgitta, we talked about her favorite workflows, how she uses AI in the IDE, in the terminal or in a genetic mode. We discussed AI impact on productivity and what the best teams are getting right, which others are not. And finally, we talked about how AI impacts both junior and senior engineers and how we can get the best out of both skeptics and optimists.

(01:27) Introduction

(04:58) A day in the work of data

(11:04) Large and smalls change sets

(15:57) The strength of Cloud Code

(18:35) Using AI tools in ThoughtWorks

(21:41) Figuring AI productive value

(27:24) Getting the most out of AI

(30:10) AI assistance in large code bases

(32:21) Good for humans = Good for AI

(39:10) AI and documentation

(41:49) Software engineer role in AI landscape

(48:24) Junior engineers and learning

—

This episode is brought to you by Augment Code! Augment Code is the only AI engineering platform built for real engineering teams.

Learn more at augmentcode.com!

—

You can also find this at:

• 📬 Newsletter: https://refactoring.fm

• 🎧 Spotify: https://open.spotify.com/show/7Luds9dmzZDoDC8Q7EMbSw

• 📱 Apple: https://podcasts.apple.com/us/podcast/refactoring-podcast/id1719137305

—

For inquiries about sponsoring the podcast, or appearing as a guest, email: [email protected]

Today's guest is Antonia Scheidel!Antonia is Director of Engineering at Duolingo, where she made the whole career progression, starting as a simple intern 12 years ago. Antonia is an expert at designing good, automated processes for your team. We discuss how to create good automation to avoid people doing glue work, how not to become a bottleneck as a manager, and how to make the team own the process and repair it when needed.(01:25) Introduction(02:02) Antonia's journey into tech(03:34) Antonia's career in Duolingo(06:55) From engineering to management(10:19) Good processing and notes(14:18) Fixing the process and team alignment(18:06) The burden of asking(23:08) Invisible work and visible improvements(27:55) Automation trade-offs(33:14) Responsibilities in estabilished processes(37:24) How to do notifications right(49:09) Automation for the sake of relationships(54:33) The "usual suspects" of management—This episode is brought to you by Augment Code! Augment Code is the only AI engineering platform built for real engineering teams.Learn more at augmentcode.com!—You can also find this at:• 📬 Newsletter: https://refactoring.fm• 🎧 Spotify: https://open.spotify.com/show/7Luds9dmzZDoDC8Q7EMbSw• 📱 Apple: https://podcasts.apple.com/us/podcast/refactoring-podcast/id1719137305—For inquiries about sponsoring the podcast, or appearing as a guest, email: [email protected]

Today's guest is Adam Tornhill! Adam is the author of the popular book Your Code as a Crime Scene, and he's the founder of Code Scene. With Adam, we discussed his unique insights about technical debt and code quality, which come from his study of forensic psychology. We explored how static analysis is not enough to understand code health and why you need to look into version control history to understand hotspots, change distribution and bus factor. And finally, we inevitably talked about AI and how it changes, or maybe does not change, how we should write code.(01:23) Introduction(02:25) Adam's journey into tech(05:58) The crime scene metaphor(08:27) Version control history(10:22) A natural law of software(14:03) Code Red(15:56) Assessing good code health(22:31) Distribution of impact and the bus factor(25:33) Reducing bus factor(29:57) Reassessing knowledge(32:25) The entropy of code bases(34:53) AI in code analysis(39:44) The impact of AI coding(41:58) Preventing technical debt(44:13) The actual developer tool space(46:21) Code data and team ceremonies—This episode is brought to you by Augment Code! Augment Code is the only AI engineering platform built for real engineering teams.Learn more at augmentcode.com!—You can also find this at:• 📬 Newsletter: https://refactoring.fm• 🎧 Spotify: https://open.spotify.com/show/7Luds9dmzZDoDC8Q7EMbSw• 📱 Apple: https://podcasts.apple.com/us/podcast/refactoring-podcast/id1719137305—For inquiries about sponsoring the podcast, or appearing as a guest, email: [email protected]