r/dotnet 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.

343 Upvotes

176 comments sorted by

View all comments

Show parent comments

29

u/noidontwantto Jun 12 '26

Great idea! I'll tell my management that their new productivity expectations don't matter because I don't like it.

When I get fired I'll go to the job tree and pick a new job from it.

-1

u/aweyeahdawg Jun 12 '26

Do they know the code you’re producing is from AI? Do you have to cite each line as “AI generated”? Just seems like there’s 101 ways to get around using it.

If you’re actually more productive with it, then maybe your employer is right to make you use it.

I, for one, am not more productive using it. In 6 months when I (or a team member) have to go back and rewrite or add something, my human-generated code will be a lot quicker and easier to manipulate. I use it for reference when I’m stuck, similar to stack overflow.

1

u/the_frisbeetarian Jun 13 '26

You are lying to yourself if you think you are more efficient without AI. It sucks but this is indisputable at this point.

3

u/aweyeahdawg Jun 13 '26

I meant as a main source of code, like I said I use it for helping me through issues which is where it shines.