

Here’s the thing… code is much closer to doing group therapy than it is to flipping burgers. The final produced artifact is somewhat less important than converging on the tiny itty-bitty details of how to collaborate on the journey of getting there. This is especially true for open source projects.
Spending time trying to understand the perspective of a chatbot-managed contributor is a waste of time. You’re not going to be able to build a community around having a good developer experience for doing XYZ if half of the people weighing in on “how to do that” are not developers who are directly experiencing the thing they’re poking at.
Edit: Also, on testing specifically… this is something I see teams get wrong all the time. The real value of a test suite is not from making sure your system works correctly, but from making sure it’s easy to inspect how your system works. If it’s hard to write or modify tests, that’s an indication that you’ve got some unwieldy abstractions floating around. LLMs don’t care about whether the friction of test-writing is increasing.














Don’t trust internet strangers to weigh in on this. Talk to a therapist or someone you trust to thoroughly consider the details that you haven’t (and shouldn’t) share here. Without the details, we’re just guessing, but even then a single post-and-reply exchange is not a good substitute for a full IRL conversation.