• 8 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: April 4th, 2025

help-circle






  • One of the developers in the exercise wrote code that was obviously incorrect to pass one of the rounds, but all of the tests passed. After that code was written, everyone basically became stumped as to how to proceed, and we largely ended up talking about how the “coach” needed to “catch his flight” soon and he exited the exercise early.

    Seems to match what John Ousterhout wrote, in “A Philosophy of Software Design”, and what he called “debugging a system into existence”.

    Tests and testing cannot prove a program is correct. What they can is find bugs in edge cases and usually taken paths, and they are surprisingly efficient at this. The downside is that systems which rely too much on them can have gazillions of bugs when the execution goes astray from the happy path, for example if some memory allocations fail.






  • In the enterprise space, we largely avoid NPM or Composer, et al, because those very best-practice docs (iso27002, here, later SLSA) prohibit repos that obscure or frustrate validation and code pedigree; and the gleeful incestuous inclusion of projects within projects means source code isn’t properly managed - a failure - so npm won’t do.

    Rust (that is, cargo and crates.io) does in principle the same, and Java (via Maven) as well. Their quality is arguably better, but a lot of modern software has hundreds of dependencies.

    I am wondering whether the SBOM philosophy is merely a box-ticking exercise. It does not buy you much when you know you have a buggy 15 years old TCP stack in your industrial control, but you can’t upgrade it because there is no storage left on your device. And the same holds for Cisco routers. Constantly upgrading works,in my experience, only with completely open systems like Linux, on open hardware.