Heimir Thor Sverrisson joins Robby to discuss the importance of software architecture in long-term maintainability. With over four decades in the industry, Heimir has witnessed firsthand how poor architectural decisions can set teams up for failure. He shares his experiences mentoring engineers, tackling technical debt, and solving large-scale performance problems—including one bank’s misguided attempt to fix system slowness by simply adding more CPUs.

Heimir also discusses his work at MojoTech, the value of code reviews in consulting, and his volunteer efforts designing radiation-tolerant software for satellites.

• [00:01:12] Why architecture is the foundation of maintainability – Heimir explains why starting with the wrong architecture dooms software projects.
• [00:02:20] Upfront design vs. agile methodologies – The tension between planning and iterative development.
• [00:03:33] When architecture becomes the problem – How business pivots can render initial designs obsolete.
• [00:05:06] The rising demand for rapid software delivery – Why modern projects have less time for deep architectural planning.
• [00:06:15] Defining technical debt in practical terms – How to clean up code without waiting for permission.
• [00:09:56] The rewrite that never launched – What happens when a company cancels a multi-million-dollar software project.
• [00:12:43] How a major bank tackled system slowness the wrong way – Adding CPUs didn’t solve their performance problems.
• [00:15:00] Performance tuning as an ongoing process – Why fixing one bottleneck only reveals the next.
• [00:22:34] How MojoTech mentors instead of manages – Heimir explains how their consultancy approaches team development.
• [00:27:54] Building software for space – How AMSAT develops radiation-resistant software for satellites.
• [00:32:52] Staying relevant after four decades in tech – The power of curiosity in a constantly changing industry.
• [00:34:26] How AI might (or might not) help maintainable software – Heimir shares his cautious optimism.
• [00:37:14] Non-technical book recommendation – The Man Who Broke Capitalism and its relevance to the tech industry.

• Heimir Thor Sverrisson on LinkedIn
• Heimir’s GitHub
• MojoTech
• AMSAT – Amateur Radio Satellite Organization

• The Man Who Broke Capitalism
• How to Make Things Faster

Jelly is the simplest, most affordable way to deal with your “contact@...” emails.

Tired of sharing an email login, or CCing colleagues to loop them into conversations? Terrified by the dizzying total cost of big-name “customer support” tools? Jelly is the answer. Whether it's for customer support, community organizing, or even managing band emails, Jelly helps your team share an email inbox and manage your conversations in a simple, elegant way. Use the "I got this” feature to communicate responsibility and private comments for internal discussions. Jelly is perfect for small teams — because it was built by a small team. And Jelly is actually affordable —team-based pricing means everyone can pitch in with your team’s conversations with customers, clients, and beyond.

Bonus for Maintainable listeners Get 20% off your first year at letsjelly.com/maintainable.

💡 Enjoyed this episode? Share it with someone who cares about maintainable architecture and technical debt management!

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Not every messy piece of code needs a refactor. Noémi Ványi, Senior Software Engineer at Xata, joins Robby to discuss how to develop the intuition to know when refactoring is truly necessary and when it’s just unnecessary churn. She shares her approach to balancing pragmatism and maintainability, how product teams and developers can work better together, and why developer autonomy is key to sustainable software.

Drawing from her experience working on both open-source and closed-source projects, Noémi reflects on the unique challenges each presents—whether it's dealing with unresponsive GitHub issue reporters, handling unanticipated user behaviors, or navigating large-scale refactors in existing systems. She also shares her philosophy on technical debt: not all of it needs to be paid down, and some of it can actually be strategic.

Robby and Noémi also explore the importance of writing meaningful commit messages, the hidden benefits of reviewing open-source pull requests, and why developers should stop waiting for permission to clean up their codebases.

