4 ms·
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 concept
by namanyayg 11mo ago
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.
- Paracompact 11mo agoExactly my thought. Can anyone here say otherwise?
- collingreen 11mo agoI didn't have any trouble with the comic but I do already know these things about how react hooks work so I'm not going in fresh. 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.
- continuational 11mo agoI think this kind of slop has negative value. It's unclear how much of the information in the comic is hallucinated, and the malformed code "for i = i1+|>" and nonsense text "(starts write hooks!" doesn't bode well.
- vunderba 11mo agoDefinitely still needs a "human in the loop." I don't know if this particular comic was cherry-picked or if it was the first one generated by Nano-Banana Pro, but either way, it's still got plenty of messy typos. RULES OF HOORS? Updste #2: setState Starts wite hooks!
- cholantesh 11mo ago>Definitely still needs a "human in the loop." At which point I feel like I would rather the human have invested their time into writing a design doc that we could discuss well before they submitted a PR.
- itronitron 11mo ago>> the given example comic makes very little sense. I thought that was just due to it being about React.