• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Design Patterns: Is the book more conceptual or it example driven?

 
Ranch Hand
Posts: 265
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think I am becoming a design patterns agnostic. I want to believe in them, but am not sure how to get the benefit. I'm finding I re-use techniques I've seen and found useful. These may come from a simplistic example of a design pattern. But at some point, "making pizza" examples only go so far in aiding my understanding of what role the design pattern has in the real world. I've been helped a lot the few times I've seen discussions of- when encountering this problem- these strategies might be helpful for these reasons.

What is the approach of your book? Does agnostic mean higher level concepts, or focusing on problem types? How do you illustrate the use of a design pattern if you are trying to avoid any specific language implementation? Do you contrast different approaches that may be applicable to the same problem?
 
Author
Posts: 44
7
MyEclipse IDE Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Joe,
I know what you mean, thanks for the question.

Your thoughts quite reverberates what I have gone through when I started learning these.

What is the approach of your book?
The approach is like this "I know I require a command pattern here. Give me ten things that I need to do to implement Command pattern for my problem. and don't give me the example of on/off switches please"

Does agnostic mean higher level concepts, or focusing on problem types?
It means "independent of", independent of any examples in explaining the design patterns. It focuses on lower level concepts rather.

How do you illustrate the use of a design pattern if you are trying to avoid any specific language implementation?
Patterns implement does not depend on any specific language features. Absence or presence of various features within a language may complicate or ease the labor of implementation.

Do you contrast different approaches that may be applicable to the same problem?
No.

 
Jon Swanson
Ranch Hand
Posts: 265
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Interesting.

I feel that one problem I have is that I have read about all the patterns, I have a rough idea how to proceed, but find myself unsure which of a small number of patterns might really solve my problem (i.e. make for the cleanest most maintainable code). Do you think your approach has advantages in this situation? This is where I think 'code-heavy' explanations are not giving me what I need.
 
Mainak Biswas
Author
Posts: 44
7
MyEclipse IDE Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Perhaps not, but you would be the best judge here.
I suggest you read the book online and check if that serves your purpose or not. The home page of the book is here.
designpatternsthoughts.blogspot.co.uk

The core advantage of the book is taking the reader through the thought process. If that is what  you are after, you would get ample of it in this book.
 
reply
    Bookmark Topic Watch Topic
  • New Topic