I'm a big fan of his writing, including the "Refactoring" book [1], which has changed my life. So it's a bit sad to read this admission. But I appreciate his honesty. Wondering if this "detached" feeling is attributed to the anxiety he has felt on the speaking side.
Anyway, I hope he keeps writing. It doesn't have to be a great hit like, say "Microsevices" [2]. I believe it can be more personal. I'd like to learn what experienced people like him think about things happening in the software development world.
(Probably I'll even enjoy reading about what he does on his "indulge" time. That's what the fandom is like.)
[1] https://www.amazon.com/Refactoring-Improving-Existing-Addiso...
Design Patterns is also very well known https://www.amazon.com/Design-Patterns-Elements-Reusable-Obj...
https://www.amazon.com/Domain-Driven-Design-Tackling-Complex...
https://www.amazon.com/Clean-Code-Handbook-Software-Craftsma...
https://www.amazon.com/Clean-Architecture-Craftsmans-Softwar...
https://www.amazon.com/Patterns-Enterprise-Application-Archi...
https://www.amazon.com/Refactoring-Improving-Existing-Addiso...
https://www.amazon.com/Code-Complete-Practical-Handbook-Cons...
https://www.amazon.com/Pragmatic-Programmer-Journeyman-Maste...
https://www.amazon.com/Mythical-Man-Month-Software-Engineeri...
And just because it’s asked at every interview.
https://www.amazon.com/Design-Patterns-Object-Oriented-Addis...
I’m focused on AWS these days, but a lot of these principals are universal.
https://d1.awsstatic.com/whitepapers/architecture/AWS_Well-A...
