HomeGroupsTalkMoreZeitgeist
This site uses cookies to deliver our services, improve performance, for analytics, and (if not signed in) for advertising. By using LibraryThing you acknowledge that you have read and understand our Terms of Service and Privacy Policy. Your use of the site and services is subject to these policies and terms.
Hide this

Results from Google Books

Click on a thumbnail to go to Google Books.

Design Patterns: Elements of Reusable…
Loading...

Design Patterns: Elements of Reusable Object-Oriented Software (original 1994; edition 1994)

by Erich Gamma, Richard Helm, Ralph Johnson, John M. Vlissides

MembersReviewsPopularityAverage ratingMentions
2,892203,360 (4.13)4
Capturing a wealth of experience about the design of object-oriented software, four top-notch designers present a catalog of simple and succinct solutions to commonly occurring design problems. Previously undocumented, these 23 patterns allow designers to create more flexible, elegant, and ultimately reusable designs without having to rediscover the design solutions themselves. The authors begin by describing what patterns are and how they can help you design object-oriented software. They then go on to systematically name, explain, evaluate, and catalog recurring designs in object-oriented systems. With Design Patterns as your guide, you will learn how these important patterns fit into the software development process, and how you can leverage them to solve your own design problems most efficiently. Each pattern describes the circumstances in which it is applicable, when it can be applied in view of other design constraints, and the consequences and trade-offs of using the pattern within a larger design. All patterns are compiled from real systems and are based on real-world examples. Each pattern also includes code that demonstrates how it may be implemented in object-oriented programming languages like C++ or Smalltalk.… (more)
Member:webaugur
Title:Design Patterns: Elements of Reusable Object-Oriented Software
Authors:Erich Gamma
Other authors:Richard Helm, Ralph Johnson, John M. Vlissides
Info:Addison-Wesley Professional (1994), Edition: 1, Hardcover, 416 pages
Collections:Home Library, Your library
Rating:
Tags:Programming Reference

Work details

Design Patterns: Elements of Reusable Object-Oriented Software by Erich Gamma (Author) (1994)

None.

Loading...

Sign up for LibraryThing to find out whether you'll like this book.

No current Talk conversations about this book.

» See also 4 mentions

English (18)  Dutch (1)  Hungarian (1)  All languages (20)
Showing 1-5 of 18 (next | show all)
[I am only going to include 10 tech books, a represtative sample]

Compulsary reading. At the time, (when it first came out) this really affected me. I have always thought that IT is a backwards field, compared to making any other objects, and this is the first step in the right direction. ( )
  GirlMeetsTractor | Mar 22, 2020 |
A classic in the field of computer science, this book describes how object-oriented software can be used to develop meaningful (and reusable) classes. It is written by the so-called "gang of four" affiliated with a working group at the University of Illinois. It has achieved notoriety for its assistance in helping programmers write code more effectively in languages like C , SmallTalk, and (my current language) PHP. The book has started a large movement in identifying design principles that are inherent in all computer science problems.

The book reads like a catalog of class types. After an initial critique on the state of computer programming, it reads like a textbook and a reference manual to be used. It is academic, analytical, and brilliant. Obviously, the book is only for the serious programmer who aspires to master her/his trade. It is not for the casual programmer or even for the intermediate programmer. It does not hold the reader's metaphorical hand as the book is perused. Instead, it provides data and analysis like a research paper. Of course, in such a style, wisdom is distilled into compact sentences.

I'll be happy to put this book on my bookshelf at work and refer to it when designing software. ( )
  scottjpearson | Jan 25, 2020 |
It held my interest, but I find it hard to incorporate what seem like very abstract lessons like these into my actual programming practice. I guess I just don't think in OO. ( )
  Kenoubi | Sep 6, 2014 |
If there were required reading mandated for any degree involving computer software development, this would be it.

Gamma, et al (AKA The Gang of Four) have given us a comprehensive guide to various software patterns, and it's the least we could do to follow them.

It discourages me to see and hear about professional industries making lousy software that can't communicate with other tools, even those made by the same vendor. It bothers me when there are tools out there that make use of a network connection, but apparently don't play nicely with people using other operating systems or even other interfaces. Why can't I play Scrabble on my iPhone with someone using Facebook's Scrabble app? Why can't I play a co-op game of LittleBigPlanet on my PSP with another user playing on a PS3?

