I think in this text, details like the timeline are simplified a bit too much. But I agree with the general tendency described.

There was never a time where software was perfect, but the accelerating cadence of serious, widespread incidents with real-world effects seems real.

Edit: Some jokers have named this phenomeon “The Crapilarity”. I am not sure whether it is written with “h”, but I guess there will be a few tasty roasted chickens on the road.

  • HaraldvonBlauzahn@feddit.orgOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    15 hours ago

    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.