If AI coding is lowering your code quality, you're not managing quality right
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
If AI coding is lowering your code quality, you're not managing quality right
Unofficial Hacker News client; not affiliated with Y Combinator.
teliskr · · focus · HN ↗
When implementing new features or making large refactoring changes; I use the superpowers:brainstorming skill. That has consistent process which has worked really well. I alway review the code before merging, but most of the time there are few issues to correct.
I don't do 95% coverage, but I have increased it from 65% to about +80% and that is sufficient.
lolakutty · · focus · HN ↗
Kindly share the metrics by which you evaluate the changes.
teliskr · · focus · HN ↗
lolakutty · · focus · HN ↗
If this is true, then you are not saving a lot of time. Because most of the time is spent evaluating various options and ways to implement the functionality. Even when you are reviewing, you ll have to do that. (With LLMs, this is even more feasible, because now you can actually implement some of the variants, and evaluate them).
But on the other side, you are saving from typing the code. So if you are really reviewing everything, then you are not saving much time. The alternative is that you settle for some local maximum during each review, that in long term won't necessarly translate to a globlal maximum or even a global "good enough" position...
teliskr · · focus · HN ↗
lolakutty · · focus · HN ↗
[deleted] · · focus · HN ↗
[deleted]