Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
How would you slice out the concerns in this object, and what would you name the resulting objects?
public class Task : ActiveRecord
public string Name { get; set; }
public int AssignedTo_UserId { get; set; }
public DateTime DueOn { get; set; }
public Task()
DueOn = DateTime.Now.AddDays(1);
override void AfterInsert()
Email.Send(AssignedTo_UserId, "New Task", "You have been assigned a new task");
Copy link

kberridge commented Dec 17, 2012

Thanks for the comments!

I would ordinarily balk at the very mention of inheritance and yell "COMPOSITION!" very loudly in your face. But oddly, I'm not completely sickened by what you say. But my concern, which is always my concern when dealing with re-use through inheritance, is what happens when our domain evolves such that we end up in a position of wanting multiple inheritance? That is, we have TaskConcernA : Task, and TaskConcernB : Task and now we want TaskConcernAB : Task. Inheritance is not a flexible way to slice and combine behaviors.

Copy link

ascendantlogic commented Dec 17, 2012

That's when you start writing in Scala and use traits :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment