In the software industry (or any industry for that matter) maintenance makes up much more of the work than writing new software, but I've seen very little written about the subject of becoming good at software maintenance. With the rise of prompt engineering and vibe coding, this work will only increase, and I think real programmers (by real I mean humans, not Scotsmen) skilled at software maintenance will be needed more than ever before.
Many of us have acquired these skills indirectly through the experience of maintaining our own software or software written by others, but I'm not aware of any specific discipline around it. Any two programmers might approach the work in a completely different way, with varying results from project to project.
Software is over a century old, so I'm sure there are known practices that apply well to general problems, but I don't know that anyone has drawn these things up into a tidy volume that can be used to learn, practice and improve these skills other than doing it the hard way (trial-and-error) or learning from other programmers, which will become increasingly rare as more new people to the field spend less time learning from programmers and more time learning from simulations of them.
I'm going to try to set-aside some time to gather-up what I can on the subject, see if there are formalizations that I'm just unaware of (very likely), curate what I can and introspect my own experience and practices as well. I'd like the result to be a concise guide for others who are either new to software maintenance or people with experience who want to make it more fun and less painful (like me!).
I expect, like the book the title of this post refers to, such a resource will be mostly footnotes to the work of others framed into a abstraction that makes learning about the process enticing, as a thorough coverage of a century-old discipline would certainly be more than I could ever commit to completing.