3 ms·
It amazes me that there is so little familiarity with Decision Tables. The greatest effort in software development or documenting processes isn’t coding; it’s t
by fredkline 3y ago
It amazes me that there is so little familiarity with Decision Tables. The greatest effort in software development or documenting processes isn’t coding; it’s the effort of covering every possible combination of circumstances – user input, database transaction, or any other events/rules – that the program/process will encounter. If any combination of inputs/events is overlooked, the program will function randomly, or the business process will be incomplete. Here's a couple of tutorial videos on an AI enabled Decision Table Processor, LogicGem. It shows how to build a table representing your Program Logic or Business Rules and then how it can find any missing, redundant, contradictory or ambiguous rules and then automatically fix them. It then shows how it generates documentation in English, French, Spanish and German and even generates source code of the validated and complete set of rules in 25 different programming languages for inserting in your application. Check them out at https://youtube.com/@logicgem https://youtube.com/@logicgem
- 082349872349872 3y ago> 32. Programmers are not to be measured by their ingenuity and their logic but by the completeness of their case analysis. — AJP
- marcosdumay 3y ago> It amazes me that there is so little familiarity with Decision Tables. They are just another language, overtly verbose, with no opportunity for a clean presentation of your ideas, that convey the exact same information you encode on your code, and isn't any more clear to laypeople than code. That stuff has some utility in a place or another, but if you are really thinking about making people fill one up, you should look into letting those people use a real programing language.
- rramadass 3y agoNot quite so simple. Computer Programming involves a lot of state management, book keeping and various other intricacies which many don't want/learn to do. A person trying to solve his problem should only focus on his problem domain concepts, their relationships and means of expressing them directly. That is why DSLs are a thing. A decision table is such a natural, simple and yet powerful way to model requirements that anybody can learn to do this by themselves.