dshacker

You're absolutely right - this is not X, but Y.

----

I'm absolutely tired at work on how many people are writing with em-dashes with obvious AI prose. I feel a little bit insulted but then I remember we all participate in this charade.

I'm not sure how to prove otherwise, but this actually happened to me. I don't understand this kind of comments saying "FAKE" for views or blog-posting. This is something that happened to me, and I can say for sure people were really pushed in this situation to ship faster every time.

It really demotivated me when this happened, I just kept seeing the PR open, but then I saw the changes applied before the PR was merged, which made me very confused. I then had an alert placed on every one of the updates made by Mike to make sure he didn't do this again. People were against "reset reviewers on commit" for "agility".

I think people can be in hard conditions, needing a job, under pressure, burnt out and feel like this is their only way to keep their job. At least that's how it felt with Mike.

At the end, I spent a lot of time sitting down with Mike to explain this kinds of things, but I wasn't effective.

Also, now LLMs empower Mike to make a 1600 line PR daily, and me needing to distinguish between "lazyslopped" PRs or actual PRs.

I mean, there are some exceptions on when 1600 PRs are acceptable (Refactorings, etc) but otherwise agree.

What really bugs me is that today, it is easier than ever to do this (even the LLM can do this!) and people still don't do it.

Thanks! Fixed.

Right, I think there is always a balance between being strict on code reviews, and just letting people ship stuff. I've also seen the other end of the stick in which a senior employee is blocking an important pr over "spacing".

To be honest I'm not a native english speaker, so I might be using words wrong.

Thanks for sharing!