I get the technical stuff regarding RF and EW, especially when it comes to having to jam all detected RF but still allowing your own RF comms, including networking, to get through among other requirements. What I try to avoid is the Army/DoD/Program Manager-ese that sound like the GD and NG commercials on WTOP. It’s annoying to us and tends to be very expensive when vendors pitch technical products using that DoD jargon.
“I get the technical stuff regarding RF and EW, ...What I try to avoid is the Army/DoD/Program Manager-ese...tends to be very expensive when vendors pitch technical products...” [mikey_hates_everything, post 18]
RF and communications systems are only about 10 percent of the problem. An artificiality, harking back to the days when each subsystem and operational area was served by its own designers & engineers. Causes latter generations to see it as a bunch of separate problems, instead of facets of an overall problem. Your reference to “RF” in isolation is a perfect sign: specialists resist the reality that it’s all the same stuff, from DC through AM, HF, FM, UHF, microwave, on up through EHF, SHF, IR, visible light, UV, X-rays, gamma rays, cosmic rays. The only differences are the frequencies.
I spent the better part of 30 years in uniform, trying to improve the language in official documents. It isn’t a problem that admits of simple, sweeping, final solutions. Not when contracts have to be written that can be legally enforced, while requirements documents have to be written in language agreeable to Congress and users both.
Fellow citizens love to blame Congress, the bureaucracy, contractors, attorneys: anyone but ourselves. Americans have big trouble with the notion that national defense is costly and un-speedy. Despite all the evidence of the past 160 years and more, they still want it in a hurry and on the cheap. It’s impossible to meet all those constraints.