> it can help you massively improve your code cleanliness. All of the little nice-to-have features, the cleanups, the high unit test coverage, nagging bug fixes, etc., they’re all trivial to do now.

It can help if you write poor code without it, probably

High unit test coverage only means something if you carefully check those tests, and if everything was tested

▲

sockgrant 11 hours ago | parent [-]

The only way Claude can help improve your code cleanliness is if you write poor code?

Code coverage means nothing if you didn't carefully check every test? "and if everything was tested" do you know what code coverage is?

not gonna engage the trolling

▲

g-b-r 9 hours ago | parent [-]

> The only way Claude can help improve your code cleanliness is if you write poor code?

No? You assert that it writes better code than the average software developer?

> Code coverage means nothing if you didn't carefully check every test? "and if everything was tested" do you know what code coverage is?

Do you know?

Code coverage only tells what amount of the code gets *touched* by the tests.

To achieve code coverage it's enough to CALL the code, it doesn't tell you anything about the correctness of the tests: they could all end with a return true, and a code coverage tool would be perfectly happy.

So, yes, if you don't carefully check the test suite that the agent writes, it might well be worthless (or simply much less useful than you assume it to be, more realistically).

With "if everything was tested" I meant that you also need to check if the agent wrote all the tests that are needed, besides verifying that the ones it wrote are correct.

	▲	wiseowise 5 hours ago \| parent [-]
		> You assert that it writes better code than the average software developer? Absolutely. It contains a lot, if not majority, of all the code available at our hands right now and can reason, whatever it means for LLMs to reason anyway, about it. It absolutely demolishes average software developer and it’s not even close. > To achieve code coverage it's enough to CALL the code, it doesn't tell you anything about the correctness of the tests: they could all end with a return true, and a code coverage tool would be perfectly happy. > So, yes, if you don't carefully check the test suite that the agent writes, it might well be worthless (or simply much less useful than you assume it to be, more realistically). That’s like saying that if you don’t check every line your coworker writes it becomes worthless.