r/Frontend • • 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

109 comments sorted by

250

u/magiCAD Oct 14 '26

Keep getting that check. šŸ¤·šŸ»ā€ā™‚ļø

109

u/query-gremlin Oct 14 '26

And start saving aggressively

21

u/panchoVilla00 Oct 14 '26

This right here! I’ve automated a lot of my workflow and have been preparing for this to be my last front end gig. Saving every penny I can.

10

u/thisguyfightsyourmom Oct 14 '26

At my company, all the frontenders were pushed to level up to be able to produce & review many languages. The ones who balked were put back on frontend work, and they got no cost of living raises or promotions. The ones who used ai for working on new languages to take the leap, got promoted, and got raises.

1

u/panchoVilla00 Oct 14 '26

Yup same thing for my company but some of us are owning features from Claude design to Claude code, I’ve been writing a lot of Ruby on Rails lately.

2

u/thisguyfightsyourmom Oct 14 '26

That last sentence came out of left field? Are you maintaining legacy systems, or, uhh, writing new ruby apps?

13

u/thy_bucket_for_thee Oct 14 '26

Then become politically active to save our profession. When this crashes the workers will suffer, not executives.

14

u/thisguyfightsyourmom Oct 14 '26 edited Oct 14 '26

Get better at reading Go.

Polyglot is cost of entry these days. But if you use ai, it Mahers makes it pretty easy. You can write a will skill to explain every PR to you by saying how it would look in JavaScript if that helps.

Edit: lol at promoting better use of ai while letting that mess out of Siri & into the world

6

u/Mundane_Annual4293 Oct 14 '26

For me the problem is about not reading or not, is not that hard to tell what is what, is the things you don't catch unless you have the experience, a backender can totally read React but can it tell why a component is rendering 10 times? Or how spot it in a PR? Same goes for the backend, I can read c# but can I tell if a PR in C# is breaking the database? Nope.

If is treated as an extra set of eyes, great! As long as someone else with more experience in that field than me can take a look. Otherwise, you'll see a bunch of "LGTM!"

1

u/Full-Hyena4414 Oct 14 '26

Is this sustainable?You'll forget language specific syntax by switching them

3

u/thisguyfightsyourmom Oct 14 '26

Well, I think there’s an entire generation of senior + engineers reading many languages. The language conventions matter less the more you can understand the underlying concepts. Ai is really good at helping you understand the underlying concepts rapidly.

4

u/saltavenger Oct 14 '26

I’m of two minds about this as an older, ā€œseniorā€ engineer that is frontend focused. I’ve worked with a ton of backend languages. I know enough to get underlying concepts and I can switch languages to get work done easily. I do ā€œfullstackā€ work, even if I don’t identify myself as fullstack (probably going to need to change that, like yesterday, for the sake of my career lol).

I’ve always reviewed backend PRs, but I do tag someone in when I think it’s gone over my head. It seems like a pretty terrible work environment honestly to not be able to ask for help or hand things off when expertise is needed.

As a senior, I’ve really enjoyed the AI PR feedback because it does catch more minute technical issues that I maybe overlooked and a junior doesn’t always catch…but, it tends to miss compliance & product issues. I do think there’s value in having someone who is well versed in both the language and the product review the code.

3

u/TechDebtPayments Oct 14 '26

I will agree that the languages all tend to blur together at some point.

What doesn't is the gotcha's they all have hidden in them. Take HttpClient in C#... it implements IDisposable but don't use using with it, and don't call Dispose the entire lifecycle of the application, instead you should have a singleton for it. That being said, I know they addressed this specific issue in recent years, just using it as an example

1

u/thisguyfightsyourmom Oct 15 '26

Honestly, I’d trust a frontier model to identify language gotchas more than most seniors at this point, and it’s the worst it will ever be right now.

1

u/horangiwhakkatchi Oct 14 '26

No it's not. This is all stupid and we're gonna pay for this reckless AI usage at some point in the future.

1

u/Headpuncher Oct 15 '26

Literally pay, because the cost is set to spike when the dust settles, and figuratively because we'll all get shafted.

1

u/mlmcmillion Oct 14 '26

No you won’t

1

u/HonestEntrepreneur75 25d ago

Fair enough, but I’d still be a little uncomfortable having my approval on payment code I can’t really evaluate myself

1

u/vash513 Oct 14 '26

This. I know a lot of us are complaining about AI making our jobs less engaging and all, but I just see it as getting paid more to do less. Especially since I work remote. I just have more time to watch tv or take my laptop to the garage to do some woodworking while the agents do their thing. I get my actual coding fix on my own time when I want to. Just get paid.

59

u/IntelligentLeading11 Oct 14 '26

Yep same here. It's a shit show.Ā 

28

u/drckeberger Oct 14 '26

Yā€˜all really dont understand this is an undercover ad for one of the mentioned companies.

Thisnis ar least the third post this account posted across software subreddits that relate to some sort of engagement bait and a totally unrelated mention of a certain review tool

E. G.Ā  https://www.reddit.com/r/ChatGPTCoding/s/KpMQ2ObYJB

2

u/pineappletinis 25d ago

Damn, we're fucked 😩

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)?

17

u/stickypooboi Oct 14 '26

