THANK YOU. I’ve always felt this way about PR review. I feel like people should ...

nottorp · 2026-09-28T07:08:56 1790579336

A proper natural language description of the change without links to parts of the diffs is already advanced material.

And arguably if the description needs linking to parts of the diffs then the commit is too large?

jolaflow · 2026-09-28T07:29:06 1790580546

You might have use for an issue tracker I've been building the past year and a half. It lets you inspect diffs inline in the ticket, and replay the board to see how the workflow evolved over time via a timeline scrubber.

https://ljtn.github.io/epiq/

It stores issues as an immutable event log in your repo, so you can go back and inspect the context behind a change without having to litter the code with comments. Helps with traceability of intent.

Hamuko · 2026-09-28T05:58:02 1790575082

People in my team are generating long and verbose PR descriptions with AI. No idea why and for whom. I certainly never read any of them.

sfn42 · 2026-09-28T06:53:13 1790578393

Man I'm so sick of seeing 50-line PRs with 800 lines of AI slop markdown files included. I also don't read them.

bunderbunder · 2026-09-28T03:08:06 1790564886

This sounds like a fussier version of what Donald Knuth was doing with literate programming.

Which, incidentally, is a really enjoyable way to work.