Pt3 - parse + store columns
Because I have no clue about the structure of the output from users (also because I'm too lazy to write the parser code) I'm punting it to gpt4 to do the work.
Hit a few snags — outdated OpenAI documentation, CORS issues + JSON structure issues 5/10
Pt2 — submit columns
I really wanted to reduce friction and ensure accurate data during this step. Other AI sql apps make you upload a comma separated list (lame).
Instead I give the user a query to grab columns and dtypes and have them paste the ouput. It sorta works 9/10
@mikebeckhamsm Awesome to hear, Mike. Love the idea of a doing a bible chapter per day. Might need to steal that idea.
Which audio version of the Bible do you use?
NOOOOO. My Spotify discover weekly playlist is now ruined.
My wife and I have been playing baby lullabies via Spotify on our echo during kiddo's bath time and now Spotify is trying to put me to sleep in the middle of the work day 😭
Request for feature: Blacklist certain genres or playlists when building out my discover weekly.
I'm terrified for when my son is old enough to talk to Alexa and make his own song requests.
Beluga whale returning dropped iPhone. This is honestly crazy, if it weren’t caught on camera no one would belive it.
_
🎥 Credit - u/PaaaalHoem on Reddit #nature#whales
@TaylorPearsonMe Thanks for sharing. Any suggestions on how to end up with a (mostly) accurate probability of outcomes? I've always struggled with how to arrive at a reliable distribution of outcomes that can be trusted.