Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, you can read just book about open source project, and authors can show what and how. E.g. I read <a href="http://rads.stackoverflow.com/amzn/click/1590599217" rel="nofollow noreferrer">Pro Spring 2.5</a> and there is even chapter called "Spring Patterns" with explanation of why and how they call files, directories, design patterns they use and invite you to use etc. Probably take a look at the books about open source projects you investigate. </p> <p><strong>UPDATE</strong> (just that paragraph insert to extend answer:) : as I told previously, you can look through the books about open source projects and find there information how this project is developed, architectural issues etc. Once I looked for real good example of "Open/Closed Principle" using, theory is nice but I would not say that it is so clear how to use it. The only book which helped me was <a href="http://books.google.com.ua/books?id=L7d0LNpSrRwC&amp;pg=PA117&amp;lpg=PA117&amp;dq=open+closed+principle+Spring&amp;source=bl&amp;ots=GCf4aZysg3&amp;sig=Dj4Mhjd7v-auoDy9Kf2totqklt4&amp;hl=uk&amp;ei=_RoqTYLuD4Gi8QPJ_bygAg&amp;sa=X&amp;oi=book_result&amp;ct=result&amp;resnum=2&amp;ved=0CCAQ6AEwAQ#v=onepage&amp;q=open%20closed%20principle%20Spring&amp;f=false" rel="nofollow noreferrer">Expert Spring MVC and Web Flow</a> (I already pointed you to google books with that chapter I read). I didn't read the whole book, but I am sure it contains a lot of such things (what and how was used to make Spring done). From book <a href="http://rads.stackoverflow.com/amzn/click/B001GSTOAM" rel="nofollow noreferrer">Clean Code: A Handbook of Agile Software Craftsmanship</a> I remember that there is a chapter, when they take a code from one open source project and make it better (unfortunately open source does not mean that it is good enough); that book also contain reference to how some other projects where written (e.g. jUnit). I don't know any book, which is completely dedicated to any project, there are just books where is "theory", and books about project which can have some explanation of what is inside. I would recommend books from APress (Pro and Expert series, afaik "beginning" books does not contain such explanation), and Packt Publishing - their main topic is open source.</p> <p><strong>UPDATE 2</strong> (just can't stop :) Just remembered new series of books from OReilly "<a href="http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&amp;field-keywords=oreilly+beautiful&amp;x=0&amp;y=0" rel="nofollow noreferrer">Beautiful ....</a>" - I never read it, but I looked through. It actually consists of different stories behind development, real stories from life. I see there is also <a href="http://rads.stackoverflow.com/amzn/click/0596510047" rel="nofollow noreferrer">Beautiful Code: Leading Programmers Explain How They Think</a> - I should contain what you need. Other "beautiful" books can be worth of your time too.</p> <p>About patterns in general there are a lot of good books, and it depends on what exactly are you looking for. E.g. <a href="http://rads.stackoverflow.com/amzn/click/0596007124" rel="nofollow noreferrer">Head First Design Patterns</a> is quite good to explain common patterns in fun way. If you need more, you can take a look at <a href="http://rads.stackoverflow.com/amzn/click/0321200683" rel="nofollow noreferrer">Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions</a> to see how different applications, systems etc. can be integrated (and how open source projects do it too). Etc. Just specify what patterns or tricks do you want to read about, community will make its suggestion ;)</p> <p>Some web links out of my bookmarks:</p> <ol> <li><a href="http://c2.com/cgi/wiki?AntiPatternsCatalog" rel="nofollow noreferrer">Anti Patterns Catalog</a> - know what you are not going to do!</li> <li><a href="http://sourcemaking.com/design_patterns" rel="nofollow noreferrer">Design Patterns</a> and <a href="http://martinfowler.com/eaaCatalog/" rel="nofollow noreferrer">Martin Fowler's Catalog</a> - that's shortly about what is good to use and know about</li> <li><a href="http://www.soapatterns.org/" rel="nofollow noreferrer">SOA patterns</a> - community site for SOA patterns (integration etc.)</li> </ol> <p>And few more books to take a look at:</p> <ol> <li><a href="http://rads.stackoverflow.com/amzn/click/0596008678" rel="nofollow noreferrer">Head First Object-Oriented Analysis and Design</a></li> <li><a href="http://rads.stackoverflow.com/amzn/click/0135974445" rel="nofollow noreferrer">Agile Software Development, Principles, Patterns, and Practices</a></li> <li><a href="http://rads.stackoverflow.com/amzn/click/0735619670" rel="nofollow noreferrer">Code Complete</a> - this book is just a bible of how to write code...</li> </ol> <p>people, who develop open source definitely know what are those books about ;)</p> <p>Hope that helps</p> <p><strong>UPDATE (25-05-2011)</strong> Just found one book, which I definitely going to buy, and I think it perfectly fits your question:</p> <p><strong><a href="http://www.lulu.com/product/paperback/the-architecture-of-open-source-applications/15819207" rel="nofollow noreferrer">The Architecture of Open Source Applications</a></strong><br> <img src="https://i.stack.imgur.com/00sAp.jpg" alt="enter image description here"></p> <blockquote> <p>Architects look at thousands of buildings during their training, and study critiques of those buildings written by masters. In contrast, most software developers only ever get to know a handful of large programs well — usually programs they wrote themselves — and never study the great programs of history. As a result, they repeat one another’s mistakes rather than building on one another’s successes. This book’s goal is to change that. In it, the authors of twenty-five open source applications explain how their software is structured, and why. What are each program's major components? How do they interact? And what did their builders learn during their development? In answering these questions, the contributors to this book provide unique insights into how they think. Electronic versions of The Architecture of Open Source Applications for e-readers will be available for download soon. </p> </blockquote>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload