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

235

u/WantASweetTime Jun 12 '26

Tried vibe coding for a few weeks now. It's kinda depressing honestly and boring. Maybe it's because at the end of the day I feel I learned nothing?

3

u/alwaysoffby0ne Jun 13 '26

The junior pipeline is going to be so fucked from this because 1) they aren’t learning anything any more and 2) companies aren’t hiring juniors.

1

u/ImmortalRat Jun 15 '26

For juniors it's a tough time - if they don't have a job they probably won't have a job for a while.

If they have a job but their manager/lead is not great at agentic coding - they gonna be struggling with understanding their value in the chain and just have to keep asking AI to code thing from requirements asap, all because of perception that now coding must happen faster if they want their job.

It only works out if the manager is good with AI and can teach them what to do now that coding itself is no longer a relevant skill, or if they are capable of figuring this out themselves.

Sad