101–110 of 149 posts
Also check out https://usedouble.com (YC W23) if you're interested in using something like this today. Note: I'm the founder :) Happy to answer any questions. Reply below with some sample data/problem and I'll reply with a demo to see if we can solve it out of the box!
Just signed up. How long is the wait list?
> 0 day 7 hour 31 min 42 sec
I've never seen rolling waitlists, it's kind of strange tbh
GPT3 charges for every token read/written. What may be more useful is using GPT-3 not to manually run itself on every row, but to take the task and generate a sufficient function that fulfills the task.
GPT3 charges for every token read/written. What may be more useful is using GPT-3 not to manually run itself on every row, but to take the task and generate a sufficient function that fulfills the task.
Like with Stable Diffusion, maybe there will be an open model for the language prompts which less or no restrictions in the near future.
This particular example is an inadeqate application of AI. This is static data which can be looked up in a table (at least zip code).
The most sensible use for AI that I can see at this time is for supporting humans in their work, but only where the system is set up so that the human has to do the work first, with the AI system looking for possible errors. For example the human drives the car, and the AI brakes when it senses dangerous conditions ahead, or the human screens test results for evidence of cancer and the AI flags where it disagrees so…
Makes total sense to me.
The most sensible use for AI that I can see at this time is for supporting humans in their work, but only where the system is set up so that the human has to do the work first, with the AI system looking for possible errors. For example the human drives the car, and the AI brakes when it senses dangerous conditions ahead, or the human screens test results for evidence of cancer and the AI flags where it disagrees so…
That’s amazing. It does rely on a level of comfort with a fuzzy error budget.
Queue Fry "I'm scare-roused" meme...
Earlier quoted context omitted.
I've used/added the USPS API into a system and it took practically no time at all to do it. I'm guessing that is significantly less time than building an AI tool. What's worse is that the thing that takes the least time to implement actually provides good data.
Obviously adding the USPS API to your tool would take less time than building an AI tool. But the AI tool is infinitely more powerful for almost anything other than dealing with addresses. So the question isn't which one you can add to your tool faster. The question is, if I already have this AI tool setup, is it worth setting up the USPS API to go from 95% accuracy to 99.9% accuracy. For countless applications, it w…
If having something like the zip code not be accurate, then what's the point of having the zip code in your data? People writing code to store zips/addresses are doing it to not not be able to send/verify/etc. They are doing so that the can, but if the data is wrong then they can't.
What countless applications that ask for a zip code/mailing address and don't need it to be accurate? I would then say that any that you name would actually not need the data in the first place. If your hoover it up just to sell later, wouldn't it be worth more to be valid? So again, I'm right back to why do you need it?
The 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…