Hi!

Thanks for your question! I excluded the Interpreter because I think it has lost its "pattern" status. The fraction of developers that deal with Interpreter scenarios is tiny. It's really hard to come up with a reasonable example for the Interpreter application as well. Here's the link I like to present when people ask me about the absence of the Interpreter in the book: http://blogs.perl.org/users/jeffrey_kegler/2013/03/the-interpreter-design-pattern.html

Thanks!

Thank you, Manuel!

If you mean the TypeScript version of my refactoring course, I'm afraid it's still unfinished.

Cool! Whenever I see some of you post photos of your prints, I imagine the day when I finally go ahead with the official printed version.

Спасибо вам за отзыв!

Thanks!

Hi!

This is a good one. I'll add it to my todo.

Hi!

"Replace Temp with Query" is often an interim step in larger refactoring efforts aimed at simplifying and improving the design of the code. By replacing temporary variables with queries, you're not only making the code more modular but also preparing it for further refactorings that can significantly enhance its readability and maintainability. In this context, any initial increase in complexity or debugging difficulty is temporary and strategic.

As you progress with further refactorings, such as "Extract Method" or "Inline Method," the overall structure of the code becomes cleaner and more coherent, ultimately simplifying the debugging process. To minimize interim issues, focus on incremental testing and refactoring in small steps, ensuring each change preserves the functionality and improves the codebase's navigability.

Дякую! Виправлю цей косяк із наступним оновленням.