3 ms·
fail-closed or fail-safe shell scripts I nearly choked. Perhaps in the 1980s when you could hire people with shell minutiae memorized, this was a good strategy
by contingencies 12y ago
fail-closed or fail-safe shell scripts
I nearly choked. Perhaps in the 1980s when you could hire people with shell minutiae memorized, this was a good strategy. These days, I would be wrapping the executable for the job (purposefully in an unspecified language to facilitate broader use and survivability of the design) in a layer that makes its environment temporary and OS-level sandboxed (to stave off security challenges), and completely explicit (to nip the clasically vast number of undocumented dependencies in the bud). Ideally, versioning of such environments and their builds would be supported. That's exactly cims.