![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Say you’re trying to defend against something like a Shahed-136. It can hit pretty much anywhere in Ukraine. You can’t stick an AA gun on everything that Russia might consider trading a Shahed-136 for.
As far as I know, the routine in the current war is - the AA gun is on a truck that moves 80 km/h, the drone comes in slower than 300 km/h, one or multiple truck crews position themselves on likely vantage points for intercepting, and the rest is luck.
Having once worked on an open source project that dealt with providing anonymity - it was considered the duty of the release engineer to have an overview of all code committed (and to ask questions, publicly if needed, if they had any doubts) - before compiling and signing the code.
On some months, that was a big load of work and it seemed possible that one person might miss something. So others were encouraged to read and report about irregularities too. I don’t think anyone ever skipped it, because the implications were clear: “if one of us fails, someone somewhere can get imprisoned or killed, not to speak of milder results”.
However, in case of an utility not directly involved with functions that are critical for security - it might be easier to pass through the sieve.