What are some good books for learning about software design/architechure? [closed]

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 12 years ago.

Not a book that talks about how to code but more high level organ开发者_如何学Pythonization of software.

---

General Responsibility Assignment Software Principles and Domain Driven Design are in my opinion are the next must have things you should get familiar with after learning to code. API Design is also a good read, especially when you are developing the software that will be used/extended by multiple people.

I am not in favor of learning patterns as it is EASIER to misuse them if the intention is not understood correctly. (Everything seems like a nail if you have a hammer kind of thing). I have nothing against patterns but I have seen it mostly misused by the junior developers thus creating hard to maintain products.

---

My Professor at RWTH recommended these:

Jacobson, I., et al (1992): Object Oriented Software Engineering

Meyer, B. (1997) : Object Oriented Software Construction,2nd edition, Prentice Hall, ISBN 0-136-29155-4

---

Though perhaps it is not strictly architecture-related (although I believe you'll find that most prescriptions of architecture patterns are mere guidelines at best, and far from comprehensive), Steve McConnell's Code Complete is truly required reading. More importantly than teaching you design patterns, it will teach you to be a better programmer so that you can make these kinds of decisions for yourself.

---

I really like Fowler's Design Patterns. Deep stuff, some of it's hard to get through, but yum.