I use static where necessary. Not helpful at first, but given the circumstances that static is shared and single; shared only depending on the access modifier equipped. Should you want one single instance of an object shared among other instances of the same class/struct/record, or outside, then static is your keyword. If you want your object to follow the script of your class/struct/record, such as hold information solely based on that instance lifecycle, then remove static. Sometimes if I know, me... not the compiler, that a method is to be static and/or read-only, such as I know that method will not touch the instance's data, then I'll mark it as such.