Re:The Second Edition of “Refactoring”
by darrenhobbs on Saturday December 01, 2018 @06:43PM
(#18579768)
I read the first edition when I was nearly 2 years into my professional career. I understood the basic 'what' and 'how' of software development.
Refactoring helped me start to understand the 'why' and 'when'. Why is design A better than design B? When is it time to tidy up this code? Which choice will be easier to change later? That kind of thing.
Re:The Second Edition of “Refactoring”
by CiaranMcNulty on Saturday December 01, 2018 @04:15PM
(#18578981)
> It seems like the trivial part of refactoring.
Trivial after the book exists, sure
The catalog misses out most of the interesting discussion
I've seen a similar, entire book dedicated to database refactoring that had roughly the same pattern. Chapters named akin to "The Change Table Name Refactor" felt kind of bizarre, when what I was hoping would be contained was advice about refactoring large databases in practice (moving data to new service boundaries, etc). Practical advice on building systems to move data and such seems to be just missing