Comment

Comment on AI Coding Is Massively Overhyped, Report Finds

the tests are written after the code is merged - there will be gaps, and the second dev will be lazy in writing those tests

I don’t really see how this follows. Why do the second one necessary have to be lazy, and what stops the first one from being lazy as well.
The reason I like it to be different people is so there are two sets of eyes looking at the same problem without the need for doing a job twice. If you miss something while implementing, it’s easier for you to miss it during test writing. It’s very hard to switch to testing the concept and not the specific implementation, but if you weren’t the one implementing it, you’re not “married” to the code and it’s easier for you to spot the gaps.

source

Sort:hotnew top

sugar_in_your_tea@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago
Devs are more invested in code they wrote themselves. When I’m writing tests for something I didn’t write, I’m less personally invested in it. Looking at PRs by other devs when we do pushes for improving coverage, I’m not alone here. That’s just human psychology, you care more about things you built than things you didn’t.

I think testing should be an integral part of the dev process. I don’t think any code should be merged until there are tests proving its correctness. Having someone else write the tests encourages handing tests to jr devs since they’re “lower priority.”

source
- Nalivai@lemmy.world ⁨2⁩ ⁨days⁩ ago
  
  Devs are more invested in code they wrote themselves. When I’m writing tests for something I didn’t write, I’m less personally invested in it.
  
  This, I think, is a very bad part of the problem and shouldn’t be happening regardless
  
  source
  - sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨day⁩ ago
    It shouldn’t, but it does. The person who writes the code cares more about its correctness, so I trust them to write better tests.
    
    source
    Nalivai@lemmy.world ⁨1⁩ ⁨day⁩ ago
    I absolutely don’t. Since we’re talking about bad cases anyway, I don’t trust a developer to be diligent in finding bugs in their code more than I believe they will try to make all the tests pass. And it’s easier and better for the ego to achieve that if you write shit tests that only cover cases that you know will work.
    
    source
    -> View More Comments