• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle


  • 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.



  • Both of you are right.

    It’s difficult, but how difficult depends on the task you set. If the task is “maintain manually initiated target lock on a clearly defined object on an empty field, despite the communications link breaking for 10 seconds” -> it is “give a team of coders half a year” difficult. It’s been solved before, the solution just needs re-inventing and porting to a different platform.

    If it’s “identify whether an object is military, whether it is frienly or hostile, consider if it’s worth attacking, and attack a camouflaged target in a dense forest”, then it’s currently not worth trying.