True, but not in the way you're thinking.

How far does a million tokens go?

Well, perhaps we will be sent similarly to asylums for "anti-AI psychosis"

As if meetings weren't bad enough already, I now have to sit through an informal introduction to the model of the week and its personality characteristics and how quickly it burnt through one subscription's token allotment or whatever and the latest tweaks on the magic markdown files. Luckily I've only had a couple changes sent my way so far, which weren't much different than just getting a bug report to debug and fix myself. I will need to get into risky options gambling or something so I can go start my farm early, if it keeps going this way. Even supposing it all works correctly, I don't see how it is in any way enjoyable, satisfying, or fulfilling.

There's a constant "need" to churn UI revamps, so I guess eventually you run out of ideas before cycling around.

So, how many are getting paycuts this year? Things aren't/haven't ever been suited for me to be a job hopper, and as always that seems to be the only way to have your salary meaningfully keep up with inflation.

When you feel they are toxic or harassing you and you don't want to deal with them anymore. If you're overwhelmed, say that you're busy and will attend to issues and PRs when you have the time. If you want to be accommodating, have good build instructions or action workflows so that people can easily fork and build it themselves.

If you ask me, LLM-generated things should just be banned outright, but I suppose other people's definitions of "community" include them.

> If you ask me, LLM-generated things should just be banned outright,

Why? In the end it's a patch's quality that counts. Regardless who or what contributed it.

Bad patch from trusted contributor is still a bad patch.

Perhaps this is more a management problem. How to best use developer's time, where to use AI (vs blindly deploy AI to generate patches & swamp developers with that).

Or do some rate-limiting? "Sorry, we accept no more than 10KB worth of patches per week on this project! Try again next week after we've reviewed this week's batch".

> Why? In the end it's a patch's quality that counts.

LLM patches tend to be significantly harder to review. Mostly because LLMs let people who don't know what they are doing get much further.

It might be an unfair heurestic as there are plenty of competent people who use it to good effect, but the vast majority of negative value patches use LLMs and it can be a bit exhausting. Lowering the technical barriers of entry just means more pressure on the human ones.

> Why? In the end it's a patch's quality that counts. Regardless who or what contributed it.

You just said: The things that I think and care about matter more than the things that you care about.

is that what you meant?

Being honest, if we're talking about the health of any given project, the patch quality doesn't matter that much. Not when you measure it against the importance of consistency and continuity of a regular contributor. A thousand perfect LLM patches are less valuable than an experienced maintainer.

If your LLM is annoying them, and they quit. The perfect LLM patch just destroyed the repo.

People wasting others time is a social problem, not a technical one. Rate limits can't prevent somebody feeling disrespected.

It's a bad signal. Someone who is lazy and using an LLM was probably too lazy to do another number of things you want a contributor to do.

No, it means that Google will be held liable for false or libelous information it provides to users by means of generative AI. It's not banned. Of course, if Google decides that its generative AI produces too much false or libelous content, it may choose to stop doing so in Germany, where it will be held liable for damages it causes.

Ah, I had that realization too. Then I started writing short emails and they still didn't read them.