This book is a throw back, and fascinating because of it. It's great to see the difference in perspective then compared to that preached by the Agile development community today. It's also interesting to see all the OO features included in Eiffel that none of today's OO language's have. There are clearly things we are doing better today, but others we have lost that we could benefit from. Especially in the areas of better design and more flexible reusable extensible software. And this book has a lot to say about those topics.
This book was written in 1997 and I can't judge it using my current knowledge, which was acquired in the almost 20 years after the book was written. This book was a great book in the past, for people learning OOP/D, hence the 4 stars. Yes, the book definitely shows its age and most things it advocates are not considered good practices today. I would not recommend it for those who understand OOP/D well enough and neither for those who are looking for the current best practices in software design. However, there are still a few hidden gems in there when it comes to software design. I recommend browsing through the book and reading some of the points you may find useful.
This comprehensive guide has been a cornerstone in the evolution of software development, particularly with its clear explanation of object-oriented programming. The newly updated edition expands on crucial topics like concurrency, design patterns, and software quality, which are all highly relevant to cloud based construction software https://www.teknobuilt.com/ . For those looking to enhance modularity, reusability, and efficient memory management in cloud environments, this book offers invaluable insights. Highly recommended for anyone aiming to refine their approach to modern construction software development.
Not bad as for a re-read of 20-years old software development book. Taxonomy around O-O changed a bit. However, it's still worth to scan it quickly for a couple of really good pointers on how to use (vs. abuse) object oriented languages. Other then that, it's just a book that captured really well certain moment in the evolution of IT eco-system, when O-O hype managed to hatch Java ;-)
I accidentally read this in my second year of university because I thought this was required reading. The author has strong opinions about object-oriented programming that he uses to make a new language Eiffel. It's a bit old and stifled by today's standards but has good value in showing all the thought processes and decision that go into language design.
A bit outdated, too much lyrics, *too much* Eiffel language. Author's opinion on some aspects are too restrictive and controversial. Anyway, it's a quite good book on OOP.
The bible of OOD. Not exactly the way things get done, in practice, but the concepts are a good foundation. I read this cover-to-cover, and enjoyed Meyer's style.