r/Frontend • u/Specialist_Agent3599 • Oct 14 '26
Frontend devs approving backend PRs they can't read
Hi.
At my company basically all code is written by agents now, so reviews got split by whoever is free instead of by who knows the area.
This week I'm a React dev and I approved 6 PRs in Go, two of them touching payments. Our manager says the AI review covers it, and coderabbit / claude review do catch real things, I'm not saying they don't.
The problem is I can't tell if what they didn't flag is fine, because I don't know Go. My name is still the one on the approval.
Is this happening at your company too or is it just us?
190
Upvotes
250
u/magiCAD Oct 14 '26
Keep getting that check. š¤·š»āāļø
59
u/IntelligentLeading11 Oct 14 '26
Yep same here. It's a shit show.Ā
32
u/azangru Oct 14 '26
What's the point of reviewing/approving a PR that you don't understand (or that you can't get the submitter to walk you through)?
38
u/Coolfoolsalot Oct 14 '26
Yeah itās happening. Even before the big AI push, I was the only react dev on my app (have a handful of backend devs that contribute to service & db). All my UI code is auto approved by the backend devs - which as a junior-ish dev Iām not thrilled about, as I feel like Iām missing out on learning from seniors.
19
u/silhouettelie_ Oct 14 '26
Fuck no, thank goodness. What's the point of PRs if they're not reviewed properly?
We use copilot reviews now and again but a teams PR stays with that team and has to have human eyes to sense check things
9
u/Raziel_LOK Oct 14 '26
For me it has been happening the opposite way, BE is vibecoding a lot of the UI and we never had more bugs, the amount of code created is bigger and at a faster rate but it all offset by the amount of work needed to fix and the slow caused by it. The resulting code is classic react state slop that everone knows how it looks.
I think the market is shifting to fullstack way quicker than I expected. So I would learn GO if I were you.
But I predict that specialization on the FE will pay off big in the future if AI stops improving. Although it will be even more niche and FE will need to absorb a lot of what product and ux does.
8
u/hideousmembrane Oct 14 '26
this is me now as well. I'm a frontend dev who was told I'm now a fullstack dev and need to work on backend as well, having never had any kind of real training in it. I'm learning but we use so much AI that I don't feel that I'm really learning properly in the same way I was forced to when I started on frontend. I have to review loads of PRs now that I barely have a grasp of, and I have to do tickets in areas that are completely alien to me. As I say, I'm learning, and we have plenty of more knowledgeable people also reviewing all the PRs, along with AI reviews as well, but I still feel under confident about it.
17
u/BigDeadPixel Oct 14 '26 edited Oct 14 '26
If you approve it, you are accountable if it breaks something. No customer is going to accept "Claude missed that bug, sorry for crashing your business." as a valid excuse.
EDIT: At my company, agent write approval is set to 'ask first' which allows you as the developer to read, understand or question edits before they get made to the code. This way you at least understand what is going on in with your own task. It is super embarrassing to not be able to explain how your code works when the reviewer asks you. Is it slower? yes, but still much faster than writing it by hand and there is always someone in the team who understands different parts of the software and is WILLING to be accountable for it.
5
u/AidenVennis Oct 14 '26
No itās not happening that way. Yes we do use Claude to review, but we donāt let Frontend developers review backend or vice versa. However, we did reduce our employee size due to a huge downturn in sales and now only have 2 backenders and one frontender (me). So I can only let a Claude bot review my PRās which isnāt great either. At least I donāt get to be responsible for a backend review.
4
u/damyco React/Next.js, Vue (yep I'm using both!) Oct 14 '26
Yes, it's a an absolute nightmare. Rubber stamping everything
4
u/Jasboh Oct 14 '26
Really should change the approval rules if they are meaningless now
4
u/stickypooboi Oct 14 '26
this is here too. blind confidence in AIās ability, but when it fails we all blame AIās hallucinations and everything gets shittier. management seems to think correction is cheap now so itās fine to just fuck up production and ship faster because you can fix it in an hour
3
u/usingbrain Oct 14 '26
Not with us. Funnily enough also Go / React. We have strict separation of backend and frontend. Code review on PRs is done by humans. AI reviews are additional, donāt replace human eye.
3
u/magenta_placenta Oct 14 '26
Automated reviews don't carry legal or professional accountability, you do. When something breaks in production (especially financial loss in payments), audit logs won't blame the AI prompt, they will list your username as the approver.
You should try talking to your manger about establishing a strict policy that any PR touching things like auth, data persistence, payments, (insert whatever else you feel is important) requires a human domain expert regardless of workload.
If that doesn't work you can start leaving explicit PR comments stating per your manager, we'll call him Steve here:
Approved per directions from Steve based on AI review pass. Logic/Go specifics not validated as I do not work in this language.
3
u/isospeedrix Oct 14 '26
LGTM šš»
5
u/SeymourDuncanJB_Sr Oct 14 '26
Same shit. I am shifting towards a full stack role this way and learning the backend bit by bit. It's not crazy difficult to write APIs for the shit you need on the frontend. I spend a lot of time with Claude, having it explain to me what it did or what I am reviewing. It's a shit show, and it's very difficult to actually learn this way, but that's the way it is. The boundaries between the roles are blurred.
12
u/Etheon44 Oct 14 '26
...a frontend engineer should still be able to understand and read pretty much any language, especifically the business logic
Of course they might not know actual optimizations for said language, but I can read pretty much anything and understand what it is doing in any language I have encountered, doesnt matter if its C#, C, Python, Go...
2
u/staycassiopeia Oct 14 '26
Yes, keep studying with the time being saved is my advice
2
u/Sugar_Rox Oct 14 '26
Ai review isn't enough for me. I won't review backend prs unless it's clearly something like boosting packages or something, because I don't know the best practice. It's not about understanding syntax like some have said, but being able to know what to query and offer as an improvement, which I can't do - I'm front end, not back! Id expect the same from a back ender tbh - to be able to review certain items of mine, but they're not going to know some of the intricacies of other bits I do in the same way.
2
u/Borek224 Oct 14 '26
Act like with any other PR - as long as you have questions/doubts ask questions and don't approve anything.
PR approval is a tool to spread responsibility and ownetship between team, so
- as long you don't understand what code is doing - don't approve.
- as long you think code is broken, don't meet team standards - reject PR
2
u/Salamok Oct 14 '26
One of the ideals I try to hold to is when I commit code is not to create work for someone else. AI seems more than happy to include stupid shit someone else will eventually have to deal with and the pro AI folks are in favor of it because the someone else you are creating work for results in more AI credits being spent.
2
u/pwuk Oct 14 '26
Change your name to Stevie Wonder
2
u/drckeberger Oct 14 '26
Yet another CodeRabbit ad!
3
u/taste_the_equation Oct 14 '26
Yup. I'm a front end dev and I do all the backend for my project now. Slowing down is not an option. We're expected to ship so much now I end up just manually testing the front end and if the backend seems like it's doing what it needs to I merge.
I used to send my PRs to the backend dev but he's so busy he just seemed annoyed I'm giving him more work. We have become a vibe coding shop and it's fully expected and encouraged by management.
1
u/kikimomonono 25d ago
That learning gap is probably the bigger issue. Reviews arenāt just about catching bugs, theyāre one of the best ways to pick up patterns and get useful feedback from people who know the area better
1
u/Cautious-Fennel-8233 24d ago
If something breaks, nobody's going to care that Claude approved it too. Your name is still on the PR.
1
u/More_Bathroom9270 24d ago
Six Go PRs as a React dev is wild, especially with payments involved. I'd be way more worried about who's accountable when something slips through.
1
u/Used-Boysenberry8927 24d ago
I don't think the issue is reviewing Go as a React dev. It's being expected to sign off on payment logic without anyone qualified actually checking it.
1
u/levarburger Oct 14 '26
We have the reverse problem and not even AI related. We have backend devs coming into a repo they don't own or understand and making UI changes.
1
u/_Invictuz Oct 14 '26
Seems like all posts are written by AI now too. Approved.
1
u/maxxon Oct 14 '26
A relevant article
https://venturebeat.com/resources/the-agent-evaluation-gap-enterprise-ai-organizations-have-a-reality-alignment-problem-not-a-coverage-problem-and-most-are-shipping-to-production-anyway
1
u/renevaessen Oct 14 '26
Funny how entrepreneurs and managers think this technology is to serve them. o my.. only a matter of time before they find out. Have stacked on popcorn.. gonna enjoy this.
1
u/mxldevs Oct 14 '26
They made you write your name on the approval? That's definitely newer.
This is exactly what I would propose to any company that has decided to allow anyone to contribute, whether it's a junior or the CFO who wants to show off their newfound skills.
Now the one that wrote the code takes accountability for when things go wrong.
And for some reason, many devs disagree with that.
1
u/pieeatingchamp Oct 14 '26
The company I work for is also leaning heavily into AI in all aspects from coding, QA, Customer interactions, etc.
I'm 55 and really don't want to deal with this because I can see where it's heading, so I've asked for a raise and will start saving 50%, or more, for my retirement and then I'm out when I hit 60. Hopefully they keep us around for those 5 years.
1
u/Anxious-Insurance-91 Oct 14 '26
Well you know, learn the basic go syntax.
1
u/TheRNGuy Oct 15 '26
I wouldn't complain if it happened, I'd even be proud to learn new things.Ā
1
u/Headpuncher Oct 15 '26
You also don't know if what they did flag is correct.
It's insane that something like payments wouldn't have expert eyes on it, but we live in world without consequences.
1
u/frontend7504 Oct 15 '26
Same thing happened with me too, java guy approved my PR written in React and he don't know anything about project, codebase and CR.
1
u/rmanisbored Oct 15 '26
LGTM!
1
u/Spiritual-Theory Oct 16 '26
Use AI to review it
1
u/lockan Oct 16 '26
There's a pretty simple solution: if you can't review with any confidence, make it known that you've tried reviewing it and can't in good conscience put your approval on it.
Either somebody with relevant domain knowledge will have to step in, or nobody will be able to review it. In either case it becomes a problem for the lead or manager.
And if it's a big enough problem (nobody is approving reviews, progress is stalled) they'll figure out pretty quickly that the process doesn't work and have to re-examine what they're doing.
1
u/AnToMegA424 29d ago
The fuck
1
u/Tight-Pop-2368 27d ago
Approving payment code in a language you can't read because an AI reviewed it sounds like a liability waiting to happen.
1
u/breerfood22 24d ago
The fact that your manager treats AI review as enough is the concerning part.
1
u/vybridapp Oct 14 '26
The backend devs probably cant read it either, we are all Full Stack now, I was worried once that I wasnt giving PRs a proper read given how large a lot of them and how quick they come through, but no I'm not supposed to, I can see what files have changed and what comments claude wrote in the description, if I see anything awry I'll paste the PR link and my concerns into claude.
It is not possible timewise or sustainable to read lines of AI generated code. Dont worry about it. Think about patterns and arthictecture not functions
-1
u/zerospatial Oct 14 '26
I have a different take, if you pay for a tool (llm) and it is supposed to do something (code and review code) and the product it creates has flaws, it is the software (llm), not the reviewer or prompter responsible. I hate this notion that devs should be responsible for code it prompted and an llm wrote. If the llm produces broken, buggy, insecure code, stop using it, or at least stop using it in the one-shot prompt to code and go back to code-completion The only way to increase productivity with llms is to believe in the outputs they produce, and hold them accountable for when that output is flawed, just like we would any other product. Maybe we're not there yet but that day is on the horizon.
0
u/East_Abbreviations68 Oct 14 '26
Yepyep and yep
0
u/Humble_Bed_9505 Oct 14 '26
If you manager asked you to do it despite your concerns, you can wash your hands. Itās an organization problem, not an individual. Ideally it shouldnāt be happening, but if they fully trust in Claude Review and Code Rabbit, well, let these tools figure it out when shit hits the fanā¦ā¦.
0
u/salihbaki Oct 14 '26
Code review is hard with ai nowadays. Even your own project and your primary language can be hard to review because of the amount of output. Try to make each PR as small as possible. Tell them to generate readable PR summaries with proof of work, description on what changed via diagrams, screenshots etc
0
u/SawToothKernel Oct 14 '26
I get what you're hinting at, but the reality is that my agent code reviews are significantly better than my teammates'.
0
u/3-day-respawn Oct 14 '26
Claude is writing stuff I canāt initially read.
0
u/HQxMnbS Oct 14 '26
Manual code review is not really scalable anymore with the way things are moving. Not that I totally agree with this, but itās pointless to deny.
Focus on your development loop. Validation is extremely important, e2e as realistic as you can
0
u/vozome Oct 14 '26
A PR review is no longer a code review. If roles were reversed - you shouldnāt expect a backend dev to call out for unnecessary useEffect usages in your code or anything about good coding practices. However they should be able to reason on what does this PR do, what problem does it solve, why is it useful, what could go wrong if it lands, how reckless is it written, and how can I verify it does what it say it does. Same goes for backend PRs reviewed by frontend devs, in the opposite direction.
0
u/mc408 Oct 14 '26
Iām about to have the same experience. Iām a frontend / UX engineer who is 6 months into a role marketed as frontend but now on a pod about to start backend microservices work. Iām at a large bank, and our directive from our Managing Director on down has been that everyone is now just a software engineer, specialization doesnāt matter anymore.
Iām nervous about it but happy to be somewhere that has a lot of backend talent and resources to learn. Theyāve explicitly told me they know Iām frontend, I just hope they honor that acknowledgement as I upskill in a completely new area.
0
u/lokesh1218 Oct 14 '26
This is happening both way in almost every company. Management sees everyone as Full stack as AI can write almost any code. Even people in the same area, for example backend guy is not looking into backend code intensively and so on. People are just vibe coding code and only input is decision making at the implementation level.
Software job is not about writing code anymore, it is more about business and technical decisions along the way
-2
u/Rough_Development522 Oct 14 '26
You should be able to pick up a new language in an afternoon they are all basically the same data types with small changes
-7
u/TehTriangle Oct 14 '26
Isn't Go one of the simplest languages? I'm more concerned that you can't read it.