Noémi Ványi: Only Fix Problems That Are Actually Problems
Maintainable
Balancing Quick Wins and Code Refactoring in Software Development
This chapter explores the contrasting experiences of small versus large work requests in software development. It emphasizes the significance of quick wins while advocating for a proactive approach to managing technical debt through code refactoring.
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.
Episode Highlights
- [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.
Resources Mentioned
Book Recommendation
Lost in Thought: The Hidden Pleasures of an Intellectual Life by Zena Hitz
🍇Thanks to Our Sponsor!
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:
Or search "Maintainable" wherever you stream your podcasts.
Keep up to date with the Maintainable Podcast by joining the newsletter.
The AI-powered Podcast Player
