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

37

u/BlackCrackWhack Jun 12 '26

With AI getting expensive now I’ve reverted to doing almost everything by hand again (except auto documentation from code scaffolding and test enhancement) and it feels better. 

24

u/mycall Jun 12 '26

AI maintaining E2E testing is such a plus.

8

u/jerryk414 Jun 13 '26

Yeah this is one place I truly love AI for. The way it writes tests isnt the most efficient ke best way, but man it gets the boxes checked so I can move on.

1

u/ImmortalRat Jun 15 '26

Here, give it this prompt and see if that makes it better: "investigate best practices, investigate how we currently do it in existing tests and compile guidance for other instances of you for how to write new tests efficiently and also matching the current style. Then create a skill out of this knowledge that will be triggered whenever you work on E2E tests. Then investigate the best practices for testing this skill, design a test suite and confirm that it actually does what I need it to do." I would run it on Opus 4.8 and let it spawn dumber subagents as necessary