// Here I'm not using that other thing that is now completely irrelevant, but I'll leave a comment to the non-existing thing anyway because I'm avoiding it.

That's because they haven't.

Try working on a codebase that's all event-driven hexagonal CQRS with hand-crafted SQL for persistence. Add additional buzzwordy methodologies to taste.

Adding a single property to your product means you now have to update an aggregate class, several DTOs, and several event classes and handlers before you can even think about touching the UI.

And that's in your main solution. There's also at least one facade service you'll need to make compatible and you also need to update the event simulator used for testing. The latter night involve having to touch every single line in a 2000 lines long SQL script.

Having to go though three separate 600-2000 LOC PRs for one PBI isn't that exotic.

I've completely banned any code that can't be explained. I've had my CTO send me code at 3 AM to implement and when I ask him what I'm looking at he just says it doesn't need review, just push it.

Uhh, no sir, I'm not doing shit because you've handed me GCC and we're MSVC.

After I bitched endlessly to the CEO about that he said I have final say on what goes into the project.

I fully expect this to become the new normal being pushed by management.

"We identified PR reviews to be blocking our newfound AI-powered efficiency, so we are now mandating all the reviews to done by AI. Also we figured all the developers are now useless since all you do is ask Claude to solve tickets, so you are all fired"

I wonder how long it takes for the first high profile disaster happening because of a policy like that.

Almost as if they're paid by the token...

Let's Go Topple the Monarchy!

Let's Gamble, Try Merging is my favourite

"So, Daywim. Why did you let this obviously aweful PR pass your desk causing so much trouble for our company? I'm afraid we have to let you go because of this questionable performance." - Corporate

is it auto reject, or just doesn't auto approve and leaves it open for manual review

It seems weird that you can't do a pr at all with 1000 line changes, any moderate size feature addition could hit that mark

The most important question that every change must answer.

The goal of AI providers is to make humans unable to maintain code, so you have to rely on their expensive subscriptions and tokens.

It's basically saying "insert one ass loads of code in one go, all written by AI".