• [00:01:00] The characteristics of well-maintained software: modular design, good tests, and observability.
• [00:02:00] Open source vs. closed source software: Why communication matters more than you think.
• [00:04:50] Not all technical debt is worth paying down—how to decide when to refactor.
• [00:06:20] Developing engineering intuition: How experience shapes decision-making.
• [00:11:08] Lessons from refactoring a log processing system at Elastic.
• [00:17:09] Strategies for modernizing legacy systems without unnecessary rewrites.
• [00:19:52] Why maintainability is a business requirement, not an afterthought.
• [00:24:03] Should developers ask for permission to clean up code or just do it?
• [00:27:00] The impact of good commit messages and pull request documentation (GitHub PR Templates).
• [00:30:00] Are issue templates in open source a helpful guardrail or a barrier?
• [00:32:00] How to gain autonomy as a developer and advocate for technical improvements.
• [00:39:00] Noémi’s advice: Only fix problems that are actually problems.

• Noémi Ványi’s Website
• Noémi Ványi on GitHub
• Elastic
• GitHub Pull Request Templates
• GitHub

Lost in Thought: The Hidden Pleasures of an Intellectual Life by Zena Hitz

Jelly is the simplest, most affordable way to deal with your “contact@...” emails.

Tired of sharing an email login, or CCing colleagues to loop them into conversations? Terrified by the dizzying total cost of big-name “customer support” tools? Jelly is the answer. Whether it's for customer support, community organizing, or even managing band emails, Jelly helps your team share an email inbox and manage your conversations in a simple, elegant way. Use the "I got this” feature to communicate responsibility and private comments for internal discussions. Jelly is perfect for small teams — because it was built by a small team. And Jelly is actually affordable —team-based pricing means everyone can pitch in with your team’s conversations with customers, clients, and beyond.

Bonus for Maintainable listeners Get 20% off your first year at letsjelly.com/maintainable.

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

How much can legacy code tell us beyond just functionality? Julia López, Senior Software Engineer at Harvest, believes that even small details—such as white spaces, variable names, and formatting choices—can reveal a system’s history.

In this episode, Julia and Robby discuss the importance of refactoring and how a strong engineering culture can make or break a team's ability to maintain and improve software over time. Julia shares her experience leading a multi-year overhaul of Harvest’s billing system, balancing stakeholder expectations while ensuring the rewrite delivered real value.

They explore how refactoring decisions evolve as teams grow, how to mentor newer developers to feel empowered to make changes, and why Julia doesn’t always trust her own estimations (for good reason). She also opens up about the complexities of transitioning a live billing system while supporting customers, finance teams, and engineering operations—all without disrupting payments.

Beyond technical decisions, they also dive into the challenges of communication in remote teams, the value of autonomy in software development, and how teams can make a case for technical debt reduction even when leadership isn’t prioritizing it. If you've ever struggled with refactoring legacy systems or advocating for improvements, this conversation is packed with practical lessons.

• [00:00:22] Meet Julia López – Her background, role at Harvest, and passion for refactoring.
• [00:00:42] What Makes Software Maintainable? – A test suite you can trust and an engineering culture that values refactoring.
• [00:06:31] Leading Harvest’s Billing System Overhaul – Why a full rewrite made more sense than incremental improvements.
• [00:09:54] The Hidden Complexity of Billing Systems – Managing ACH, credit card, and invoice payments.
• [00:14:05] The Fear Factor in Large-Scale Refactoring – Why organizations hesitate and how to push forward.
• [00:18:47] Communication Challenges in Remote Teams – Why documentation and transparency matter beyond GitHub.
• [00:28:30] Finding and Enforcing Engineering Patterns – How teams can encourage consistency in a constantly evolving codebase.
• [00:35:45] Why Autonomy Matters for Developers – Learning through struggle and when to ask for help.
• [00:45:25] Advocating for Refactoring When Leadership Says No – Julia's approach: "Ask for forgiveness, not permission—but estimate higher."

• Harvest – Julia's company
• Radical Candor by Kim Scott
• The Making of a Manager by Julie Zhuo
• Stripe – The payment processor used in Harvest’s billing system
• Git Blame – A tool for understanding code history

• Julia's Website
• LinkedIn
• GitHub
• BlueSky

Jelly is the simplest, most affordable way to deal with your “contact@...” emails.

