))
The code works. Is refactoring worth it?
Arkiverad serie ("Inaktivt flöde" status)
When?
This feed was archived on October 20, 2024 21:11 (
Why? Inaktivt flöde status. Våra servar kunde inte hämta ett giltigt podcast-flöde under en längre period.
What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.
Manage episode 370969583 series 3412539
Innehåll tillhandahållet av Bennett Garner. Allt poddinnehåll inklusive avsnitt, grafik och podcastbeskrivningar laddas upp och tillhandahålls direkt av Bennett Garner eller deras podcastplattformspartner. Om du tror att någon använder ditt upphovsrättsskyddade verk utan din tillåtelse kan du följa processen som beskrivs här https://sv.player.fm/legal.
I discuss the dilemma of whether or not to refactor code that may not have the best design.
There are always trade-offs involved in leaving messy code versus investing time in making it better designed. It’s not straightforward whether you should undertake a refactor.
Understanding the scope of the refactor is also critical. Your changes can have a big impact on future developers and the overall system. In the video, I provide a set of questions to ask oneself before undertaking a refactor and emphasize the need for collaboration with the team.
Ultimately, the goal is to ensure that refactors drive value and benefit both developers and end users.
10 episoder
Dela
