Old Age and Treachery

I just finished rewriting the access checking code for our product so it runs in a somewhat more efficient manner. The good news is that the account input screen actually replots in finite time now when you've got a complex set of access rules set up.

The bad news is that modern programmers tend to forget about efficiency until the system slows to a crawl. (But storing a sorted list and doing a binary chop search is one of those fine old tactics that will beat the crap out of regenerating the list for each query and then doing a linear search.)

Old Age and Treachery

I just finished rewriting the access checking code for our product so it runs in a somewhat more efficient manner. The good news is that the account input screen actually replots in finite time now when you've got a complex set of access rules set up.

The bad news is that modern programmers tend to forget about efficiency until the system slows to a crawl. (But storing a sorted list and doing a binary chop search is one of those fine old tactics that will beat the crap out of regenerating the list for each query and then doing a linear search.)