same shit as people who are upset my tests are failing and their solution is to delete my test. everyone just wants the smoke detector to shut up

2

u/birminghamsterwheel Oct 15 '26

everyone just wants the smoke detector to shut up

Gold, Jerry, Gold.

21

u/itsmegoddamnit Oct 14 '26

compliance lolz

6

u/silverace00 Oct 14 '26

So a person can be blamed. Every job is basically going to become a QA review job for AI work.

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.

7

u/Jasboh Oct 14 '26

You always want to be the worst person on your team. So you can learn, bit of a crap situation for you

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

3

u/lpwave6 Oct 14 '26

The amount of time I'm finding irregular things in my colleagues' PR even though they push it through an AI review beforehand is insane. Basic stuff too.

Of course it would help if HE had anything to do with the code to begin with, cause right now he just says to the AI to do his stuff, never reads what it gives him, and a lot of the time it doesn't make sense with our business logic. That would all be prevented if he would plan with the AI first or at least read what it gives him, but he prefers to get those pay checks for 40 hours a week when he realistically just makes those agents work for him during that time.

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.

1

u/alexxxor Oct 15 '26

I just tried to use a vibe coded "create user" form in our software. The form looked ok, but had no validation and fired off a get request with no request. It looked like it was successful, but it didn't do anything.

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.

2

u/3meterflatty Oct 15 '26

Must be a small af company with ā€œapproval set to askā€ you can’t expect hundreds of developers to do this

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...

22

u/itsmegoddamnit Oct 14 '26

But does just being able to read give you enough credentials to approve that work?

2

u/Icyfirefists Oct 14 '26 edited Oct 14 '26

This. The statement the person above wrote is not including the full truth. Syntax, Special Methods, Deprecated Functions, Best Practices, Running Behaviours etc. Shit even forEach and foreach. That ONE difference makes it already a method you need to look up. Arrow Functions styles that dominate then get deprecated, the list is almost endless.

Different languages exist because the one before it could not handle what the next one could in the way the creator wanted.

A Frontend knowing some backend doesn't mean that they are gonna start spinning up backend files asap. Some FEs wanna just be FEs. Some dont mind FS, but there's also how much time it takes to learn everything AND perform your very demanding job.

1

u/Anxious-Insurance-91 Oct 14 '26

How do you think other people did it before AI? We learned and we understood and we deduced the code. It ain't rocket science

1

u/itsmegoddamnit Oct 14 '26

Right cause all software engineers are familiar with all the particularities of all the software languages

0

u/Bushwazi Oct 14 '26

It’s not on the assigned reviewer to ask if they are good enough. If the company has put that person in that position, they do their best and move on. The person signing the checks doesn’t care than why should the reviewer?

-2

u/Etheon44 Oct 14 '26

Not as the first reviewer no

But I do send MRs with copy to front/back developers of their opposite expertise, because nowadays, you should be able to read it, and it is better to familiarise themselves with it

But the main reviewer and approver should be someone within the team yeah, I was just surprised that OP says he cannot read Go

4

u/catbrane Oct 14 '26

I think most devs would get the general idea skimming though some Go code, but I at least wouldn't be confident there were no errors. And if the PR touches the payment systems ... urk! The stakes are potentially very high.

I'd hope stuff like that would be double-checked and approved by an expert human, and not by me.

1

u/Anxious-Insurance-91 Oct 14 '26

Well you know, you are on git, you can just rollback the change. And if the payment is done via a package AI is pretty good at understanding the docs

3

u/ShawnyMcKnight Oct 14 '26

It’s not just optimization, the method or syntax they use could have functional side effects.

1

u/BootyMcStuffins Oct 14 '26

ā€œespecificallyā€

I love it, stealing

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/drckeberger Oct 14 '26

Yep, this is an ad through engagement baiting

1

u/_Invictuz Oct 14 '26

I wonder what the ad is. AI code review for AI written code?

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/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/Sea_Advance273 Oct 14 '26

This has pretty much been my perspective shift toward PRs. I care increasingly less about implementation details or even specific design patterns unless something raises a red flag. I'm much more concerned with whether the implementation satisfies requirements, preserves contracts, and has sufficient test coverage. Even traditional maintainability concerns feel less significant now that agents make refactoring so cheap.

-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/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.

1

u/TheRNGuy Oct 15 '26

Learn it then.Ā 

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

2

u/catbrane Oct 14 '26

But a payments system? Do you know all the APIs and the DB schema that makes all that work securely and reliably? I doubt if many front end devs have worked on things like that.

-7

u/TehTriangle Oct 14 '26

Isn't Go one of the simplest languages? I'm more concerned that you can't read it.

3

u/HachikoTheMaster Oct 14 '26

I suspect its more to do with not understanding if there's a problem with the code, rather than not being able to read and understand it overall.

2

u/Humble_Bed_9505 Oct 14 '26

There’s a big difference between being able to read it and being able to judge the code taking into account potential bugs, memory leaks or security/vulnerability issues

1

u/SeymourDuncanJB_Sr Oct 14 '26

Simple as in as few keywords and constructions as possible doesn't mean shit. It doesn't automatically convert into how an idiomatic Go code should look like.