2026-04-01 18:58 UTC
Replies (3)
-
@aredridel@kolektiva.social 2026-04-01 19:00
@itamarst VERY MUCH. And they've been turning similar screws on their employees too. I wish them a very egg on their face for the consequences of their actions.
-
@itamarst@hachyderm.io 2026-04-01 19:00
@aredridel To sharpen the argument: this is a combination of a top-down political push and an addictive bottom-up emotional response. And conflating human work with machine generated code makes it easier to not think about the downsides because it allows management to shift blame workers for anything that goes wrong ("you're responsible for your code!"), and harder for people who do care to do something about it because you can't even choose how you prioritize your review time. Maybe not the biggest problem ever in this whole mess, but certainly as someone who has open source projects I do not want anything machine generated, no one's paying me to do that much more review work.
-
@dandean@indieweb.social 2026-04-01 19:03
@itamarst @aredridel The typical exec only cares about quality to the degree that it impacts immediate profitability. This is why addressing technical debt is generally deprioritized relative to feature work, despite its immense (but less visible) organizational cost. People keep saying "more guardrails!" will solve this, but every time we disconnect from the implementation and prompt our way through, we have a harder time understanding what we're building. It's the path of least resistance.