One moment a project can get on an unwanted road is when new business rules pop in. Even more if this happens on a tight deadline. You just throw some innocent if statements, and that’s how hell can unleash…
Later, other rules will be requested by business. Each will have at least one if statement and maybe interactions with some services. Then one day you notice yourself tangled in the code you’d prefer to never see.
There are ways to implement these rules fast and efficient, avoiding most of those undesired if statements. This is my situation:
- I have a Song resource and a User resource
- A Song can be restricted to a User based on multiple conditions
- If a Song is restricted to a User, we have to let them know why, and this can be for reasons like:
- Song is not released yet
- Song was retired by the record company
- User is from a country where we don’t have rights to offer the Song
- User has a plan which doesn’t allow him to play the Song
- and so on
The “what” doesn’t matter, the “how” is the key. And business folks can change their mind any time. They want a new rule fast, or cancel one, or change it. Continue reading Avoiding IF statements for business rules