Elegant Objects: Volume 1

This book is about Object-Oriented programming, but it's (probably) not what you think!There are many books, articles, blogs about OO. Everyone seems to think they know what it is. But this book tries to convince you otherwise. A lot of people will probably have a negative reaction to it just because of the fact that it basically tells them "you've been doing OO wrong the whole time". But I would strongly advise you to read the book and really try to understand what the author is saying.The good parts:* A rather short book without much needless small-talk* Most of the book's ideas are applicable even if you don't adopt the whole philosophy of the book (things like "don't use singletons", "make classes immutable", "keep classes/objects small", etc.)The less good parts:* Some things the author says sound a bit "dramatized"* What author says is not always exactly what he means (for example, "Never use -er names", tells you not to name classes with words that end with "-er" suffix, but what the author is trying to say is something like "A LOT OF class names that end with '-er' are bad because their names imply procedural code wrapped in objects rather than real objects; basically, things like "CashFormatter", "PageLoader", "UserDeleter" or "ImageTransformer" are bad, but things like "User" and "Programmer" are OK).Despite a few flaws, it's still an excellent book.

The book is far too opinionated presenting the authors preferred way of coding as "the one true way", rather than showing why certain patterns can be bad, but might be acceptable for certain sets of tradeoffs.Some of the choices the author prefers might be fine choices for the projects the author has worked on, but are definitely not universally true. Making the argument that anyone that disagrees is an idiot as the book does is not a good way to educate programmers.A much better book is "Timeless Laws of Software Development" https://www.amazon.co.uk/Timeless-Software-Development-Jerry-Fitzpatrick/dp/099933560X/ref=sr_1_1 which explains why/how certain solutions are good at solving certain problems.

Before reading this book, I did not even realize how many OOP anti-patterns I was using.Now that I have read it, I am really eager to apply the principles defined in the book.Problem is that, it is not very easy to change a way of thinking one has had for years.Also it is really hard to "isolate the diseased" when the language you are writing in and the API framework you are using violate the principles defined in the book.Even after reading the book, I would say that I still write code that is not very maintainable, but now I know that I can improve this code.

Elegant objects is a really thought provoking book with some great ideas. The structure is good with nice bite size chapters that are easy consume.The writing style definitely challenges you to consider the suggested approaches to writing pure OO software. I won't say I agree with everything but I feel the strong opinions offered, if taken with a pinch of salt in some chapters, have definitely helped me to think about the design of the systems I write from a new angle.

What an amazing journey across these ~200 pages. I would like start by writing aboutthe quality of the paper and the font from this book. Both are extremely pleasant.This book is not for beginners, you have to write very ugly code first.Only then, you'll fully enjoy this master piece.Each chapter you'll start by: Yep, another rant.And you'll always end as: I just can't believe I write such ugly code.Birth, education, and employment. This is the path to write OOP software.

This is the most influential book about software development I have ever read!It completely changed my approach to designing applications. I strongly encourage you to read it and try out different techniques this book suggests even though you might not agree entirely.

Nice perspective. I like the innovative way the author proposes to look at an object - with a life metaphors. Very good examples, practical examples and many take aways. 95% of the ideas are awesome. 5% are a bit controversial and require additional thought.

What a fantastic book! It really opens your eyes to what true object oriented programming is all about. I would strongly recommend every software developer to read this book. I'm proud to now have this on my bookcase and will be taking it down for reference (and reminding) very frequently.