If you see such an implementation in code during a review, what would you write?

It is difficult to give a precise comment without specific code, but during a review of the implementation, attention should be paid to the following points:

• Readability and maintainability of the code: are variable, method, and class names clear?
• Compliance with SOLID principles and good OOP practices.
• Exception and error handling.
• Efficiency and optimization: are there redundant operations or potential memory leaks?
• Testability: is it easy to cover the code with unit tests?

If the implementation violates any of these aspects, specific issues should be pointed out and improvements suggested. For example, if a method is too long and does many things — recommend breaking it into smaller functions. If magic numbers are used — replace them with constants with clear names.

Example comment:

// The method is too long and complex, I suggest breaking it into several private methods to improve readability.
// Also, consider adding exception handling when working with external resources.