3 ms·
Honestly, this approach would probably get you fired eventually for non-coop behaviour in every company I’ve worked at. AI slop code is becoming the go-to way
by tokioyoyo 1y ago
Honestly, this approach would probably get you fired eventually for non-coop behaviour in every company I’ve worked at.
AI slop code is becoming the go-to way for a lot of written code. At some point it’ll make more sense to find a solution to the problem (“how to be confident in slop code”), rather than going against the financial motives of the business owners (cut expenses, maximize profit somehow through AI). I’m not sure if it’s right or wrong, but it is what it is.
- embedding-shape 1y ago> Honestly, this approach would probably get you fired eventually for non-coop behaviour in every company I’ve worked at. I don't think I've ever worked in a company that would fire someone for something like that. Maybe you'd get a scheduled conversation to talk about it, to try to resolve whatever is going on (in this case verbose AI slop PRs), since obviously something is going wrong when people start engaging in malicious compliance. But then I also never worked in a country where people can be fired for whatever reason, it's always been a legal requirement (in the countries I've lived at least) that the firing needs to be properly justified and explained, and firing someone like that wouldn't be justified.
- fifilura 1y agoWow, 636 karma points in 8 days since registering! You are on a roll! (FWIW i upped this comment).
- embedding-shape 1y agoHah, don't say that, just makes my current computer and HN obsession even more clear, I've hidden upvotes in my browser just to avoid realizing that! (jokes aside, I do probably spend too much time on HN at this moment...)
- tokioyoyo 1y agoIt wouldn’t be a direct firing, but if the majority of the company/team is pro-AI, people will complain privately for “being a person hard to work with”. Eventually, after 6 months of repetitive passive aggressiveness, you’ll be let go or get paycuts.
- userbinator 1y agoIf the company is like that, chances are you wanted to find a better job anyway.
- pavelai 1y ago> Honestly, this approach would probably get you fired eventually for non-coop behaviour in every company I’ve worked at What's so non-coop in this? This huge PR is a non-coop work and it requires to be fixed. Just imagine if someone locks the work of the whole branch just to review 9000 LOC, which they even didn't wrote. It's just no-go option And even if there would be an AI which explains what this code is doing, people wouldn't be able to check it manually in reasonable time. It just enormous piece of work. So until there is a solution to this, such PRs should be declined and rewritten Also it seems like the worker who brought this code doesn't know how evaluate the complexity of the task relatively to the solution, so there is a question about their qualification and level