2 ms·
Better link, at least for me: https://xcancel.com/paulg/status/1953289830982664236 https://xcancel.com/paulg/status/1953289830982664236 I've done that, occasi
by cess11 1y ago
Better link, at least for me:
https://xcancel.com/paulg/status/1953289830982664236 https://xcancel.com/paulg/status/1953289830982664236
I've done that, occasionally, though through deterministic means, i.e. code generation tools. If you know what you're getting it's no big deal. If you don't, it probably is, but not in a good way.
If it's actually true and the result reasonable, I expect ~7-8 KLOC out of those 10 to be adequate and necessary tests, and roughly 4 out of those 12 h a day to be waiting for tests to finish. I also expect static analysis tooling, linters, ast-grep and so on get a lot of use.
- philipp-gayret 1y ago> I also expect static analysis tooling, linters, ast-grep and so on get a lot of use. Better yet, feedback from these kind of tools is exactly what AI is great at in iteratively resolving so you don't have to review code below your standard of quality.