• 0 Posts
  • 3 Comments
Joined 2 years ago
cake
Cake day: June 29th, 2023

help-circle
  • It’s a risk management strategy where you only do checks afterwards.

    “Trust” means that you don’t make processes wait on passing checks before proceeding, because that would be expensive and/or slow.

    “Verify” means that you have a separate process that comes through and runs checks afterwards, maybe on only some of the things you trusted, to catch issues.

    It’s ideal when you have high-volume and/or low-latency processes where failures are low stakes but you still want to catch systemic issues eventually.

    It’s related to the idea that “the optimal amount of fraud is non-zero”.



  • For the first part, I was like, yeah, that’s pretty much how all C++ GUIs work: a markup file describes the structure, a source file controls the behavior, and a special compiler generates more C++ code based on the markup file to act as glue.

    That’s all pretty standard, and it’s annoying, but I didn’t really get why they were making such a big deal out of it.

    Missing documentation is also annoying but not uncommon for internal widgets.

    What really elevates this from simply annoying to transcendentally bad, is the lack of error messages, the undocumented requirements that resource IDs be sequential, and the mandatory IDE plugin. That’s all unforgivable.