O Smalltalku i OO

Kilka książek polecanych do nauki OOP z komentarza do http://onsmalltalk.com/objects-should-be-composable

Ramon Leon „...I've learned what I know from books, and reading great code.

I picked up many of the little things by reading a fantastic book by Kent Beck called "Smalltalk Best Practice Patterns", which despite the title, applies to far more than just Smalltalk. It's a must read to understand how to think about everyday programming and what little things simply must be done well to write good readable object oriented code.

Some more favorites were Refactoring, Analysis Patterns, and Enterprise Application Patterns from Martin Fowler. He's an awesome pattern sleuth and a great writer. Anything he writes is worth reading.

Then I read a fantastic book called Streamlined Object Modeling by by Jill Nicola, Mark Mayfield, and Mike Abney that really gets down and dirty about modeling business rules with the simplest possible set of patterns. Samples came in Smalltalk and Java, which had a nasty habit of showing just how ugly and verbose Java and its ilk really are, when stacked up with identical code in Smalltalk.

Domain Driven Design, by Eric Evans is also a great, if not extremely long read. This guy's done some serious thinking about code. His depth is amazing, and quite beyond me, but I still pick it up on occasion and try to grok more and more of his thinking.

I've also learned a great deal simply from reading the sources of Seaside, Magritte, and Scriptaculous. Lukas and Avi are fantastic programmers and I've learned a great deal about how good frameworks are written, from using and extending theirs. There's nothing like using great code, to teach you how to write great code...”

oraz Lionel Barret „The first book about OO should be Meyer's Object-Oriented Software Construction. It is about statically typed world but it is very very good. Quite provocative but the reasoning behind each choice (ex : when to use inheritance vs composition) is always clear and well thought. Design Patterns should come next I suppose and Refactoring third.”, ale w dyskusji padł także argument, że jest to książka trudna dla początkujących.

© Piotr Chamera, 2001–2016