"The best way to learn good code design and architecture is to work
with code someone already wrote (open source, libraries, frameworks,
etc) that uses good design and architecture."
Or having to debug code that someone else wrote that *wasn't* written
well. It's one thing to learn the good practices, but it's quite
another to understand WHY good code is good and bad code is bad.
Sharon M. Foster, JD, MLS
On Wed, Sep 9, 2009 at 12:57 PM, Jonathan Rochkind<[log in to unmask]> wrote:
> I am a big fan of the original Design Patterns book, myself.
> But just reading the book alone won't do as much as reading the book AND
> working with code that is written using the lessons of the book.
> The best way to learn good code design and architecture is to work with code
> someone already wrote (open source, libraries, frameworks, etc) that uses
> good design and architecture.
> Robert Fox wrote:
>> Since this list has librarians, hard core programmers and hybrid librarian
>> programmers on it, this is probably a good place to ask this sort of
>> I'm looking for some book recommendations. I've read a lot of technical
>> books on how to work with specific kinds of technology, read a lot of online
>> technical "how tos" and that has been good as far as it goes. But,
>> technology changes too fast to be wed to one particular programming
>> language, database technology, metadata standard, etc. I'm interested in
>> finding books that speak to the issues of programming methodology, design
>> principles, lessons learned, etc. that transcend any particular programming
>> technology. Are there good books that distill the wisdom and experience of
>> veteran developers and /or communicate best practices for things like design
>> patterns, overall software architecture, learning from mistakes, the
>> developer mindset and such things?
>> Could you recommend perhaps the top three or four books you've read in
>> these areas?
>> Rob Fox
>> Hesburgh Libraries
>> University of Notre Dame