Skip to Content

Anna Filina: How Every Decision Introduces Technical Debt

EP-001 | April 15, 2019 | 35:32 | Last updated: March 27, 2024

Technical Debt Architecture

Anna Filina

Software Development Consultant, FilinaCo

Specializes in rescuing legacy projects, writing tests for untested code, and training development teams on best practices.

Robby speaks with Anna Filina, a software consultant at Zenika Montreal who specializes in legacy code. They discuss why engineers don't have to ask permission to write tests, why convincing people to get on board with your technical plans matters, and what a "software archaeologist" really does.

Helpful links:

Subscribe to Maintainable on:

Or search "Maintainable" wherever you stream your podcasts.

Join the discussion in the Maintainable Discord Community

Brought to you by the team at Planet Argon.

Frequently Asked Questions

How does Anna Filina view technical debt?

Anna explains that every software decision introduces some form of technical debt. The key is making conscious decisions about which debt to take on and having a plan to manage it over time.

What is Anna Filina's approach to rescuing legacy projects?

Anna specializes in legacy project rescue by first adding tests to understand existing behavior, then refactoring incrementally. She emphasizes that understanding the business context is as important as understanding the code.

How does Anna Filina recommend teams handle untested code?

Anna advocates starting with high-level integration tests to capture existing behavior, then gradually adding unit tests as you refactor. She recommends focusing testing efforts on the parts of the codebase that change most frequently.

🎧 Listen from Anywhere 🪐

Listen on all the major podcast platforms.

Between the episodes

223 Episodes published since 2019

Stay sharp. Skip the noise.

One email when a new episode drops. That's it.

Joined by engineering leaders at companies you've heard of.