it’s pretty good for things that I can eye scan and verify that’s what I would have typed anyway. But I’ve found it suggesting things I wouldn’t remotely permit to things that are “sort of” correct.
Yeah. I haven’t bothered with it much but the best use I can see of it is just rubber ducking.
Last time I used it was to asked how to change contrast in a numpy image. It said to multiply each channel by contrast. (I don’t even think this is right and it should be ((original value-128) * contrast) + 128) not original value * contrast as it suggested), but it did remind me I can just run operations on colour channels.
Wait what’s my point again? Oh yeah, don’t trust anyone that can’t tell you what the output is supposed to do.
sugar_in_your_tea@sh.itjust.works 5 months ago
I just don’t bother, under the assumption that I’ll spend more time correcting the mistakes than actually writing the code myself. Maybe that’s faulty, as I haven’t tried it myself (mostly because it’s hard to turn on in my editor, vim).
IHeartBadCode@kbin.run 5 months ago
Nah perfectly fine take. Each their own I say. I would absolutely say that where it is, not bothering with it is completely fine. You aren't missing all that much really. At the end of the day it might have saved me ten-fifteen minutes here and there. Nothing that's a tectonic shift in productivity.
sugar_in_your_tea@sh.itjust.works 5 months ago
Yeah, most of my dev time is spent reading, and I’m a pretty fast typist, so I never bothered.
Maybe I’ll try it eventually. But my boss isn’t a fan anyway, so I’m in no hurry.
SkyeStarfall@lemmy.blahaj.zone 5 months ago
It can be useful in explaining concepts you’re unsure about, in regards to the reading part, but you should always verify that information.
But it has helped me understand certain concepts in the past, where I struggled with finding good explanations using a search engine.