4 ms·
The problem rather is that you still have to stay somewhat agreeable while calling out the bullshit. If you were "socially allowed" to treat colleagues like >
by aleph_minus_one 1y ago
The problem rather is that you still have to stay somewhat agreeable while calling out the bullshit. If you were "socially allowed" to treat colleagues like
> All while the author—who clearly only skimmed their “own” code—is taking no responsibility, going “whoopsie, Claude wrote that. Silly AI, ha-ha.”
as they really deserve, the problem would disappear really fast.
So the problem that you outlined is rather social, and not the LLMs per se (even though they very often do produce shitty code).
- AnimalMuppet 1y agoThey should get a clear explanation of the problem and of the team expectations the first time it happens. If it happens a second time? A stern talk from their manager. A third time? PIP or fired. Let your manager be the bad guy. That's part of what they're for. Your manager won't do that? Then your team is broken in a way you can't fix. Appeal to their manager, first, and if that fails put your resume on the street.
- aleph_minus_one 1y ago> Let your manager be the bad guy. That's part of what they're for. > Your manager won't do that? Then your team is broken in a way you can't fix. If you apply this standard, then most teams are broken.
- 01HNNWZ0MV43FF 1y ago"A big enough system is always failing somewhere" - can't remember who said it
- sudahtigabulan 1y ago> If it happens a second time? A stern talk from their manager. In my experience, the stern talk would probably go to you, for making the problem visible. The manager wouldn't want their manager to hear of any problems in the team. Makes them look bad, and probably lose on bonuses. Happened to me often enough. What you described I would call a lucky exception.
- sevenseacat 1y agoFor interrupting the velocity and efficiency of the other dev.