One of my favourites is Michael Feather's "Working effectively with legacy code". It is slightly out of date by now, which carries the risk people reading it a

One of my favourites is Michael Feather's "Working effectively with legacy code". It is slightly out of date by now, which carries the risk people reading it and interpreting its advice "literally" (which by definition will take your code back by 15 years). But the main message of the book is as relevant today as then, and a great way to think about writing code and how to approach large complex codebases that need to be tamed.