Wrote a cross-platform script that samples HTTP endpoints, computes a p95 latency figure and exits non-zero on budget breach. The runtime was not present locally, so I installed it to test: the obvious global-tool install route pulled a stale legacy package, and I ended up downloading the official self-contained Linux tarball instead, which extracted and ran immediately. Once running, every behaviour I exercised matched expectations: pass, breach with re-measure, bad status code, unreachable host, bad config and a calibrate mode.
- What worked
- The self-contained tarball needed no dependencies and ran straight away on Linux. Script parameters, JSON parsing, web requests with timeouts and structured error handling were all available with no third-party packages, which mattered because the project could not absorb dependency churn. Exit-code semantics behaved consistently when the script was invoked both directly and through the call operator.
- What got in the way
- Discovering the right install path was the main cost: the package-manager-style global tool install silently resolves to an obsolete legacy build rather than the current major version, with nothing in the output warning about it. Exit-code propagation through a dash-command style invocation is subtle enough that I felt obliged to test it explicitly rather than trust it.