Tired of sharing an email login, or CCing colleagues to loop them into conversations? Terrified by the dizzying total cost of big-name “customer support” tools? Jelly is the answer. Whether it's for customer support, community organizing, or even managing band emails, Jelly helps your team share an email inbox and manage your conversations in a simple, elegant way. Use the "I got this” feature to communicate responsibility, and private comments for internal discussions. Jelly is perfect for small teams — because it was built by a small team. And, Jelly is actually affordable —team-based pricing means everyone can pitch in with your team’s conversations with customers, clients and beyond.

Bonus for Maintainable listeners Get 20% off your first year at letsjelly.com/maintainable.

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Marty Haught joins Robby to discuss the sustainability of open-source projects, the challenges of maintaining RubyGems, and why the metaphor of technical debt may not fully capture how software ages. Instead, he suggests thinking of it as drift—the natural misalignment of software with its evolving purpose over time.

They also dig into security challenges in package management, including how Ruby Central worked with Trail of Bits to audit RubyGems. Marty also shares insights on the EU Cyber Resilience Act and how it might affect open-source maintainers worldwide. Finally, they explore how companies can support open-source sustainability through corporate sponsorships and individual contributions.

• [00:01:00] The two pillars of maintainable software: good tests and readability.
• [00:02:40] From Perl to Ruby: How readability changed Marty's approach to programming.
• [00:07:20] Is technical debt the right metaphor? Why "drift" might be a better fit.
• [00:11:00] What does it take to maintain RubyGems? Marty's role at Ruby Central.
• [00:14:00] Security in package management: How RubyGems handles vulnerabilities.
• [00:16:40] The role of external audits: Partnering with Trail of Bits for security improvements.
• [00:20:40] EU Cyber Resilience Act: How new regulations might affect open-source projects.
• [00:34:00] Funding open source: Why corporate sponsorships are becoming essential.
• [00:38:20] Processes in distributed teams: Balancing structure with flexibility.
• [00:44:45] Advocating for technical debt work in teams: How to make a compelling case.

• Technical debt is often misunderstood. The real issue may not be shortcuts taken in the past, but the way software naturally drifts from its original purpose.
• Security in package management is a growing concern. Open-source ecosystems like RubyGems require continuous investment to remain secure.
• Open source needs sustainable funding. Relying on volunteers is not a long-term solution—companies need to contribute via corporate sponsorships.
• Advocating for code improvements requires strategy. Engineers should frame technical debt discussions around business impact, not just code quality.

• Marty Haught on LinkedIn
• Marty Haught on Twitter
• Ruby Central
• RubyGems
• Auditing the Ruby Ecosystem’s Central Package Repository – Trail of Bits
• EU Cyber Resilience Act Overview
• What the EU's New Software Legislation Means for Developers (GitHub Blog)
• Ruby Central Open Source Program – Get Involved
• Corporate Sponsors Program
• Give and Take by Adam Grant

• LinkedIn
• Twitter
• BlueSky

Jelly is the simplest, most affordable way to deal with your “contact@...” emails.

Tired of sharing an email login, or CCing colleagues to loop them into conversations? Terrified by the dizzying total cost of big-name “customer support” tools? Jelly is the answer. Whether it's for customer support, community organizing, or even managing band emails, Jelly helps your team share an email inbox and manage your conversations in a simple, elegant way. Use the "I got this” feature to communicate responsibility, and private comments for internal discussions. Jelly is perfect for small teams — because it was built by a small team. And, Jelly is actually affordable —team-based pricing means everyone can pitch in with your team’s conversations with customers, clients and beyond.

Bonus for Maintainable listeners Get 20% off your first year at letsjelly.com/maintainable.

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Mike Bowers, Chief Architect at FairCom, has spent decades navigating the evolution of database technology. In this conversation, he and Robby explore the challenges of maintaining a 40+ year-old codebase, balancing legacy constraints with forward-thinking design, and the realities of technical debt.

Mike shares how FairCom transitioned from ISAM-based databases to modern JSON-driven APIs, the trade-offs between strict schemas and flexible document stores, and how software architecture plays a critical role in long-term maintainability. He also explains why human-readable JSON simplifies debugging, how documentation-driven development improves API usability, and why many software teams struggle with refactoring at the right time.

