As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I find myself rarely using object oriented principles when I design applications. I am looking for a good reference for Object Oriented design. I'm using C# as my programming language and would like to have a reference which helps to make use of the OO contructs provided by C#. But basically I need a good book to derive some inspiration.
Here goes: two milestones
Design Patterns: Elements of
Reusable Object-Oriented
Software
Head First Design
Patterns
I think a book on Design Patterns may be what you want. The classic one would be Deisgn Patterns: Elements of Reusable Object Orientated Software.
Check out Evan's DDD
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I've heard that using a lot of polymorphism is bad and that it's better code design to avoid polymorphism where ever possible. Is this true?
you probably heard that about Inheritance. The design principle being favor object composition over class inheritance.
No, quite a few design patterns are implemented primarily using polymorphism. The factory pattern is one of the more common patterns that use it.
It is a fundamental part of object oriented programming.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
what is the recommended progression of topics that one should pursue if they are trying to self-learn iOS programming after a solid foundation of the C programming language is established?
How about buying an Objective-C book on amazon.
Object Oriented Design and ObjC Memory Management -- just try porting your C programs to ObjC, learn the APIs (mostly in Foundation.framework) and see how it executes in a sampler. Then make more complex programs of great quality, then move on to UIs and more specialized frameworks you're interested in.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I've been programming with OOP for a year. But I think sometimes, my solutions to the problem, code quality and so on, is not the best as it could be. Are there any good books on writing good and quality OOP code (programming language doesn't matter) for advanced programmers? What would you recommend?
I'm reluctant to suggest a "patterns" book, but Design Patterns is pretty good. It's much more descriptive than proscriptive -- and some of the patterns won't make any sense at all, until you've fought the underlying problem that leads to the patterns -- but if you read the book with the mindset that they are trying to provide a grammar that programmers can use to talk about problems rather than tools that are the Best Possible Solutions, then it is an excellent book.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Is there a branch of computer science that focuses on concepts of OO? There are many books about Object Oriented software development, but they are mostly adopting an engineering perspective.
In the context of a research paper, I'd like to be able to adopt the computer science point of view. In other words, most resources out there seem to be about the craft, not the science behind the craft.
Important books, papers which study OO at a more abstract level would be really useful.
This book appears to be a good starting point: http://www.amazon.com/Foundations-Object-Oriented-Languages-Types-Semantics/dp/026202523X
In case anybody else is looking for the same thing.
Object Oriented Software Construction by Bertrand Meyer is probably the most in-depth study of OO I've come across.
You may like to check AbdelGawad's recent work at Rice University. He builds a mathematical model of mainstream OOP (eg, Java, C#, C++, Scala, X10, etc) called NOOP. Here is a link to his PhD thesis http://scholarship.rice.edu/handle/1911/70199
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
There are various books written for Design Patterns ranging from "Design Patterns: Elements of Reusable Object-Oriented Software" to "Pattern-Oriented Software Architecture Volume 1-4".
But, I did not found any good book which explains Objects Oriented Design, how to design classes, interfaces, etc for large scale and complex systems and make system design as simple as possible through those techniques.
Please share your thoughts about it.
A couple of the most obvious:
Object Oriented Analysis and Design With Applications (Grady Booch)
Object Oriented Software Construction (Bertrand Meyer)
IMHO good OOD is about keeping modules as small, compact and consistent as possible (e.g. the "SOLID" principles). Therefore, good large-scale OOD is "just" a bunch of good small-scale OOD together.
The only thing that really changes in larger scale systems is the importance of getting the smaller scale bits right. Get your abstractions in good order before you get down to actual code.