Reminds me of the technobabble generator I built for an IRC bot years ago. Seems that it still works:
The developer will pipe the log before they frobnicate the USB. Now we execute the logs and fork the BSOD. Why don't you populate the terminal unless you define the protocol. You just untar the octals lest they undo the ECC RAM. Our only option is to kill -9 the more magic or compile the patch. The developer will convert the tarball before you rebase the virtualization. Let us mask the compilation and then WONTFIX the wetware. Now rebase the ECC RAM or you might have to fix the Layer 4.
I wonder if I should update it with more ML/FP buzzwords.
That works for general decision making. The reason I'm asking for input is that there might be risks or opportunities involved that I haven't fully considered. There are also people here who have more experience interacting with the AI alarmists' target audience and might be able to comment on their experiences or suggest strategies and talking points.