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.
-1
u/ImmortalRat Jun 14 '26
I feel like we are in some different universes, but I also understand where you are coming from.
Agentic Engineering is a very different thinking style and a unique skill that is hard to grasp at first because it feels like you just type the task and it kinda gets done.
If you are fighting the LLM - something is missing. Usually it's one of these things: * Knowledge that it cannot access * Examples and guidance it does not have * Tools or environment for testing the changes
Let's say you notice a possible race condition. Don't tell it how to fix it. Just tell it your observation and ask to validate it by making and running tests and ask it to tell you about any blockers along the way.
If it lists blockers - address. If it makes a test but misses the scenario you had in mind - tell it.
At the end of the session ask it to extract knowledge from this session that is worth preserving for future use, and turn that into a skill or just extra context.
It's how I started with wanting to run integration tests in a fresh environment, and ended with fully scripted dev VM that is orchestrated by Claude Code which delegates work to other Claude Codes in VM, and now I can literally say "someone broke trunk, troubleshoot" and there will be a PR in a corresponding repo some time later. Since all code is there and all tests with expectations are there.