News for hackers. Stuff that matters.
Re:Becoming a Better Software Developer: A Handbook on Perso... by Fellshard on Thursday September 20, 2018 @03:28PM (#18034885)
I've been wondering if it would be useful to have tools that help build better narratives for proposed changes. Which files should be viewed in which order? How do the changes tie together?

It's not quite literate programming - the commentary would have to be interwoven with the code, but it's not permanently attached to it.

Existing comment systems usually approach the interwoven change and commentary alright by interleaving comments into the diff, but they still don't allow you to choose which files or diff chunks are displayed in which order.

Re:Becoming a Better Software Developer: A Handbook on Perso... by btasovac on Friday September 21, 2018 @08:42AM (#18039241)
Thanks for sharing this idea! We have a similar issue regarding this [1], so please feel free to engage in the discussion there and bring some attention to it. We'd love to hear more from you on this matter!

[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues/18037

Re:Becoming a Better Software Developer: A Handbook on Perso... by JohnBooty on Thursday September 20, 2018 @05:44PM (#18035708)
I'd never thought of that. That's brilliant. I agree: it'd be nice to somehow control the order in which the diffs were presented to the reviewers!

This would IMO be a killer feature for Github or Gitlab to implement.

Typically, I explain complex PRs "manually" in the PR itself or by screen sharing them with the other devs, but this is not always very efficient.