I have some but they’re awful. I ususally use mnemonics to cram some list into temporary memory that I don’t want to waste brain cells on actually learning for keeps.
The sillier the better.
Kill Some Easy Chickens, Really Kill Every Chicken!
That one’s for memorizing the order of script-triggering events in FileMaker in which the script runs before the triggering event is allowed to complete.
Developer TMI:
FileMaker Inc. provides certification for its developers. Their tests are not practical tests but instead focus on memorization of product details, some of which are ridiculously arcane and not things you need to have memorized in order to be an efficient developer (i.e., things that, on the rare occasions you need to know them as a developer, are easy enough to look up). One such item is the freaking order of script triggering events.
Addl Developer TMI:
A script can optionally be triggered by any of a variety of events such as a layout loading or a field being exited or a record being committed etc. The developer sets that up. It is possible that a developer would set up multiple competing script triggers, such as one set up to fire on each and every keystroke and, on the same screen, one set up to fire on exit from a specific field, so that when someone tabs to get to the next field both scripts would theoretically fire.
I had a hunch that the developer certification test was going to ask me to specify the order in which competing triggering events would be handled. It’s arcane crap no one needs to know other than to past the cert test. Hence,
Kill Some Easy Chickens Really Kill Every Chicken
= OnObjectKeystroke, OnObjectSave, OnObjectExit, OnRecordCommit, OnRecordRevert, OnLayoutKeystroke, OnModeExit, OnWindowClose.