Articles & Blogs
It's the age old question and Wouter Lagerweij gives his thoughts on when to do which. "If you have a team of people that knows how to attack a legacy system, refactoring will always be the better option. It’s less risky and has less overhead than any type of rewrite. But those skills are unfortunately still quite rare..."
Brian York is the CEO of Bliss, a tool that helps teams pay down tech debt. In this post, he describes why he believes tech debt is a necessary investment for startups and can be paid down as companies mature.
Sarah Allen argues that reducing staff to a skeleton crew for maintenance invites technical debt and has created the negative stigma of legacy code we see today.