Around ifelse and business logic

ifelse Very important , It is almost the core of programmer programming , Business logic and rules are also passed ifelse reflected , The statement is simple but the article behind it is very big , Let's first look at some humorous pictures ：      

      

1.  Maybe by default return false You can save half the code , The cartoon complained about if else The burden of is long , Hope to simplify it , But it is essential to simplify the business logic , If it is only within the boundaries of the coding category visible to the programmer , Limited role ：

 

2.  Programmers are at different stages if else The cognitive , Programming is using iflese Implement business logic ：

    

          

3. Take another look ​ Humor , Probably because it is too complicated ifelse Lead to Bug A hundred , Last but not least bug Maintain the normal operation of the software system ：

 

The above three humorous pictures illustrate ifelse The status quo of implementing business logic , Solution ：

1.   Business and IT The era of separation is over ？ ： Programmers can't just do solutions , It must also enter the problem area
2. What is a strategically clear challenge map ？ ： Introduce strategic approaches such as products , Solve the fundamental problems of business logic from the perspective of problem domain
3. Product sharing ： What should the product manager do after taking the post ？： Introduce product manager , Specifically address these businesses and IT The strategic issue of integration
4. The side effect is the number one enemy of programming ！ How to peel it off ？-： When programmers implement the business logic code , Need to put if else Represents the separation of business rule strategy and specific execution action tactics , This is also Functional programming A train of thought
5. Rule engine mode .NET Open source project cases ： Further more , according to SOLID Principle introduces rule engine Design patterns , Completely separate strategy and tactics .
6. A complex system is a mental interface ： For more complex systems , Use DDD Domain Driven Design, etc .

All in all ,ifelse A few letters represent the bitter tears of the software industry , Boulevard dissolves in ordinary code , This may be the true meaning of the road to simplicity .