It's a cool thing that software moves so much faster than other processes, like in my experience military grade weapon loading. Our sub would dock at the pier

It's a cool thing that software moves so much faster than other processes, like in my experience military grade weapon loading. Our sub would dock at the pier the day before, everyone but Weapons Department got the day off/in port duty day. Weapons Department would hold an all afternoon walkthrough of the entire process. Manpower locations and roles. Equipment setup and basic operations. Types, quantity, and sequence of weapons to take aboard. Expected timeframe / pace so that no one was expecting to have to hustle to catch up. And everything was in binders, with plastic strip edged pages and fresh grease pencils issued to everyone managing. Every one of those steps was a result of "Ok, crap, what do we rewrite to make sure (shudder) THAT NEVER happens again." And even so, on my fifth loadout party, I still missed a retaining strap and almost helped dump a torpedo in the harbor, except there was already a step right after mine with a separate checkbox that said "Aux handler has checked strap type/quantity/positioning for weapon type." Procedures are great for the things that need them. And when you have numerous teams/functions scattered about, procedures are even more necessary. And I do get that a lot of code is not likely to detonate under the companies' hull, per se.