this post was submitted on 23 Apr 2026
122 points (98.4% liked)

Technology

42862 readers
247 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] megopie@beehaw.org 22 points 1 week ago* (last edited 1 week ago) (2 children)

*75% of code was written by people who were required to have an AI plug in installed.

Probably also having their usage tracked.

Also have had their work loads increased and their deadlines shortened.

And if they don’t hit the metrics and meet the shorter deadlines… they get fired.

I’m sure that’s a recipe for functional, well tested, efficient, and secure software. Definitely not creating a shit ton of technical debt.

[–] Hirom@beehaw.org 5 points 1 week ago* (last edited 1 week ago) (1 children)

And I guess engineers would be held responsible for the code produced by the AI agent's they're pressured to use.

So management can blame and fire more engineers when things go wrong.

[–] fuzzzerd@programming.dev 3 points 1 week ago

Here, use this tool it makes you fast and it only costs you not understanding what you ship.

But when the tool screws up and breaks things we'll blame you and not the tool.

We must go fast so you must use this tool.

[–] resipsaloquitur@lemmy.cafe 3 points 1 week ago

Chat, please fix everything in the technical debt pile. Make no mistakes.