> I think nobody would accept their manager being an LLM

this depends heavily on what is easier to do: social engineering or prompt engineering.

this isn't uniquely pythonic and JS isn't a great counterexample.

https://nodejs.org/api/esm.html#importmetamain

node also has __dirname and __filename from the good old days.

the frontend team can write a BFF to make all pages render server-side. there is an advocacy group for keeping oauth2 clients out of browsers which gives this idea some _political_ merit. in ways more than one, SPA is not the only solution when a dedicated _frontend team_ is employed.

The separation of teams happened before the BFF pattern came into existence so all frontend engineers became specialists in frameworks like React. Unless you can do it with React, FE's won't touch a BFF or anything else for that matter.

what is often overlooked in corporate culture: if you take a step back, two coworkers refusing to cooperate, regardless of the reason, is a typical "corporate kindergarten" scenario for the manager to take care of.

To avoid rushed or incorrect decisions, conflicts intentionally move through gradual escalation. If someone behaves unprofessionally, for example by submitting a code review they do not understand, the first step is to establish the likely cause.

They may ultimately be at fault, but that does not absolve the surrounding environment. The culture may be toxic, deadlines unrealistic, or communication poor.

The best course of action for someone directly affected by uncooperative coworkers is to avoid assuming ill intent. Get them on a call and let them explain their pull request, however trivial the issue may seem. Even if the gesture is misinterpreted, you still have a far stronger position than righteous indignation.

This, I totally agree with you having a call and letting them explain the changes. One of my coworker used claude to write and push PR's and the message was so cryptic, it's not really understandable. I got him on a call and let him explain the PR. He also actually couldn't really interpret the PR message. I warned him not do this again. Now he writes by hand. I think communication between humans should be written by only humans. AI is not really good at communication.

That here.

I once worked in a place where a guy would pick on me in code reviews, he wasn't really higher position, but had been with the company longer than I was.

He was just an asshole asserting his dominance and needed to be taken a notch down by a manager and it turned out he didn't understood (or more likely didn't try to understand) the PR when confronted.

You are absolutely right to push back...

this is a great comment.

(name doesnt check out though)