Edited
・
Reviews 2
・
Average rating 5.0
Working with legacy code, I always wondered, "Why do we keep piling new code on top of this instead of resolving the technical debt?" However, it was a burdensome situation to step up and say, "I'll fix it," and even when I suggested we do it together, the response was usually, "Considering the cost involved, it's a bit..." I plan to request a legacy cleanup project once more after establishing a concrete plan with a proper approach. I'm walking away with the courage and wisdom (and a 40% super-discounted course) to successfully "clean the restroom." Beyond the talk about legacy code, it was a great opportunity to hear the perspectives of two outstanding developers on the current state of the industry due to the intrusion(?) of AI and the attitude developers should have toward it. Amidst a flood of threatening comments that a developer can't simply ignore—such as "A certain era is coming by when" or "There's no longer a need to write code"—it felt like a reassuring source of support for someone like me, who couldn't stop studying and practicing technology and design while shouting in a corner of my heart, "But they don't *truly* understand it in the real sense."
Hello sp4kid! Thank you so much for taking the time to attend the live session and for writing such a thoughtful review! As you mentioned, having an "approach strategy" is incredibly important when it comes to cleaning up legacy code! The style that works can vary significantly from company to company. I hope you set the stage well and turn this into a successful experience! Additionally, as you go through the legacy lectures, please feel free to post any questions or concerns regarding "legacy cleanup strategies" on the Inflearn community! I am so happy to hear that it felt like a supportive time for you! I will be rooting for all your future challenges! Thank you!




