I’ve been experimenting with a way to make code reviews more understandable - turning tricky pull requests into short comic strips.

The blog post shows an example generated from a real PR: summarizing the changes, anthropomorphizing the components, and making the flow visually obvious. It’s meant to help reviewers grasp intent quickly and make reviews a bit more fun.

Curious whether others have tried visual or narrative aids in their review process, and whether this could be practical for real teams.

This could be a fun way to educate the judge about why my opposing counsel's position is laughably wrong.

Sadly, the fun would end with a reprimand or sanctions order. Cf. https://news.ycombinator.com/item?id=43866303 ("Don't watermark your legal PDFs with purple dragons in suits").

Might work for bringing associate attorneys up to speed in a new case, or for teaching concepts to law students, though!

I'm not against it, but this particular strip seemed a little incoherent. It might need manual storyboarding.

Using visual approaches, including comics, is a reasonable idea I've been looking into personally as well (mostly using style transfer from manga). :)

But, the actual concepts communicated need to be clear. In your example strip here, it doesn't seem to be meeting that bar for a reviewer. :(

Keep at it though, as I get the feeling this is the kind of thing that will work after a few important "aha!" ideas and tweaks happen to the generating process. :)

I really like the idea... but I have to admit my first visceral reaction was "I hate this". I think it's because the tone and style is quite infantile/childish. A good experiment nonetheless. Maybe there's a middle ground somewhere?

I think it’s a fun idea.

Not sure if it would be used, though. Being on HN front page helps.

It would also have to contain a lot of content, and be indexed well.