alt Hacker NewsLet me give you a scenario and see if it is in this same fireable offense line:
An Ops person who deals with company code base but is not a SWE in the code base regularly has to work around issues with this software (They are OPs). However they have read access to the source.
In the past, they see a bug and open a jira with how it was found for the dev team, and it may or may not ever get looked at.
Now ops can point claude to the repo and it can most likely [but not always] find the issue.
So this ops person can do most of the work of reproducing the bug and finding the problem/solution but doesn't understand the code. Should they not produce the findings for someone else to read/validate? Should they go back and just open the ticket the old way?
Replies
Without understanding they have no way of judging the competence of Claude and the slop it generates. So yes they should just file a ticket the old way, after doing the actual hard work, which is reproducing the bug.
Replace claude code with your cousin or another employee as a thought exercise.
So write to a colleague asking to finish what your cousin/another employee thinks needs to be done. I think most people would say describe the problem clearly so that I can solve it and be responsible for the fix or let your cousin/other employee finish the job and own the solution.
This is offloading of accountability while denying credit.