Re:Automated Unit Test Improvement Using Large Language Mode...
by stavros on Saturday February 17, 2024 @10:49AM
(#39410529)
I don't understand this. Why is management telling you what to do? In our company, the managers ask/push the teams to improve some metric, but the teams are responsible for the how. The metric is usually high-level, like "reduce the number of bugs reported", not "increase code coverage".
Re:Automated Unit Test Improvement Using Large Language Mode...
by therealdrag0 on Sunday February 18, 2024 @04:49PM
(#39423771)
I think having cognitive complexity indicators are great. Many devs don’t think about that so having the visibility reminder is good on average. However it should not be blocking in any manner and it’s silly to drive a rewrite based on it. Engineering leaders should understand the architecture at a visceral level, know good patterns/design, and suggest refactors without static analysis tools.
Re:Automated Unit Test Improvement Using Large Language Mode...
by dgan on Tuesday February 20, 2024 @04:12AM
(#39439307)
"having them" is fine, being forced them down your throat is not. I mean like "your hotfix cannot be merged because you touched this piece of ancient code nobody understands and now it's complexity grew beyond the arbitrary threshold, please put all your tickets aside, and make a start refactoring this function because Sonar saud so"
Re:Automated Unit Test Improvement Using Large Language Mode...
by therealdrag0 on Tuesday February 20, 2024 @12:03PM
(#39443719)
Totally agree! That sounds absurd.
Then management sweeps in and is trying to add sonar, and it's a nightmare. Besides tripling our total build time to run this horrible tool, they want us to waste time rewriting our codebase to follow these insane rules like "cognitive complexity", and editor integration that takes several seconds to update after every file change.