That is actually a very dangerous way to do it because there is no absolute certainty that it works. It is a prime example of a race condition because the LabVIEW code shown assumes that the local variable AAA contains a stale value. It falsely assumes that in
every iteration of the loop, the local variable is read before the AAA terminal is written, an assumption that cannot be guaranteed by the dataflow! It might well be that once in a while (or almost always!) the local variable already contains the current value and you'll get a FALSE even though your trigger condition is met.
It could stop working at any time, e.g. once you add some more code to the loop, recompile the VI, upgrade to a new version, or just by itself, without reason.
😉