The Architecture of Open Source Applications
and over one million other books are available for Amazon Kindle .
Learn more
| |||||||||||||||
 Trade In this Item for up to £10.75
Trade in The Architecture Of Open Source Applications for an Amazon.co.uk gift card of up to £10.75, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
More About the Authors
Discover books, learn about writers, and more.
Product Description
Product Description
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.
Inside This Book
(Learn More)
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items. |
Customer Reviews
There are no customer reviews yet on Amazon.co.uk.
5 star
4 star
3 star
2 star
1 star
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
4 reviews
11 of 11 people found the following review helpful
Incorrect product description
13 Nov 2011
Format:Kindle Edition
The product description states that you will learn "What are each program's major components? How do they interact? And what did their builders learn during their development?" Also, that you will learn how the "software is structured, and why". You will learn how the programs are structured and nothing else. Some of the projects do have a paragraph or two on what the developer would do differently, but some (Asterisk for example is the first chapter) has no discussion at all on anything other than how the code in the project works. It's sort of good to prepare you to look at the code, but the book doesn't actually meet it's stated goals of telling you "why" anything is the way it is.
I would have given 1 star since I feel lied to about what was most important to me, but the discussions on how the projects work are interesting enough to give the book some merit.
IMPORTANT: You can read the entire book for free on the author's site: [...]
I would have given 1 star since I feel lied to about what was most important to me, but the discussions on how the projects work are interesting enough to give the book some merit.
IMPORTANT: You can read the entire book for free on the author's site: [...]
4 of 4 people found the following review helpful
A gem that belongs to every serious developer's library
4 Aug 2011
Format:Paperback
This is not a typical software development book but rather a wonderful collection of essays from the veterans. The editors did a great job by providing such a wide spectrum of programs and authors. From database systems to visualization toolkits, from mail transfer agents to multi-player online games, from continuous integration systems to cutting-edge web applications and then to audio processing systems, you'll find experienced developers talking about the internals of their well-established code bases, used by millions of people and developers worldwide.
Some of the authors have been working on the same system for more than 30 years (e.g. Eric Allman on Sendmail) and it is definitely a pleasure to hear their perspectives spanning such a long time period. Every chapter provides a brief overview of the relevant software and then the authors try to justify the choices they made, sometimes stating their regrets with reasons and sometimes reflecting on how their intuitive decisions turned out to be great strategic advantages in the long run. In some chapters such as the one by Audrey Tang (SocialCalc), you'll learn how it becomes possible to work together for a geographically distributed team of developers and what made Tang's job easy when she joined the team one year after the initiation of project (hint: a well-prepared Wiki becomes much more important than you can imagine).
I think this book belongs to every developer's library to be read and re-read. Time-honored lessons when told by insiders with the help of great editors provide us with an immense value in terms of technology, craftsmanship and community.
Some of the authors have been working on the same system for more than 30 years (e.g. Eric Allman on Sendmail) and it is definitely a pleasure to hear their perspectives spanning such a long time period. Every chapter provides a brief overview of the relevant software and then the authors try to justify the choices they made, sometimes stating their regrets with reasons and sometimes reflecting on how their intuitive decisions turned out to be great strategic advantages in the long run. In some chapters such as the one by Audrey Tang (SocialCalc), you'll learn how it becomes possible to work together for a geographically distributed team of developers and what made Tang's job easy when she joined the team one year after the initiation of project (hint: a well-prepared Wiki becomes much more important than you can imagine).
I think this book belongs to every developer's library to be read and re-read. Time-honored lessons when told by insiders with the help of great editors provide us with an immense value in terms of technology, craftsmanship and community.
1 of 1 people found the following review helpful
Lessons and patterns of Open Source
15 Jan 2012
Format:Paperback
The book covers 25 different open source projects, some of the most notable being: CMake, Eclipse, LLVM, Sendmail and Berkley DB. Each chapter stands on its own and is written by the project lead or one of the lead contributors, while following a loose set of questions such as "how did it start", "what would you do differently", and so on. All in all, a fun an educational read. Some chapters go into the nitty gritty technical details, while others stick to the high-level architectural view.
As intended by the title, I think the most valuable part of this book is simply reading about the history and lessons learned from all of the different projects. The authors don't provide any conclusions, but you can easily spot patterns as you make your way through the book.
As intended by the title, I think the most valuable part of this book is simply reading about the history and lessons learned from all of the different projects. The authors don't provide any conclusions, but you can easily spot patterns as you make your way through the book.
Were these reviews helpful?
Let us know
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
