Humor, jokes, memes about TTRPGs
Image transcription:
I'll start:
Your turn
Hard mode: Try not to include closer to domain-specific things like javascript library names
Bounds execption: Allows larger objects to fit in smaller containers, ritual spell effective for 1 day, can be upcast to increase amount of "overfill", some check when retrieving the item for a chance of "corruption" (small chance to retrieve a different item, or have the "overfill" become something different like have the outer edge of a bar of gold be meat)
Paralellization: High level time magic, Allows the target multiple turns to be taken simultaneously, but an equivalent cooldown afterwards (waiting for all threads or jobs to return before being able to continue), so 3 turns at once means 2 turns the target can't do anything after.
Split brain configuration: Allows focusing on multiple concentration checks/spells at once. This could also be called paralellization, or multithreaded.
Pass By Reference enchantment: requires two identical items. Once enchanted, changes to one happen to both. Room for all sorts of shenanigans.
Private field: cast on an area to prevent entry/visibility into it by unauthorized entities. Sounds inside are not audible to unauthorized entities outside of it.
Lossless Compression isn't actually powerful, its just an improved Lossy Compression which is admittedly terrifying to use in many cases.
So you're saying if I use it... they'll be squished and lose random pieces of themselves?
I always found "The Perceptron" to have such a badass name…. 😅 (Math part was annoying though…)
Oomkiller
Piracy wizards may teach you a homing missile spell of linking a magnet to someone and then sending a torrent of bits and pieces their way.
Lightning wizards can teach you how systematically shocking your minions should to some extent boost their efficiency in the same amount of time. They call it 'over clocking'.
And 'distributed denial of service' or 'dedossery', is a mastery of wizards who are just pissed, means sending a ton of said minions to one particular shitty tavern, ordering something and walking away en masse.
Volatile Memory
PEBCAK
Secrets
Cloud Run
Kubernetes
Flash
Rest endpoint
Guru Meditation
Boot
Disaster Recovery sounds like a great party name.
Shielded Twisted Wire rootkit worm recursive loop MAC address( kinda like a true name i guess) Administrator control
Null
Null Modem
Crossover Cable
Null Modem Cable with Handshake
Request to Send
Edit:
Proxy
Reverse Proxy
wine control launches Wine's sparse control panel (most options are under winecfg). You can use it at fancy parties for fun tricks or to make someone puke.
Feels like I should DM some Shadowrun or Cryptomancer sessions again. Just to use those.
This thread feels like someone half remembering playing technomancers in shadowrun.
Memoization
Easily my vote for the most unweildy named concept in software development.
It always reads like a typo of memorization. Not exactly an accident, of course. Memorize is memory + -ize, while memoize is memo + -ize, and memo is short for memorandum, which comes from memory. Both terms refer to some kind of storage and retreival of information. The similarities are deliberate.
My gripe with it is that memo in my head exclusively refers to a one-paragraph email sent to my company to notify me about something. Not remembering something. Definitely not the very specific case of linking input parameters to results of pure functions.
So we have this made-up word that looks suspiciously like an existing word that is related and means something related but is not the same thing, and the words it is actually adapted from don't mean the thing it's supposed to mean. Thanks, I hate it.
Really ought to call memoization what it what it really is. Lazy-loaded lookup tables.
This just reinforces that one short of piratesoftware saying all programmers are wizards.
Pseudocode
Daemon Thread
Ruby on Rails
Onion Router
Python Commands
All leap to mind.
Superuser
Truncate
Force
Purge
Decimate
Warp transform
Innumerate
Checksum
Out of memory crash
Stuck process
Orphaned process
Killed child process
Force killed child process
Child workers
Lock contention Parallelism Buffer overflow