Post #4203585
2026-07-29 15:47 UTC
This also means that the best way forward is to be restrictive in the feature set, to make code slowly, carefully, and with a deep and committed engineering mindset both at the level of the code itself, through good architecture and well-defined modules and interfaces, and at the level of the organisation, with multiple points of both human and automated review that can verify such proofs and guaratees, as well as run internal fuzzing.
Replies (1)
-
@pettter@social.accum.se 2026-07-29 15:49
curl seems to be an inspiration in this context, at least from the outside looking in, but I do wish that infrastructural code in general would be better at committing to standards, to ABIs and APIs, and to make sure that standards for outside communications are _always_ made in a protocol that can be provably correctly parsed.