5 ms·
Not sure what you’re getting at
by teaearlgraycold 14d ago
Not sure what you’re getting at
- Sivart13 14d agoTest coverage for its own sake is not always a worthwhile goal.
- kyleee 14d agoUnless it was indeed valid coverage? You are assuming it was all bad
- teaearlgraycold 13d agoCoverage started out kind of mediocre, about 50% IIRC. There were a lot of easy wins, and a handful of files were intentionally ignored. I also had it first review all tests for superfluous ones that could be deleted.
- nottorp 14d agoThat's how the LLMs made you think of your work? You're producing commits now? It's like "content creator" vs "writer" or "artist".
- teaearlgraycold 13d agoI'm not producing commits. LLMs are producing commits. Fix more things, solve more problems, and do it to a higher degree of quality in less time using LLMs. What's to complain about?
- nottorp 13d agoBasically that using "commits" implies a certain degree of psychological detachment from your work. Did you ever use "commits" before LLMs came out? An actual psychologist could explain it much better than me, but i notice these things.
- teaearlgraycold 13d agoFair enough. I didn’t do most of the work.
- simonw 13d agoI've long thought that commits are the principle unit of work for a software developer. We don't ofter write software from scratch, we modify existing software - and a well crafted commit is a great way to capture that effort.