Skip to main content
Software Engineering

Return to Question

Post Closed as "Duplicate" by gnat, user40980, durron597, Arseni Mourzenko, user53019
Tweeted twitter.com/#!/StackProgrammer/status/399295619246067712
added 4 characters in body
Source Link
the_naive
the_naive
  • 143
  • 1
  • 5

I'm taking a course on design patterns in software engineering and here I'm trying to understand the good and the bad way of design relating to "coupling" and "cohesion".

I could not understand the concept described in the following image. enter image description here The example of code shown in the image is ambiguous to me, so I can't quite clearly get what exactly "Ask, don't tell!" approach mean. Could you please explain?

I'm taking a course on design patterns in software engineering and here I'm trying to understand the good and the bad way of design relating to "coupling" and "cohesion".

I could understand the concept described in the following image. enter image description here The example of code shown in the image is ambiguous to me, so I can't quite clearly get what exactly "Ask, don't tell!" approach mean. Could you please explain?

I'm taking a course on design patterns in software engineering and here I'm trying to understand the good and the bad way of design relating to "coupling" and "cohesion".

I could not understand the concept described in the following image. enter image description here The example of code shown in the image is ambiguous to me, so I can't quite clearly get what exactly "Ask, don't tell!" approach mean. Could you please explain?

deleted 52 characters in body
Source Link
gnat
gnat
  • 20.9k
  • 29
  • 115
  • 295

I'm taking a course on pattern designsdesign patterns in software engineering and here I'm trying to understand the good and the bad way of design relating to "coupling" and "cohesion". 

I could understand the concept described in the following image. enter image description here The example of code shown in the image is ambiguous to me, so I can't quite clearly get what exactly "Ask, don't tell!" approach mean!. Could you please get anything outta the image? If yes, please explain!

Thanks?

I'm taking a course on pattern designs in software engineering and here I'm trying to understand the good and the bad way of design relating to "coupling" and "cohesion". I could understand the concept described in the following image. enter image description here The example of code shown in the image is ambiguous to me, so I can't quite clearly get what exactly "Ask, don't tell!" approach mean! Could you please get anything outta the image? If yes, please explain!

Thanks

I'm taking a course on design patterns in software engineering and here I'm trying to understand the good and the bad way of design relating to "coupling" and "cohesion". 

I could understand the concept described in the following image. enter image description here The example of code shown in the image is ambiguous to me, so I can't quite clearly get what exactly "Ask, don't tell!" approach mean. Could you please explain?

Source Link
the_naive
the_naive
  • 143
  • 1
  • 5

Explanation needed, for “Ask, don't tell” approach?

I'm taking a course on pattern designs in software engineering and here I'm trying to understand the good and the bad way of design relating to "coupling" and "cohesion". I could understand the concept described in the following image. enter image description here The example of code shown in the image is ambiguous to me, so I can't quite clearly get what exactly "Ask, don't tell!" approach mean! Could you please get anything outta the image? If yes, please explain!

Thanks