Post #1722038

2026-04-19 16:51 UTC

As for automated testing / acceptance checks as a replacement, that mitigates the problem somewhat, but certainly doesn't eliminate it. The tool can make your tests pass, sure, but did it architect it correctly? How do you structurally evaluate that? You fall into the linter tar-pit pretty quickly with that approach.

Replies (2)

@jneen@unstable.systems 2026-04-19 16:52

i think the idea that there is a quick, easy measure of "good code" that is universally applicable and not filled with holes is... well it's just not true, and we're not even close to defining the problem rigourously, let alone solving it.

Open ##1722039
@beeoproblem@mastodon.gamedev.place 2026-04-27 20:49

@jneen not to mention some folks will vibe-code the tests so they're effectively back at square one WRT hypervigilance Also I don't think I have ever seen an automated test suite that has perfect coverage for everything. I have seen people say they have that, then follow up with something like "I have 100 tests for my [very nontrivial thing] it's covered" and the tests consist of one or two happy-path cases one obvious failure mode and little else.

Open ##1736969