• [00:05:32] The role of software architecture in long-term maintainability
• [00:10:45] Why FairCom's legacy ISAM technology still matters today
• [00:14:20] Transitioning to a JSON-based API for modern developers
• [00:19:40] The challenges of maintaining 40+ years of C code
• [00:24:10] Technical debt: What it really means and how to manage it
• [00:28:50] The trade-offs between strict schemas and flexible NoSQL approaches
• [00:34:00] When to refactor vs. when to start over from scratch
• [00:38:15] The influence of product management thinking on software architecture
• [00:42:30] Advice for engineers considering a shift into architecture roles

• FairCom
• Mike Bowers on LinkedIn
• FairCom on Twitter/X

The Influential Product Manager by MSc Bucero

Need a smoother way to share your team's inbox? Jelly’s got you covered! 🍇✨

Jelly is perfect for small teams — because it was built by a small team. If you struggle with keeping your team’s knowledge organized and accessible, check out Jelly, a lightweight knowledge management tool designed to make finding answers easy—without all the clutter of traditional wikis. No more sticky situations or knowledge gaps—Jelly keeps everything smooth, and shareable.

Bonus for Maintainable listeners Get 20% off your first year at letsjelly.com/maintainable,

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Join Robby as he chats with Lorna Mitchell, open source advocate and technical writer, about the art of creating documentation that doesn’t gather dust. Lorna shares her experiences as a maintainer of the open source project RST2PDF, the value of API governance, and how documentation bridges gaps in developer experience.

• What Makes Software Maintainable: Characteristics like great documentation, automated tests, and onboarding ease.
• Documentation's Role in Long-Lived Software: Why it’s crucial for internal tools and open source projects alike.
• Open Source in Practice: Lorna’s journey with RST2PDF and adopting a tech stack she wasn’t initially fluent in.
• API Governance Simplified: Lorna explains the four levels of API readiness and how teams can work toward more usable APIs.
• Writing Documentation for Engineers: How style guides can empower contributors without overwhelming them.
• Using Tools to Improve Documentation: From linters to prose-checking tools like Veil, Lorna discusses practical tips.

• [00:01:00] What makes software well-maintained: documentation, accessibility, and automated tests.
• [00:03:10] Why documentation isn’t just for new users—Lorna’s experience with revisiting her own open source projects.
• [00:06:30] Diving into rst2pdf: Challenges in maintaining an abandoned project.
• [00:13:45] Balancing ownership and transitioning open source projects to new maintainers.
• [00:15:30] What is OpenAPI, and how does API governance impact usability?
• [00:26:10] The art of concise yet helpful documentation for different audiences.
• [00:33:00] Using examples in APIs to enhance clarity and reduce confusion.
• [00:40:00] Tools for improving writing, from prose linters to markdown syntax checkers.

• Lorna Mitchell’s Website
• rst2pdf Project
• Simon Willison’s Post on One-Person Projects
• How to Take Smart Notes
• OpenAPI Specification
• Veil Prose Linter

Follow Lorna:

• GitHub
• IndieWeb

Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.

It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.

Keep your coding cool and error-free, one line at a time! 

Use the code maintainable to get a 10% discount for your first year. Check them out!

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

In this episode of Maintainable, Robby sits down with Carola Lilienthal, Software Architect and Managing Director at WPS. Together, they explore the intersection of cognitive science and software architecture, strategies for tackling technical debt, and why simplicity, modularity, and domain knowledge are crucial for maintainability.

Carola shares her approach to improving legacy systems, fostering domain-driven development, and introducing sustainable patterns into software design. She also discusses the Modularity Maturity Index (MMI), a tool her team has used to assess and improve over 300 systems.

• [00:00:43] What makes software maintainable?
• [00:01:24] The importance of clear structure, modularity, and simplicity in software.
• [00:02:38] How patterns help reduce complexity and onboard developers faster.
• [00:04:42] Addressing the challenges of systems with mixed architectural patterns.
• [00:06:20] Strategies for fostering creativity while maintaining simplicity.
• [00:07:05] How to guide teams to balance technical experimentation and maintainability.
• [00:14:03] Practical techniques for documenting architecture and decisions.
• [00:16:17] What is the Modularity Maturity Index (MMI), and how does it measure system health?
• [00:18:02] Common mistakes in managing technical debt and how to avoid them.
• [00:21:20] Why domain knowledge is essential for innovation and problem-solving.
• [00:33:03] Evolving legacy systems with domain-driven design and transformation.

