System Design Notes

In system design, “must not” is a sure sign of failure. “Can not” is the thing to aim for.

I am not sure there is any other rule important enough to share a page with this one. Below is an example of the current “best thinking” in this respect. this is how most systems are currently designed. Within its own terms of reference it works.

“What you have to do is create a landscape of incentives that is ruinous for those that attempt to corrupt it. If you don’t do that, you will create an evolutionary arms race in which those who are wishing to corrupt your system for whatever reason are seeking those quadrants where you can’t detect them.”

This idea advocates making the punishment for parasitic behavior, when discovered, severe enough to be off-putting to those who might engage in it. It identifies the problem; that’s good, but surely it’s better to make a system that automatically repels people inclined to behave parasitically or one that they simply aren’t attracted to. Our system should ideally be designed so that there is no advantage in such behavior, and people don’t even need to be detected at all in order to be dissuaded.

The Love Vs Fear page has more on this.