Mustachius_Grumpius@thelemmy.club to Technology@lemmy.worldEnglish · 1 month agoEngineer says Claude Code has made his job "soul-sucking" as workers spend 12-hour days pressing enterwww.techspot.comexternal-linkmessage-square50fedilinkarrow-up136arrow-down11cross-posted to: [email protected][email protected]
arrow-up135arrow-down1external-linkEngineer says Claude Code has made his job "soul-sucking" as workers spend 12-hour days pressing enterwww.techspot.comMustachius_Grumpius@thelemmy.club to Technology@lemmy.worldEnglish · 1 month agomessage-square50fedilinkcross-posted to: [email protected][email protected]
minus-squarePollo_Jack@lemmy.worldlinkfedilinkEnglisharrow-up0·1 month agoPossibly motivated to do more complex problems to spend more tokens?
minus-squareLeon@pawb.sociallinkfedilinkEnglisharrow-up0·1 month agoI can believe this. I’ve been put on slop duty, and had the slopmachine go all Time to run the test to ensure everything is good. It passed. Good. Let’s run the entire suite to ensure no regressions. All tests passed, yay. And I’m here thinking, if you’re gonna run the whole suite anyway, why’d you run an individual test? That’s just redundant.
minus-squareshiftymccool@piefed.calinkfedilinkEnglisharrow-up1·1 month agoIt’s pretty much what i do when i think i’m done. Run the test(s) for the stuff i touched, then the whole suite to make sure nothing else broke. Why would i take all that time to run the whole suite every time?
Possibly motivated to do more complex problems to spend more tokens?
I can believe this. I’ve been put on slop duty, and had the slopmachine go all
And I’m here thinking, if you’re gonna run the whole suite anyway, why’d you run an individual test? That’s just redundant.
It’s pretty much what i do when i think i’m done. Run the test(s) for the stuff i touched, then the whole suite to make sure nothing else broke. Why would i take all that time to run the whole suite every time?