Well, the short answer is that you should be able to do these things, using interfacing, one of the fundamental patterns in this book. Just as the user (usually) doesn't care what's going on behind the curtain with their software applications, as long as they get the right feedback when the click the right buttons, the client-side application shouldn't care about what's going on in the server-side, as long as it gets the right feedback from the server when it sends it the right data. When you hear things like this for the first time, it's kind of eye-opening, but at the same time, when you think about it for a minute, it really makes sense. It's like when you're playing a puzzler game, and you need a hint about how to solve a puzzle; once you see the solution, you smack your head. "That's makes so much sense!" you say, "Why didn't I think of that." Well, consider this book the solution guide to software design.

No, it's not a recipe book (like the O'Reilly Cookbook series), but it does provide examples of the patterns you should be using, and unless you describe your coding style as "anarchist," it should really help you.

If you're a software engineer and get your hands dirty by mucking with software, and you haven't yet read this book, then take off those coding gloves and give yourself about a week to absorb the amazing knowledge this book presents. If you want to go into software engineering, ensure that you have a firm grasp of a particular programming language, and then read this book, preferably before you start interviewing for a job. Then, in your interview, when asked a technical question, you can start off your answer by saying, "Well, The Gang of Four said in their book on design patterns..." And then, you're working in some software engineering field (results may vary).

If you're truly devoted to making yourself a better software engineer, though, you simply must read this book. ( )
1 vote aethercowboy | May 26, 2009 |
This book was really a game-changer. The art of creating a computer program had not been analyzed much at all up until that point - plenty of algorithms had been created by computer scientists, and systems designers had some ideas about API's, but there wasn't a whole lot of direction for people who wanted to engineer applications to do things that user wanted them to do. Some of the patterns in the book are in common use today; others have been relegated to the dustbin; but the larger point is that after this book came out, people started using a whole new language to describe the work they were doing. Today we have UI patterns, management patterns, data access patterns, antipatterns, patterns, patterns, patterns everywhere, and this was the book that really caused the concept to take off.

Is it worth reading today? That's a little tougher. There's no question to my mind that every developer should be familiar with the patterns in this book, but a more modern book on the same topic would probably display source code in a language that more people would more commonly be using. Still, there's no question that if you want to go back to the basics, you go back to Gamma. ( )
  benfulton | Feb 10, 2009 |
Showing 1-5 of 18 (next | show all)
no reviews | add a review

» Add other authors (26 possible)

Author nameRoleType of authorWork?Status
Gamma, ErichAuthorprimary authorall editionsconfirmed
Helm, RichardAuthormain authorall editionsconfirmed
Johnson, Ralph E.Authormain authorall editionsconfirmed
Vlissides, John M.Authormain authorall editionsconfirmed
Booch, GradyForewordsecondary authorsome editionsconfirmed
You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Canonical title
Original title
Alternative titles
Original publication date
People/Characters
Important places
Important events
Related movies
Awards and honors
Epigraph
Dedication
First words
Designing object-oriented software is hard, and designing reusable object-oriented software is even harder.
Quotations
Last words
Disambiguation notice
Publisher's editors
Blurbers
Original language
Canonical DDC/MDS
Capturing a wealth of experience about the design of object-oriented software, four top-notch designers present a catalog of simple and succinct solutions to commonly occurring design problems. Previously undocumented, these 23 patterns allow designers to create more flexible, elegant, and ultimately reusable designs without having to rediscover the design solutions themselves. The authors begin by describing what patterns are and how they can help you design object-oriented software. They then go on to systematically name, explain, evaluate, and catalog recurring designs in object-oriented systems. With Design Patterns as your guide, you will learn how these important patterns fit into the software development process, and how you can leverage them to solve your own design problems most efficiently. Each pattern describes the circumstances in which it is applicable, when it can be applied in view of other design constraints, and the consequences and trade-offs of using the pattern within a larger design. All patterns are compiled from real systems and are based on real-world examples. Each pattern also includes code that demonstrates how it may be implemented in object-oriented programming languages like C++ or Smalltalk.

No library descriptions found.

Book description
Haiku summary

Quick Links

Popular covers

Rating

Average: (4.13)
0.5
1 2
1.5 2
2 13
2.5 1
3 86
3.5 13
4 163
4.5 14
5 184

Is this you?

Become a LibraryThing Author.

 

About | Contact | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 150,909,385 books! | Top bar: Always visible