• Modularity matters: Simplified, modular systems with high cohesion and loose coupling reduce cognitive load and technical debt.
• Patterns as a shared language: Establishing a pattern language within your team creates consistency and eases onboarding.
• Cognitive science in software: Architecture aligned with how our brains process complexity results in more maintainable systems.
• Domain knowledge drives innovation: Teams should focus their creativity on solving domain-specific problems, not over-complicating the architecture.
• The value of architecture documentation: Keeping clear decision records helps teams navigate legacy code and onboard new developers.

• Carola’s LinkedIn
• WPS Website

• Sustainable Software Architecture
• Domain-Driven Transformation (English version coming soon)
• Modularity Maturity Index Overview

• Reinventing Organizations by Frédéric Laloux
• Team Topologies by Matthew Skelton and Manuel Pais

Be sure to follow Carola on LinkedIn and X.

Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.

It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.

Keep your coding cool and error-free, one line at a time! 

Use the code maintainable to get a 10% discount for your first year. Check them out!

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

• The importance of changeability as a core characteristic of well-maintained software.
• How GitHub has approached accessibility as a business and legal imperative.
• The evolution of GitHub’s frontend system, spanning over 2,000 pages, and the concept of "frontend vintages."
• Primer: GitHub’s design system and the paradox of its success—consistency vs. changeability.
• The disproportionate maintenance costs of frontend systems compared to backend systems.
• Using tools like Axe and keyboard-only tests to identify and resolve accessibility issues.
• The philosophical balance between creativity and usability in software design.
• Practical advice for teams starting their accessibility journey with limited resources.
• How frontend complexity affects scalability, especially in app-like experiences.
• Joel’s advocacy for adopting off-the-shelf components to reduce complexity for smaller teams.

Joel explains how changeability—the confidence to make and deploy changes—provides the foundation for high-quality software.

The Microsoft acquisition drove GitHub’s investment in accessibility, introducing SLAs, automated tools, and manual processes to track progress.

Primer fosters consistency but introduces the challenge of making changes across a vast, interconnected system.

Joel shares how browser quirks, device diversity, and other variables make frontend maintenance far more expensive than backend systems.

Joel recommends focusing on key user workflows like signing up, making payments, and completing core tasks. He emphasizes the importance of tools like Axe and keyboard-driven tests.

• [00:01:12] What Makes Software Well-Maintained? Joel shares how changeability drives quality.
• [00:03:05] GitHub’s Accessibility Journey: The role of SLAs, audits, and automation.
• [00:08:49] Primer and Design Systems: Balancing consistency with innovation.
• [00:12:54] The Hidden Costs of Frontend Complexity: Lessons learned at GitHub.
• [00:20:33] Balancing Creativity with Usability: Joel reflects on the intersection of design and functionality.
• [00:28:05] Accessibility Best Practices: Where teams should focus their initial efforts.

• Joel Hawksley’s Website
• Primer Design System
• Axe Accessibility Tools
• GitHub’s ViewComponent Framework

• How Buildings Learn by Stewart Brand

• Joel Hawksley on GitHub
• Joel Hawksley’s Website

Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.

It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.

Keep your coding cool and error-free, one line at a time! 

Use the code maintainable to get a 10% discount for your first year. Check them out!

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Austin Story, Senior Engineering Director at Doximity, joins Robby to explore the intricacies of building maintainable systems, fostering team accountability, and enabling faster iteration without sacrificing quality. Austin shares how his team approached migrating from a monolithic GraphQL architecture to a federated model, why simplicity matters for long-term success, and how guiding principles like YAGNI influence his decision-making.

Doximity is a leading digital platform for medical professionals, and their technology blog offers deep dives into the systems and tools that power their innovative solutions.

