4 ms·
http://www.aosabook.org/en/ http://www.aosabook.org/en/ "Architects look at thousands of buildings during their training, and study critiques of those building
by pessimizer 12y ago
http://www.aosabook.org/en/ http://www.aosabook.org/en/
"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.
"Our goal is to change that. In these two books, the authors of four dozen 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 these books provide unique insights into how they think.
"If you are a junior developer, and want to learn how your more experienced colleagues think, these books are the place to start. If you are an intermediate or senior developer, and want to see how your peers have solved hard design problems, these books can help you too."
edit: a major advantage to aosa is that all the source is available.
- chton 12y agoThis is a great suggestion. Make sure to buy all 3 books. Then, next time you come across an article about any of the techs in the book, spend the time reading how it was built. You'll learn loads.
- lightblade 12y ago^ This I was going to reply about experience (and code review) being the best teacher, but this is better. Critics from your peers are good, but critics from the experts are even better.
- weitzj 12y agoThese are really great books. I stumbled upon them while reading the great article about the Selenium WebDriver http://aosabook.org/en/selenium.html http://aosabook.org/en/selenium.html
- nikhilalmeida 12y agohttps://github.com/aosabook/500lines https://github.com/aosabook/500lines This is a repo of smaller real world applications that are 500 lines or less in length, so as not to be overwhelming to novice / intermediate programmers.
- nikhilalmeida 12y agohttps://github.com/aosabook/500lines https://github.com/aosabook/500lines This is a repo of smaller real world applications that are 500 lines or less in length, so as not to be overwhelming to novice / intermediate programmers.
- bthomas 12y agoI'm curious if anybody has an example of how one of the designs in this book informed one of their own designs. I love the motivation for this book in theory, but started reading it and couldn't identify any explicit benefits to my own code.
- bjitty 12y agoAwesome thanks for the link. I've seen this book / project a while back but completely forgot about it.
- vishnugupta 12y agoOnce in a while I ask my self why do I spend time on HN. All my doubts vanish when I come across gem of suggestions such as this. There's no way I would have stumbled upon this book but for HN. Thank you!
- tmsh 12y agoI think this is great and look forward to reading these books. Lots of familiar names. But I'd say in my oh 10-15 years of programming I've learned that the way to really learn the importance of a pattern is by deriving why it is really needed. You can't really make shortcuts there. The difference with software is that it's soft. We're not actually creating buildings. Yes we ship products so it's related. But it's more on the spectrum towards disciplined writing or math than architecture in the traditional sense. It's actually more to your advantage to learn via practicing with the minimum tools for the job. Anyway, still important to learn others' patterns. But it's less meaningful in terms of how it fits in your mind -- in particular, knowing when to apply them in the future -- than deriving them on your own. And there's less risk in learning via mistakes unlike with building physical things. Software just has faster iterations.
- philrea 12y agoamen
- kenbot 12y agoThere's certainly great value in reading application source code, but it has nothing to do with physical Architecture. I do wish people would let go of this tired and completely wrong metaphor.
- jalfresi 12y agoPersonally, I think the metaphor is quite apt. Obviously it is a metaphor so there isn't a complete mapping, but where do you feel the impedance mismatch is between the traditional architecture metaphor and software architecture? I'm genuinely curious to know, because I have found the metaphor to be strong enough that I read traditional architecture books to help me understand architecture and design in general in software development.
- walshemj 12y agoit's a shockingly bad metaphor for software development. I used to work for a top5 consulting engineer - architects some times just do the very high level design the consulting engineers actually turn this into a practicable design which is then built by the contractors and the navvy's. And I am sure that my dept boss Dr Shair (one of the pioneers of the cable stay bridge design) would consider him self an engineer and not an architect
- kenbot 12y agoThey have almost nothing in common, and it's accidental when they do. For instance: - Designing software in minute detail beforehand is generally neither necessary nor possible. - It is impossible for someone to be a capable software "architect" unless they are an experienced software "builder". - It is impossible for someone to be a capable software "builder" unless they are also capable of designing it. - Software can be reused once built, and this matters while building it. - Software is rarely "finished", but continues to grow over time. - Software can be used by an unbounded number of users at the same time. - Software can be reproduced infinitely. - Software can be forked and incrementally changed. - Anyone can design and build their own software, given some talent and a computer. - The business motivations for software development are fluid, and often change rapidly over the course of a single project. I could go on and on. As with many (most?) metaphors, it offers some superficial familiarity, but is ultimately harmful to your understanding. Software is software. Understand it by reading about software and writing software.