I think maybe "treatable" vs "untreatable/terminal" could be a better metaphor. Both obviously still suck and are expensive and painful and time consuming, but the difference seems signficant
Agreed, I like that. Seems more useful/actionable than 'good' or 'bad'. So can we then say the difference between a rookie and a seasoned developer is just whether they say code is 'unsalvageable' or whether it's 'bad'? We solved it - coming soon to a interview process near you.
