Technology

hideshow 8 child comments

parent

[–] heluecht@pirati.ca 1 point 7 months ago (7 children)

@TehPers @Limerance why hadn't you time to review it? Every minute in review pays off because it saves you from hours of debugging and handling with angry customers.

hideshow 7 child comments

parent

[–] TehPers@beehaw.org 7 points 7 months ago (2 children)

Because if I spent my whole day reviewing AI-generated PRs and walking through the codebase with them only for the next PR to be AI-generated unreviewed shit again, I'd never get my job done.

I'd love to help people learn, but nobody will use anything they learn because they're just going to ask an LLM to do their task for them anyway.

This is a people problem, and primarily at a high level. The incentive is to churn out slop rather than do things right, so that's what people do.

hideshow 2 child comments

parent

[–] heluecht@pirati.ca 1 point 7 months ago (1 child)

Who creates these AI-generated PRs? Colleagues in your company or some third party people in an open source project? I guess when this would happen to me, and the PRs were created by colleagues, then I would escalate this to my line manager. And I guess that she would understand why this is a problem and why it had to stop.

parent

hideshow 1 child comment

[–] TehPers@beehaw.org 1 point 7 months ago*

Colleagues, and the issue is top-down. I've raised it as an issue already. My manager can't do anything about it.

parent

[–] Limerance@piefed.social 0 points 7 months ago* (3 children)

Sure, that’s the theory. In practice code review often looks like this:

a quick glance to see if the code plausibly does what it claims for longer patches
A long argument about some stylistic choice for short patches

In other words – people were barely reading merge requests before. Code reviews have limited effects as well. You won’t catch all bugs or see if it actually works just by looking at the code. Code reviews mainly serve to spread knowledge about the code among the team. The more code exists in a project, the harder it is to understand. You don’t want huge areas of code, that only one person has ever seen.

Project managers don’t necessarily talk to angry customers directly. They might also choose to chase more features instead of allocating resources to fixing bugs. It depends on what the bosses prioritize. If they want AI and lots of new features, that‘s what they will get. Fixing bugs, improved stability, better performance, etc. are rarely the priority.

hideshow 3 child comments

parent

[–] heluecht@pirati.ca 2 points 7 months ago* (last edited 7 months ago) (2 children)

@Limerance Well, on Friday I spent around 1.5 hours just reviewing a single PR. And I'm not done. I will have to continue my work on it on Monday. Reviewing in our company means understanding the connected use case, then having a look if the coding does what the use case defined. Also we look if the coding is done according to our internal style guide. Since our review is normally done by at least two people, (at most of our apps two people have to accept the PR until it can be merged) one person will see what the other missed. And we often talk about what the other missed, so that we learn.

Concerning angry customers: Our apps are used by several ten thousand users. And although our group doesn't have direct customer contact, we get the bug reports and have to fix them anyway or we have to support the teams who directly work with the customers.

And I just realize that I'm in a very lucky situation. In our company each use case is tested thoroughly by the responsible QA and PO. And for each use case we write half a dozen (or more) test functions that check the functionality. Normally coding the tests takes more time then coding the use case itself.

Our company is very AI driven, but on the same hand we hear in the regular town halls about the customer satisfaction. And the goal there is to increase it steadily. Our customers are companies, so maybe there's the difference.

hideshow 2 child comments

parent

[–] TehPers@beehaw.org 1 point 7 months ago (1 child)

To put some perspective into what our code looks like, there are very few tests (which may or may not pass), no formatter or linter for most of the code, no pipelines to block PRs, no gates whatsoever on PRs, and the code is somewhat typed sometimes (the Python, anyway). Our infrastructure was created ad-hoc, it's not reproducible, there's only one environment shared between dev and prod, etc.

I've been in multiple meetings with coworkers and my manager talking about how it is embarassing that this is what we're shipping. For context, I haven't been on this project for very long, but multiple projects we're working on are like this.

Two years ago, this would have been unacceptable. Our team has worked on and shipped products used by millions of people. Today the management is just chasing the hype, and we can barely get one customer to stay with us.

The issue lies with the priorities from the top down. They want new stuff. They don't care if it works, how maintainable it is, or even what the cost is. All they care about is "AI this" and "look at our velocity" and so on. Nobody cares if they're shipping something that works, or even shipping the right thing.

parent

hideshow 1 child comment

[–] heluecht@pirati.ca 1 point 7 months ago

@TehPers That sounds like a very bad situation!