Steven Baker 3.45
Software maintenance often gets a bad rap. Many developers look down their noses at “maintenance programmers”, and will shy away from maintaining existing code, preferring green field projects and avoiding the tired old code of their predecessors. When a new person or team looks at existing software, it is not uncommon for the subject of a rewrite to come up. It doesn’t have to be this way.
This talk will focus on practices and experiences that will help prevent software from becoming an unmaintainable mess and enable the development of software that will be a joy to work with long after the final sprint to release. It aims to allow current and future developers to find more joy in working with the existing code base and avoid the expensive and time consuming re-write.