If someone submitted "How I managed to emulate Super Mario in C without using more than 30 Kb of memory" I'd be super interested and look to see what sorts of crazy pointer tricks or unioned structs were in use - even though I don't currently work with games or C in my daily.
If every detail was explained in layman's terms, reading would be terribly boring and nuanced technical writing would be dead.
There are some terribly complex CS concepts (try and explain how a hash function produces essentially random output - or how private and public keys are actually computed in a manner to make private keys non-trivially derivable from public keys) and some terribly ingrained jargon (Oh, how's that SSL cert was it SHA signed?) but the effect on your topic of how these jargony terms work is usually easy to express, you don't need to know the history of POSIX to comprehend that CS people have a tool that checks if a string sorta looks like an expect format that we use everywhere, and you don't need to explain positive lookahead zero width assertions to convey that point.
Having a single clause stating "ACH (the preferred US method for bank-to-bank transfers)" would instantly clear all this up... it's also insanely relevant because the topic of the article is about what happens when bank-to-bank transfers have a recipient who is dead.