>>105831675
>Damn they had you editing plain text files, and that was the job?
In my trade, we affectionately call eachother "battle secretaries"; we take the message traffic (as in literally the Tom Clancy-esque allcaps nonsense transmissions) and package them in a more digestible form.

On the botes, the preferred way to do it was
>receive the message, probably through Outlook (but potentially over radio teletype)
>save everything as .txt files to a given local share (the botes have servers)
>vet the bulk for applicability/relevance to the unit (i.e. if you don't have aircraft, probably no one cares about wide-distribution air traffic control messages and will yell at you if included(unless a helicopter crashes nearby in which case it becomes your personal fault it did despite your unit not even having a helipad))
>strip header and footer information that no one but the operators care about
>add header/footer information for local bookkeeping
>print, staple, hole-punch, put it in a binder with sticky notes/tabs
>highlight the important stuff
>do said highlighting by hand, because normies' eyes glaze over when the highlighting too straight*
>hand-deliver it to the highest-ranking person willing to even look at you
>get yelled at by everyone above the guy you gave the binder to because you didn't consort with them first

*I was once told that I shouldn't use a ruler for this because it's too regular and thus too hard to notice

>What would the charge have been?
"conduct unbecoming" or "dereliction of duty" or something; it was clearly an empty threat. But he already didn't like me for various reasons. He made a similar threat to me about telling stories college about a teacher who would always end every Combinational Logic lecture with "...And that's important to high-speed cryptography!" because he worked at Lockheed or something before becoming a professor)

empty threats are just that but are still offensive and they still work. I will die free and die mad