design patterns - anti-if campaign -
I was recently running against a very interesting site which expresses a very interesting idea - anti-if The campaign you can see here. I believe that complex nested if statement is a complete pain in the back. I am currently on a project which was recently some crazy nested IFs that were correctly scrolled correctly. Corrected issues in two ways - We used the Windows Workflow Foundation to address routing (or workflow) concerns, and we implemented all our business rules. In the process of ILOG rules. NET (recently purchased by IBM)! For the most part, this has been our nested pain ... but I think myself how many people do to correct their pain in such a way that the good people in anti IFCampaign () represent a certain scenario By creating many abstract classes for what was originally covered by Nested IF. I wonder if another way to remove this complexity might be to use a IoC container such as Structured Map that can carry out the various bits of functionality and in any way ... ...