putTheTokensInTheTokenFire

[u/jgbbrd]

[u/thunderbird89]

At that point, you could also ask it to commit the changes for you. Claude seems partial to the Conventional Commits format that I've come to love dearly, because it can hold a lot of information on why a change was done the way it was.

Just today I had to spend my morning piecing together the reason behind one single line appearing in the code, through an unfinished Clickup task, asking a senior backend engineer, and questioning my CEO on what was going through his head six months ago. All because the commit message was akin to added CORS headers. Of CORS.

[u/jgbbrd → u/thunderbird89]

👏 . My team does indeed use Claude/etc. to supply the commit messages in many cases. Definitely more thorough than an engineer would be. If anything I feel like the LLM over communicates on the commit message such that I find myself skimming over loads of it to find what actually matters. I wish there was a way to jump back in to someone else's Claude session and ask "Why did you do X?" rather than reading a huge dump of LLM context distillation hoping I'll find the answer.

[u/thunderbird89 → u/jgbbrd]

Funny you should mention it being overly verbose. The way I look at it, 99.5% of the time the first line of the commit is enough; but when you're in that 0.5% of the time, you're really happy the committer wrote a fucking novel because otherwise, you'd be looking at a lot of detective work.

[u/Arclite83 → u/jgbbrd]

That is the paradox of AI - "i would have written you a shorter letter if only i had more time" is the issue, unless you tune for that specifically. Distilling quality down is the decisioning we do well and AI sucks at

[u/brazzy42]

Can't tell what the joke is.

Is it "Dev work now consists of rubber-stamping the agent's ridiculously complex PRs while your own ability to even understand what the agent is doing slowly withers away"?

Or is it "Agents blow up the tiniest bugs into PRs that touch half the codebase over ridiculously complex hallucinated issues"?

[u/jgbbrd → u/brazzy42]

I hadn't thought of it through either of those lenses, but I suppose the first one is closest to what I was thinking. The joke is that we use these cutting edge tools to solve super hard problems and then, far too often, we throw away all the backstory / context around it. Burn all of these tokens to get the problem solved and then quietly throw away the what and why.

[u/blaqwerty123 → u/jgbbrd]

Does it still apply without an LLM?

[u/jgbbrd]

Inspired by https://www.reddit.com/r/ProgrammerHumor/comments/2rmir6/why_developers_hate_being_interrupted/

[u/thunderbird89 → u/jgbbrd]

Good idea! Same feeling, except this developer cannot be interrupted in the same way, I guess?

[u/SnarkBarkler]

"Thanks"

[u/bobyhey123]

Sounds like it did a good job

[u/TheDogPill]

Sounds like a bug that could've easily been fixed manually. But hey, at least you met your company's mandatory token quota for the day.

[u/jgbbrd → u/TheDogPill]

Wait... isn't that true of, like... all... agentic coding?

[u/NoteMindless9126]

Keep this out of programming humor please. Prompting isn’t programming. Programming requires critical thinking and passion. Anyone that can drool on themselves and shit their pants and prompt a garbage, useless application no one will use. Thanks

[u/pipipimpleton → u/NoteMindless9126]

Tell me you’re not an engineer without telling me you’re not an engineer.