News for hackers. Stuff that matters.
Re:Recombine to avoid naming when naming is hard by PaulHoule on Monday July 06, 2015 @11:19AM (#9839694)
Yeah, I have been looking at why production rules systems (OPS5, Drools, IBM ILOG, etc.) have not caught on and I think one of the problems is that most of these systems make you give every rule a name, which is like saying every line of source code has to have a name.
Re:Recombine to avoid naming when naming is hard by frobaldo on Monday July 06, 2015 @11:39AM (#9839864)
I've spent half a year of my professional life programming custom business rule engine and my experience aligns with a sarcastic note I've read somewhere: "Business builds business rule engines so they can change their rules and workflows without the need for expensive programmers, but in the end they need to hire even more expensive Business Rule Engine Programmers".

Declarativeness of the system was really nice and named rules really made sense, if the actions you can take are really meaningful. It was more like naming every function set while doing FP.

Re:Recombine to avoid naming when naming is hard by braythwayt on Monday July 06, 2015 @11:43AM (#9839900)
I call this "Duck Programming:"

https://unspace.ca/dev/2012/duck-programming