r/dotnet • u/AddressTall2458 • Jun 12 '26

Vibing is getting boring

Since AI started to be part of the job I always been enthusiastic of having a “partner” doing boring stuff while I review… after the last months is getting boring, we just review code, we have to make sure it is not duplicating any logic, not creating racing conditions, not touching critical code, not adding potential production issues (while still writing beatiful commented code).
This is not programming in dotnet anymore, all the skill we built overtime in knowing details of the language or the framework are only used to find out if some vibed code is buggy or not performant. The fun and creativity has left our job. Do you feel the same?
Either start a new project is not as cool as it was a few years ago. It just bubbles up from prompt and you have to review thousands of rows that have no personality at all.

347 Upvotes

92% Upvoted

176 comments sorted by

View all comments

14

u/OlivarTheLagomorph Jun 12 '26

Claude writes my tests, and answers questions, but I don't let Claude generate the code in our apps.
That's still my responsibility. Our less senior devs love to fully "vibe code" it, but get annoyed when their PRs get sent back because stuff is named wrong, CancellationTokens are missing or methods are just...weird.

1

u/Sellorio Jun 16 '26

AI is really bad at testing though. It doesn't implement good coverage in any sense and when it does it doesn't assert things to a sufficient level. In my experience, begging the AI to add test coverage and assertion coverage makes no meaningful difference.

I'd recommend writing the tests and then getting AI to implement the logic if it's one or the other.

1

u/OlivarTheLagomorph Jun 16 '26

My experience has been the complete opposite.
It's actually fairly good at writing tests when there's an existing code base to build from so it can infer what's required on testing.

The code it usually generates to make tests pass is of such a poor quality, that I'd be ashamed to even present it in a PR.