Win a copy of The Java Performance Companion this week in the Performance forum!
    Bookmark Topic Watch Topic
  • New Topic

Design Pattern.... necessary?

 
Richard Teston
Ranch Hand
Posts: 89
  • Mark post as helpful
  • send pies
  • Report post to moderator
I have this program a database manipulation program as good java program do i have to use model view controller design pattern which i separate the GUI part, the data manipulation part, and the that one that control the two parts of the program? My senior colleagues say that it is more confusing to debug than the standard inline style programming where u can see all the part of the program in one class. I'm doing this pattern in all of my program, and they said when they try to to look at my program they have to go to another class to look what that method do.... (data manipulation part) but all the method does is to retrieve data and save data to the database. They are forcing me to use inline style of programming to standardize with them, which i'm not custom of doing, they said the code is not reusable anyway to separate them into this MVC pattern. My questions are... is that so? if the code is not reusable do i have to do it in an inline style? Does java design pattern can be used only for reusable code? Am i right in using design pattern in my code? What are the advantages of design pattern vs inline style programming? Please... please give me more understanding...
 
Frank Carver
Sheriff
Posts: 6920
  • Mark post as helpful
  • send pies
  • Report post to moderator
Please don't post the same message to multiple forums. You obviously read more than one forum, so do the people who might answer your question.
This thread is now closed. All replies to the one in Java in General (intermediate).
 
    Bookmark Topic Watch Topic
  • New Topic