Earlier quoted context omitted.
So true. It's a fixing the algorithm vs tweaking some parameters situation. PS: if I were to design a state I would make it a part of the constitution that laws must either be written with placeholder variables for any concrete numbers you'd want to put into them or specify only concrete values for those placeholders and nothing else. And no single vote can contain both kinds at once.
rather than simple placeholder variables, we should employ placeholders for smoothly continuous functions over the relevant parameter space. for taxes, the parameter space might include revenue and profit, over which the tax is smoothly continuous. discontinuities just beg to be exploited.
It was in my second or third programming side job when I was asked by the ramshackle finance marketing upstarts I was working for if it was possible to implement the almighty Income Tax Table (in Access, obviously). I had heard scary things about that beast. A few minutes of googling (I think was already Google?) and I realized that the law in question defined a simple linear factor that increases at certain thresholds, with a tax-exmpt base per threshold to correct for any jumps. I was so disappointed! Not so much by a scary mad beast that turned out to be all tame and reasonable but by the professions of finance marketers and tax consultants who routinely acted as if it was some arbitrary monstrosity that could only be dealt with in a lookup table.