A usecase is an object.

It seems naive, doesn’t it? It seems to be that sort of thing that everyone know, right? Well, get into your code and, please, find the object representing a usecase. You didn’t find it, did you? Object Oriented is far away from being adopted, neither understood.

In these days I’m working on some code developed by one my fellow colleague, who’s absolutely a master in technology: he knows the very everything about each framework, tool and library… such a cool boy to work with! But it lacks OO, he always thinks in term of “how” and never of “what”, and its code is always “code”.

In my opinion, each usecase should be present in form of an object into your code, every system interaction should be present in form of a method exposed by the usecase object, the state of your system is the state of the usecase object. And, yes, this is not enogh, more to come. But start thinking about this, please, before switching to the next framework or tecnique. Please do business logic.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s