184 reputation
7
bio website
location
age
visits member for 2 years, 3 months
seen Jul 19 at 11:08

Jul
18
comment Should we avoid using design patterns in constantly changing projects?
@Cornelius Doc Brown said it's hard without concreteness. Requirements going from a word processor to a flight simulator would not be reasonable; no design pattern would help. There's a whole lot of gray area in between his example and, say, adding a new file format to a word processor's Save function (which is very reasonable). Without specifics, it's hard to discuss. Also, it's not that one wouldn't want to change. It's that such changes are difficult, if you already made a design choice early based on a requirement. The word processor vs. flight sim is a great example of early choice.
Jul
18
comment Should we avoid using design patterns in constantly changing projects?
+1, but "or at least better evolvable (that means: easier to be adapted to changing requirements)" -- I'd qualify this with reasonably changing requirements, right?
Jul
18
answered Should we avoid using design patterns in constantly changing projects?
Jul
18
comment Should we avoid using design patterns in constantly changing projects?
The real problem is constantly changing requirements. No design [pattern] is impervious to that!
Jul
11
awarded  Citizen Patrol
Jul
11
comment Is this a good practice or not?
@user140149 Team Geek also has great advice about how to constructively deal with conflicts in teams. Perhaps much harder when the team member is one's boss, but maybe you can start by buying him that book -- after you've read it and found it to be AMAZING ;-)?
Jul
8
comment What is a helper? Is it a design pattern? Is it an algorithm?
Searching Google with keywords helper pattern antipattern reveals a lot of controversy. Not sure it needs asking here.
Apr
24
comment Visitor only applicable when using the Composite pattern?
That seems bad. Why?
Apr
19
answered Relative encapsulation design
Mar
29
answered Model-View-Controller: Does the user interact with the View or with the Controller?
Mar
29
comment Model-View-Controller: Does the user interact with the View or with the Controller?
The reason views exist as an abstraction is so we can substitute them easily when necessary. A controller for an app on various platforms can be the same, but the views have to recognize user gestures differently and translate them into controller operations. I disagree, therefore, that users interact directly with controllers.
Mar
29
comment Model-View-Controller: Does the user interact with the View or with the Controller?
Views recognize user gestures and translate them to controller actions. Think of Siri on the iPhone or the Kinect on the Xbox. Of course, clicking a button in the GUI is a gesture, too, albeit very easy to recognize.
Mar
28
comment Alternatives to inheritance on complex structures?
This would make sense if there is some client method in all the controllers that is similar to operation() in the Decorator pattern. My experience with controllers is limited, but I am not sure this exists.
Mar
28
comment Alternatives to inheritance on complex structures?
Favor composition over inheritance is a design principle.
Mar
25
answered Does the Composite design pattern implement recursive behavior?
Mar
23
awarded  Scholar
Mar
23
accepted Inverse of Extract Interface refactoring
Mar
22
comment How to use the Decorator pattern to add little functionality to big objects?
+1 for stating the cohesion problem (too many responsibilities is 15 methods) and using interfaces.
Mar
22
comment OOP what is meant by object-to-object communication
Check out Pebble for a somewhat complex domain model of a blog system. Not saying it's good or bad, but it might give you some ideas of what behaviors exist in the objects in this domain.
Mar
22
answered OOP what is meant by object-to-object communication