Agree on the sativa. Back when you had to use a code name if you mentioned it on the phone, I and my friends at Tymshare, Apple, General Magic, Grid, Tandem, etc. called it "programmer's fuel".
Many here are familiar with the term "fire an event". I coined that in the late 1980s when I was at Cooper Software working on a program that would become Visual Basic. (Our team did the "Visual" part, and Microsoft added the "Basic".)
Our system was event-driven just like pretty much any GUI app or system. Under the hood, of course, we used the Win16 SendMessage, PostMessage, GetMessage, and PeekMessage calls.
But we had a habit of using creative names. In fact Alan Cooper once said that "one of my most important programming tools is a thesaurus."
We had already decided to call them "events" instead of "messages" for whatever reason, and now I needed a way to talk about sending them.
At my previous job we had "SQL triggers". I started thinking along that line but wasn't getting anywhere.
So I turned to a trick I often used when I felt stuck: I started firing rubber bands against my computer screen. I kept a stack of them on my desk for just that purpose.
(This was an IBM Monochrome Display with a sturdy glass front. Do not try this on your modern LCD/OLED displays.)
I still wasn't getting anywhere, so I fired up a doobie. I flicked the lighter a few extra times and looked at the flame.
And then it all fell into place: Fire a rubber band. Fire up a doobie. Fire an event!