Elegant objects. Java Edition (Elegant Objects)

Summer. 5 I read this book by Yegor Bugaenko. And I do not recommend reading the entire book for junior and middle developers, because the author lives in his fictional world of pure OOP:) But some sections would be worth reading:) Seniors and architects will be interested in reading if they want to participate in the holy war in absentia as to which OOP is considered sufficiently offensive. In general, some sections of the book are extremely good, while others are extremely doubtful. But in any case, it is rare that any book reminded me of a roller coaster ride and evoked such an emotional response. I'd rename the book the PLO Dogmas from Egor. In this case, the title would be much closer to the content. By the way, the book is composed of the author's notes on his blog - in the end, some of the notes contradict themselves:) Finally, examples of dogma: I recommend encapsulating no more than 4 objects. ...without exception Do not use public constants.

• "If there's less in class" 5 Public policy is acceptable. If there are more, the class needs refactoring. (Another magic number taken from the ceiling.) Do not use static methods. "Never use setters and getters."

#Software #SoftwareDevelopment