Lee Duna@lemmy.nz to Technology@lemmy.worldEnglish · 7 months agoMicrosoft's Pricey AI Assistant Copilot Leaves Early Adopters Feeling Cheatedwww.ibtimes.co.ukexternal-linkmessage-square12fedilinkarrow-up15arrow-down10
arrow-up15arrow-down1external-linkMicrosoft's Pricey AI Assistant Copilot Leaves Early Adopters Feeling Cheatedwww.ibtimes.co.ukLee Duna@lemmy.nz to Technology@lemmy.worldEnglish · 7 months agomessage-square12fedilink
minus-squarelemmyvore@feddit.nllinkfedilinkEnglisharrow-up0·7 months ago Copilot isn’t actually bad for developers, it’s just that you need to be careful with it and recognize its limitations. Is it me or is this a weird statement for what’s supposed to be an exact science? Imagine working in construction and using a level and you’re told “it’s not that it’s a bad level, you just gotta be careful with it”. How much margin for error should we allow for getting our code right? Is it now acceptable if we only get 80% right?
minus-squarekescusay@lemmy.worldlinkfedilinkEnglisharrow-up0arrow-down1·7 months agoIt’s more like you get some kind of weird construction multitool that promises to be a level, a drill, a hammer, and a dozen other things, and it turns out to be a really good, innovative, and helpful level… and a really bad everything else.
Is it me or is this a weird statement for what’s supposed to be an exact science?
Imagine working in construction and using a level and you’re told “it’s not that it’s a bad level, you just gotta be careful with it”.
How much margin for error should we allow for getting our code right? Is it now acceptable if we only get 80% right?
It’s more like you get some kind of weird construction multitool that promises to be a level, a drill, a hammer, and a dozen other things, and it turns out to be a really good, innovative, and helpful level… and a really bad everything else.