Elegant Objects

This book showed me that I didn't understand OOP very well. Now I do. I would advice to read it with open mind, don't let your ego to get on the way. Mistreatment of those poor objects must come to an end.

Great book about Object-oriented programming. And not even object-oriented programming in particular, some sections about naming and NULL-s for example are applicable to other programming paradigms also.The author is a practicing programmer who writes a lot of code every day. And the book contains a lot of examples which are small and simplified of course but very useful to better understand the idea and how to implement it in code. I would recommend the author to pick one of his projects for his future books and explain all the principles using examples from that only particular project (simplified ones of course). To my mind that will make examples more consistent across the book.I found grouping into chapters a little bit weird but still every section is more or less independent from each other. One could start reading almost from any section of the book.So in conclusion: Great book which every Java programmer at least should read definitelly.The book is expensive but worth buying.

The main problems, at the current state of Java, it is possible to apply some of the principals but not all at once. Therefore, some of the suggestions become unpractical. Another problem that comes from the library vendors it is not always possible, especially in the production code ignore null paradigm and static objects. Also, when enterprise code is huge and becomes legacy code create each time new object may be costly and fail safe approach may not be avoidable. I am not saying that the all above is good and should be as it is BUT my main concern you cannot apply all these principals at once and even if you do, you would be in much bigger troubles as before because you automatically becomes the opposition of all existing practices in the industry for years. Also, as mentioned by some of the reviewers. Examples are not apply principles from the previous chapters, so when Yegor takes code, it always bad and never tuned with suggestions from previous chapters. It creates certain feeling of contradiction, it is not always bad, it is just how it is.Concrete points I disagree with:- Lazy evaluation using ctors is always good (I imagine many scenarios when without applying other principles from the book, this paradigm will put the knife into the develops back)- Chain exceptions but not log them (Logging is a very powerful technique and with large application you cannot recover on few points, sometimes you need notify customers, business that something went wrong and also do retrospective when failure was missed or was of less priority)- Functional programming is a bad design and not wise ides to use among OOP code (I will not any arguments to this, it is up to each individual to decide either use FP or not. My opinion it creates immutable objects that is good and comes along with ideas from the book and it reduces amount of boilerplate code has to be written, sometimes remove need of utilities)Point I like:- The style of book is awesome, I really like it- It is both easy to read and understand- If I disagree with some points, this book is still triggers some points into my head to ponder deeper about some concepts, approaches, etc.- There are many more my stars just say after meI recommend this book people who just started learning OOP or mostly for those who are professionals and disagree, dissatisfied with the state of the industry and what to revisit some of the old concepts and look on them from different angle.

Tout comme Clean Code de Robert C. Martin, ce livre m'a remué dans mes habitudes de développeur.L'auteur montre à travers le livre ce que l'on doit faire en programmation objet, et que ce qui est fait en général est du procédural. L'idée qui est le fil conducteur du livre est de rendre le code plus maintenable. Et cela est notre but à tous, notre devoir même. Ce livre apporte sa pierre à l'édifice de façon claire, concise. Jetez un oeil à la table des matières, et si vous avez encore un doute, allez sur le site de l'auteur.Un pavé dans la mare que je recommande à tous, si vous savez mettre votre ego de côté.

Poquísimos libros sobre desarrollo de software son tan amenos y fáciles de leer. Ayuda a entender de verdad el porqué de la orientación a objetos