you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 3 months ago (3 children)

I never understand why you wouldn't want to read the code. I prevent a massive amount of correct slop by just skimming. The LLM will 10 times out of 10 never ask "this code will be a massive duplication of exact same behavior, do you want to refractor it?" because it's trained to finish a task without asking if possible.

Uncle Bob now writes code for his tests instead of tests for his code. I know it's TDD but it always seemed backwards to me.

Unit tests for logic, integration tests for outside apis, e2e for features is the sweet spot IMO.

  • source
  • parent
  • hideshow 3 child comments
  • [+] 3 points 3 months ago (1 child)
  • [–] 2 points 3 months ago

    I use Claude/Codex, if it finds a thingy that's reusable it'll use it but it'll never create it or ask if it should be created in my experience. I find that it doesn't create new components but just replicates the existing one.

    Within same file is a different story though, it does write helper functions to share logic which is proper.

  • source
  • parent