[bigiain]

I (mostly) welcome _people_ writing medium to long form emails, slack posts, and pull request comment (and the like).

What really grinds my gears is when the clearly desired response is a few words or a single sentence, and what I get is a link to an obviously llm generated 3 page pdf full of em-dashes and emoji bullet pointed lists with very little relevance or context about the question.

If I wanted Claude or ChatGPT's response, I would have asked them. If I'm going to bother a cow orker with a question, it's because I want domain specific knowledge or workplace experience that might be important.

I'm more and more often internally reacting with "if you didn't bother writing it, I don't need to bother reading it".

I would welcome your 30 min or half day turnaround with a well written and thought response, over lazy/disrespectful colleges who are just doing the instant 2026 version of "just fucking google it".

[munk-a]

Hey, speaking of gear grinding - have you run into LLM generated comments? I have always loathed JavaDoc and friends as I think it encourages vapid space filling comments that are inherently knowable from the code - when it's connected to a renderer (as was the original JavaDoc) so that the comments can be exposed without the code that is fine-ish - it serves a purpose and I can comprehend the rational but in most cases I've seen those comments committed without any intent to ever render them separately.

In the modern world we've got comments written by LLMs because "You've got to write a comment, of course, it's required!" but now the actually significant comments (the Why comments - as opposed to the What ones) are lost in a sea of LLM slop so no one will read them. Considering it'd be just as easy for the reader to point a conversational LLM at the codefile if they want the LLM interpretation of what's happening why are we bothering committing it at all?

Gosh that really grinds my gears. It's definitely a tangent but that being encouraged is a huge red flag for me.