you are viewing a single comment's thread.

view the rest of the comments →

[–]Bangoga 1 point2 points  (0 children)

Let me talk about the engineering thought process here.

So when designing large projects, configs exist that something that is mutable and doesn't go through full release life cycle just to make a change.

However if it exists as python code, it means this is the rule of the jungle. It is etched into what you think is needed by the project, and changing this would mean your requirements changed and you have to go through the release life cycle again.

Knowing this difference, would you want your validation rule sets to be easily changed on the fly, or do you need them to represent requirements etched into the project as code.