"I tried parsing your messy input. Here's what I came up with. Please make sure it's correct then proceed with the checkout."
Demo of =GPT3() as a spreadsheet feature
21–30 of 149 posts
Re: Demo of =GPT3() as a spreadsheet feature
#22"lack of dark mode" should be "features" not "usability"?
Re: Demo of =GPT3() as a spreadsheet feature
#23Of all the places spreadsheet is probably the one place you don’t want AI generated content. Half the time it’s financial info so sorta correct simply isn’t good enough
I was going to say: This can only end well for the economy... /s
Re: Demo of =GPT3() as a spreadsheet feature
#24From one of the replies: “This is awesome. I also love how 20% of the zip codes are wrong. Messy AI future seems really fun and chaotic.”
So of course a human developer made an AI that makes bad data.
Re: Demo of =GPT3() as a spreadsheet feature
#25"lack of dark mode" should be "features" not "usability"?
And for the second Kindle review, it summarized one point from the actual review, then completely made up two additional points!
Really impressive Sheets extension, but you'd have to be so careful what you applied this to.
Re: Demo of =GPT3() as a spreadsheet feature
#26The amount of 90% sensible, 10% ridiculously wrong computer generated crap we’re about to send into real humans’ brains makes my head spin. There’s truly an awful AI Winter ahead and it consists of spending a substantial amount of your best brain cycles on figuring out whether a real person wrote that thing to you (and it’s worth figuring out what they meant in case of some weird wording) or it was a computer generat…
Re: Demo of =GPT3() as a spreadsheet feature
#27The ability of language models to do zero-shot tasks like this is cool and all, but there is no way you should actually be doing something like this on data you care about. Like think about how much compute is going into trying to autofill a handful of zip codes, and you're still getting a bunch of them wrong.
Better one would be "based on these three columns, generate a cold outbound email for the person..."
it would suck to be on the receiving end of those, but the use case makes much more sense.
Re: Demo of =GPT3() as a spreadsheet feature
#28The amount of 90% sensible, 10% ridiculously wrong computer generated crap we’re about to send into real humans’ brains makes my head spin. There’s truly an awful AI Winter ahead and it consists of spending a substantial amount of your best brain cycles on figuring out whether a real person wrote that thing to you (and it’s worth figuring out what they meant in case of some weird wording) or it was a computer generat…
The software would save people 80% or the work and most are lazy enough to release it as is, instead of fixing the remaining 20%. That laziness will end up forcing legislation to flag and eventually ban or deprioritize all GPT content, which will result in a war of adversarial behaviors trying to hide generated stuff among real. Can’t have nice things!
Re: Demo of =GPT3() as a spreadsheet feature
#29The amount of 90% sensible, 10% ridiculously wrong computer generated crap we’re about to send into real humans’ brains makes my head spin. There’s truly an awful AI Winter ahead and it consists of spending a substantial amount of your best brain cycles on figuring out whether a real person wrote that thing to you (and it’s worth figuring out what they meant in case of some weird wording) or it was a computer generat…
Re: Demo of =GPT3() as a spreadsheet feature
#30From one of the replies: “This is awesome. I also love how 20% of the zip codes are wrong. Messy AI future seems really fun and chaotic.”
The hilarious one is changing the zip code to 90210. The AI basically accusing you of a typo because you obviously meant that more famous zip code.
General purpose AIs in situations where more targeted, simpler solutions are needed are going to be incredibly dangerous. Sure this AI can fly a plane 99.999% of the time, but every once in a while it does a nose dive because of reasons we cannot possibly understand or debug.