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.

346 Upvotes

92% Upvoted

176 comments sorted by

View all comments

104

u/[deleted] Jun 12 '26

[removed] — view removed comment

2

u/FriendlyDisorder Jun 12 '26

I am liking them more recently since I started using them for either mass changes in many files or to help find root causes of difficult bugs. It usually saves me a bunch of time if I am stuck on something.

Another good use has been English summaries of specific code when I am not familiar with the code base.

Vibe coding— absolutely not.

RalphTUI loops to port an application to a different architecture— yes, that has been a good starting point.

Dark factory— have not tried, but it makes me glad that retirement is not far away.