undefined

points

[-]

It does amaze me when colleagues refuse to read what I (personally, deliberately) wrote (they ask AI to summarize), but then tell AI to write their response and it's absolutely bloated and full of misconceptions around my original document.

If they aren't willing to read what I put effort into, why should I be expected to read the ill-conceived and verbose response? I really don't want to get into a match of my AI arguing with your AI, but that's what they've told me I should be doing...

by switchbak3 hours ago|

parent|

[-]

I've been having ongoing issues with a manager who responds in the form of Claude guided PRs. Undoubtedly driven from confused prompts. Always full of issues, never actually solving the problem, always adding HEAPS of additional nonsense in the process.

There's an asymmetry of effort in the above, and when combined with the power asymmetry - that's a really bad combo, and I don't think I'm alone.

I'm glad to see the appreciation of the enormous costs of complexity on this forum, but I don't think that has ascended to the managerial level.

by CharlieDigital3 hours ago|

parent|

[-]

    > ...a manager who responds in the form of Claude guided PRs

I think the job of a dev in this coming era is to produce the systems by which non-engineers can build competently and not break prod or produce unmaintainable code.

In my current role, I have shifted from lead IC to building the system that is used by other IC's and non-IC's.

From my perspective, if I can provide the right guardrails to the agent, then anyone using any agent will produce code that is going to coalesce around a higher baseline of quality. Most of my IC work now is aligned on this directionality.

by sodapopcan4 hours ago|

parent|

prev|

[-]

Ya, I can't stand that. Asking a question and being hit with "this is what claude said" gives me a new kind of rage.

by Izkata2 minutes ago|

parent|

[-]

Yeah, this happened to me recently and the advice could have caused data corruption (yay old systems). I only caught it because they asked before making changes and I had a vague memory of it from having investigated the same thing almost a decade ago (and found the note and explanation with a link to a bugtracker in my personal wiki).