11–20 of 37 posts
Earlier quoted context omitted.
It's valuable to make a difficult task easier, even for those who could do the task without the help.
I'd rather just have a high-level summary in English for that. This seems to take dumbing-down beyond any sensible level.
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 narrat…
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 narrat…
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’ve been guilty of injecting bits of whimsy, sarcasm, and other unserious behaviors in a corporate We Mean Business environment.
I’ve toned it down because I recognize some people are very resistant to seeing both the serious and humorous aspects of a situation at the same time.
I asked it to generate a comic for https negotiation over tcp https://imgur.com/a/0p0Pzum I think with a bit more prodding it might be interesting for documenting protocols
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 narrat…
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’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 narrat…
Interesting idea but unfortunately the given example comic makes very little sense. It was difficult to parse even as someone who's familiar with these concepts, and I think it will hurt more than help any newbies.
Interesting idea but unfortunately the given example comic makes very little sense. It was difficult to parse even as someone who's familiar with these concepts, and I think it will hurt more than help any newbies.
Exactly my thought. Can anyone here say otherwise?
I think it's a little whimsical, perhaps too much for what info it conveys (a bullet list with the same component names would probably be equally informative), but I thought it was easy to understand and follow. I think there is -something- here; I don't need THIS comic but if it was more about the context and goals of the change then maybe that would be powerful. Especially if it was consistently done over many PRs.