Unit tests are exactly for code that is often rewritten, because it ensures that whatever interface still behaves the same, regardless of the implementation. This a large portion of the point of unit tests: not for testing the initial implementation but confirming that any subsequent implementation behaves the same.
In a normal scenario yes, but “vibe coding” rewrites whole swaths of code. It’s like painting detail with a bucket. Trying to keep up with it seems like a sisyphiean task
Unit tests are exactly for code that is often rewritten, because it ensures that whatever interface still behaves the same, regardless of the implementation. This a large portion of the point of unit tests: not for testing the initial implementation but confirming that any subsequent implementation behaves the same.
In a normal scenario yes, but “vibe coding” rewrites whole swaths of code. It’s like painting detail with a bucket. Trying to keep up with it seems like a sisyphiean task