aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Being able to see solutions Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Being able to see solutions" Watch "Being able to see solutions" New topic
Author

Being able to see solutions

Jean Miles
Ranch Hand

Joined: Aug 20, 2003
Posts: 53
The problem I have is not having the ability to see solutions other than what I have experienced. Even though there are working solutions in form of patterns, it doesn't mean I can understand them enough to use them appriopriately. Do you see reading about Antipatterns is a way to gain a more understanding by looking at what when wrong and how it is resolved?
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
In fact, this is exactly why anti-patterns are needed. Reading a pattern book often doesn't make significant changes in one's work quality -- the most common outcomes seem to be 1) no change at all, and 2) patterns for patterns' sake.
Reading about anti-patterns makes one see better what's wrong. That gives a better incentive to change than just showing a solution (even though the problem is discussed before showing the solution).


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

What is the solution provided by anti-pattern called? Isn't a pattern?


Groovy
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Yes, a solution to an anti-pattern is often a pattern of the same type (design patterns vs architectural patterns, for example). Sometimes the solution could be better described as "common sense"...
Jean Miles
Ranch Hand

Joined: Aug 20, 2003
Posts: 53
Originally posted by Lasse Koskela:
In fact, this is exactly why anti-patterns are needed. Reading a pattern book often doesn't make significant changes in one's work quality -- the most common outcomes seem to be 1) no change at all, and 2) patterns for patterns' sake.
Reading about anti-patterns makes one see better what's wrong. That gives a better incentive to change than just showing a solution (even though the problem is discussed before showing the solution).

I agree with Lasse, I found the reason most people including myself have a difficult time it not easy to see the solution in context of any problems they encounter. Is that why so many people end up doing it wrong because the problem is not completely understood until the code is done? I am told by some problem and model being defined is necessary before any code is written, then there are those that feel coding or hacking at it they will find out what out a clearer understanding of the problem.
Bill Dudney
Author
Ranch Hand

Joined: Sep 05, 2003
Posts: 234
Hi All,
This is a great thread.
Jean perhaps AntiPatterns will help you to see the problems and how to fix them. Another thing that your troubles say to me is that we need to get better at presenting the patterns in the first place. A Pattern needs to be focused so that it can be redily applied to a situation. All to often patterns are way to abstract to be of real use. One of the things that John Crupi (Core J2EE Patterns guy) is trying to do is make patterns and specifically J2EE patterns more accessable in the form of what he calls 'Micro Architectures'. The final section of the second edition has a micro-architecture to integrate workflow into a J2EE app. The approach is almost a cook book, its really worth the read.
Another interesting point is that we often don't really grok some things until we look at it from another vantage point. Thus the value of expierence. If we build a big system we almost always get some things right and some things wrong. If we have and/or take the time to learn from what went well and what didn't we often learn it a lot better.
Best of luck Jean!


TTFN,<br /> <br />-bd-<br /> <br /><a href="http://www.amazon.com/exec/obidos/ASIN/0471449156/qid=1064343733/sr=2-1/ref=sr_2_1/002-8375300-3666449" target="_blank" rel="nofollow">Jakarta Pitfalls</a> | <a href="http://www.amazon.com/exec/obidos/tg/detail/-/0471146153/qid=1064343733/sr=1-2/ref=sr_1_2/002-8375300-3666449?v=glance&s=books" target="_blank" rel="nofollow">J2EE AntiPatterns</a> | <a href="http://www.amazon.com/exec/obidos/tg/detail/-/0471462071/qid=1064343733/sr=1-3/ref=sr_1_3/002-8375300-3666449?v=glance&s=books" target="_blank" rel="nofollow">Mastering JavaServer Faces</a> | <a href="http://bill.dudney.net/roller/page/bill" target="_blank" rel="nofollow">Blog</a> | <a href="http://www.jroller.com/page/BillDudney" target="_blank" rel="nofollow">Eclipse Blog</a> | <a href="http://www.sourcebeat.com/TitleAction.do?id=2" target="_blank" rel="nofollow">Eclipse 3 Live</a>
 
 
subject: Being able to see solutions