Please note the title wasn’t my decision; I wanted to call it “faster feedback with formal methods”.
Respectfully, the current/actual title doesn’t make sense to me so thanks for being honest. I really like how you worked with the decision table examples in the article. Are there any examples of tools to make working with decision tables easier?
That’s an interesting question. I always just write them up in a spreadsheet, but now that I think about it having a tool where you could generate the inputs automatically and mark some as redundant would be really helpful, especially as you add and remove variables.
Decision tables seem nice, but I don’t think they scale much. I’m thinking of work, where we have 13 feature bits for an account, so that’s at 8,192 rows. Yes, I know, too much. But it’s legacy code that’s grown over the years.
They don’t scale all that much, true! But it’s usually obvious in the first couple minutes that they won’t scale to your problem, meaning you’ve only lost a couple minutes applying the wrong tool. That’s why I love decision tables: they’re a useful tool with extremely low cost.
We have over 50 feature bits. It’s insane.
You don’t need one row per combination in a decision table though, pretty much always there are redundant combinations that you can communicate with -