2 posts tagged with "Unit Tests"

"We're now cooperating with AIs and usually they are doing the generation and we as humans are doing the verification. It is in our interest to make this loop go as fast as possible. So, we're getting a lot of work done."

— Andrej Karpathy: Software Is Changing (Again)

This quote describes a shift that is already visible in many teams. Code generation has accelerated. Verification and validation increasingly become the bottleneck.

With AI tools, writing code is often not the limiting factor anymore. The hard part is proving that what was generated is correct, safe, and maintainable.

Writing unit tests is expensive. Not just in time, but in technical debt.

Every test you write is code you must maintain. When you refactor, you refactor twice: once for production code, once for test code. When dependencies change, you update mocks. When APIs evolve, you rewrite assertions.

What if there was a different way? What if your tests could be generated from reality itself?