Post #1722060
2026-04-27 07:35 UTC
@brib @phillmv @jneen For me, it's less about how confusing the software can become, but more about "Is what I am testing for actually what I want?".
I can more easily manually verify that it makes sense than I can automatically come up with the contracts I want, and the latter leads to...not finding out until later that I don't actually want to do it that way, and sunk cost fallacy kicks in (As opposed to saying "Well, okay, let's try something else then.".).
I don't want green tests confirming that I did the wrong thing correctly; I'd rather they act as a "Your development is deviating from what you last thought was good; are you *sure* you wanted to make that update?".
Replies (1)
-
@phillmv@hachyderm.io 2026-04-27 12:15
@AT1ST @brib @jneen this is why i trot to write tests that fail first. by writing a test with a mocked out implementation it helps clarify the design and fill in gaps i haven’t thought of yet. this is a lot easier in higher level langs tha lower ones