• [00:00:41] What is maintainable software? Austin highlights key traits, including testability, simplicity, and ease of removal.
• [00:02:09] Designing for removability: Why it's important and how it enables iterative progress.
• [00:03:05] YAGNI (You Aren’t Gonna Need It): How this principle shapes Austin's approach to feature development.
• [00:04:13] Migrating to GraphQL Federation: Benefits of breaking up a monolithic GraphQL server and the challenges faced during the transition.
• [00:05:56] GraphQL vs. REST: How GraphQL aids developer productivity while maintaining backward compatibility.
• [00:10:53] Collaboration between data and application teams: Using tools like Kafka to bridge gaps and improve workflow.
• [00:17:00] Upgrading Ruby on Rails applications: Balancing autonomy with central guidance for seamless updates.
• [00:27:55] Fostering ownership on teams: The cultural practices that empower engineers to take initiative and drive results.
• [00:34:29] Prioritizing work effectively: How Austin's team uses quarterly planning and measurable "goalposts" to align efforts with impact.
• [00:40:00] Avoiding bike-shedding: Keeping meetings and reviews focused on meaningful progress.

• Simplicity Wins: Maintainable software is easier to adapt, remove, and iterate on when it's kept simple.
• Iterate and Refine: Use principles like YAGNI to avoid over-engineering and ensure systems are built to evolve.
• Collaboration Drives Success: Bridging communication between specialized teams can unlock untapped potential.
• Focus on Outcomes: Define clear goals and track measurable results to ensure projects align with business needs.

• YAGNI (You Aren’t Gonna Need It)
• GraphQL Federation Overview
• Doximity Technology Blog
• The Mom Test by Rob Fitzpatrick
• Austin Story on LinkedIn
• Austin Story's Website

Follow Austin:

• LinkedIn
• Website

Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.

It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.

Keep your coding cool and error-free, one line at a time! 

Use the code maintainable to get a 10% discount for your first year. Check them out!

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Characteristics of Maintainable Software
Dan emphasizes the importance of internal consistency in codebases, automated tests, and proper documentation to preserve decision-making context.

• [00:05:32] Internal consistency: Why it matters.
• [00:08:09] Lessons from maintaining legacy codebases.

Working with Legacy Systems
Dan shares stories of upgrading ORM frameworks, introducing caching systems, and transitioning to bug tracking tools.

• [00:09:52] Replacing custom ORM systems with Hibernate and Ehcache.
• [00:13:10] Tackling high-risk components with automated testing.

Modern Authentication Challenges
As part of FusionAuth, Dan discusses building developer-friendly tools that balance local flexibility with SaaS convenience.

• [00:21:05] FusionAuth’s role in secure authentication.
• [00:28:13] Testing authentication flows locally and in CI pipelines.

Navigating Constraints in Teams
Advice for managing technical debt, advocating for team priorities, and communicating with stakeholders during lean times.

• [00:16:39] Communicating the impact of resource constraints.
• [00:19:27] Tracing single requests to understand complex systems.

Industry Trends and AI's Role
From managed services to the impact of AI on coding languages, Dan reflects on how the industry continues to evolve.

• [00:35:05] Managed services as accelerators for maintainability.
• [00:41:25] The potential and limits of AI in software development.

• Consistency and documentation in codebases reduce cognitive overhead for developers.
• Understand how your software fits into the business to prioritize effectively.
• AI might reshape the industry, but it won’t replace the need for thoughtful problem-solving.
• Opinionated frameworks like Ruby on Rails continue to offer exceptional developer ergonomics.

• FusionAuth Blog
• Dan's Personal Blog
• CIAM Weekly Newsletter
• Dan’s Book: Letters to a New Developer
• Zen and the Art of Motorcycle Maintenance
• The Asimov story mentioned

• Download FusionAuth: Get started with the self-hosted version today.
• Free Trial of FusionAuth: Experience the FusionAuth cloud for free!

• LinkedIn
• BlueSky

Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.

It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.

Keep your coding cool and error-free, one line at a time! 

Use the code maintainable to get a 10% discount for your first year. Check them out!

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.