From what I’ve seen and heard, AI seems to do well for test-driven development. That doesn’t necessarily translate into good code, but it does translate into tested code.
At the very least it can translate the documentation of an API into the appropriate tests to verify the documentation is correct, and I’m being quite humbled by that.
One problem I could see with the aggressive testing (which also happens in human-written codebases) is that it becomes hard to tell essential behaviour apart from details. If you nail everything down with a unit/integration test, nothing can be changed anymore.
I could imagine that this is part of the reason why LLMs love to duplicate code rather than adjusting existing code.
Well… That’s why you test the public API and not the internals. And if you need to change the API you should have a good enough reason that changing the tests is okay too.
Removed by mod
From what I’ve seen and heard, AI seems to do well for test-driven development. That doesn’t necessarily translate into good code, but it does translate into tested code.
At the very least it can translate the documentation of an API into the appropriate tests to verify the documentation is correct, and I’m being quite humbled by that.
Removed by mod
One problem I could see with the aggressive testing (which also happens in human-written codebases) is that it becomes hard to tell essential behaviour apart from details. If you nail everything down with a unit/integration test, nothing can be changed anymore.
I could imagine that this is part of the reason why LLMs love to duplicate code rather than adjusting existing code.
Well… That’s why you test the public API and not the internals. And if you need to change the API you should have a good enough reason that changing the tests is okay too.
Removed by mod