I am confident that is not correct, but every time I zoom in to test it, my brain explodes and I can’t tell.
I am confident that is not correct, but every time I zoom in to test it, my brain explodes and I can’t tell.
Well color me impressed.
That’s so weird. You can stare at a pixel and go “yep that’s red”. Zoom in, still red. Zoom more, BOOM IT’S BLACK!
Do people actually form any sort of relationships in Twitch chat? For a decent size streamer, chat moves so fast that I can’t imagine anyone ever recognizing anyone.
Maybe for a super small streamer.
Applications of these systems have been plagued by persistent inaccuracies in their output; these are often called “AI hallucinations”. We argue that these falsehoods, and the overall activity of large language models, is better understood as bullshit in the sense explored by Frankfurt (On Bullshit, Princeton, 2005)
Now I kinda want to read On Bullshit
Maybe this makes me old, but I much prefer a written document explaining how an API works over Swagger.
Same. Especially since I’ve been building EDWs for most of my career. People are always surprised that it actually takes time to integrate with different systems.
“What do you mean you can’t just pull all the data out of this system that we don’t have database access to and are still building out the APIs?”
I kid… The people asking for stuff don’t know what backend databases and APIs are.
That would have been fine for me too. I don’t own the API, so I can only speak from a consumer perspective in saying: I don’t want a HTTP 200 if my request didn’t succeed.
I got pulled into a meeting with a team from AWS. I was told they were looking to implement a new solution, so I had to explain in detail how our data lake and data warehouse solution worked. I showed them how we pull data from all these different sources, how we have different integration patterns, etc.
At the end of my presentation, I asked “does that give you what you guys need? Or do I need to go into any more detail about anything specific? I don’t know what you all are actually building, so I’d be happy to provide more detail where you need it.”
Their response was “yeah that was all great info. We’re looking to build an app using AI and ML that allows you to run the business with a click of a button.”
I’m glad it was a remote meeting without cameras, because I literally face palmed. They didn’t have an actual use case or problem they were trying to solve. They were literally just selling a solution built on AI and ML. They didn’t know what it was gonna do, but by God they were committed to selling it.
The problem I ran into was the response returned a JSON body, but then had an “error” attribute that was returned in it that had the error details. So we were parsing the JSON and loading elements into our database. We were hitting the API passing in a datetime of when the last success job was run, so basically saying “give me everything that’s changed since I last called you.”
So yeah, eventually we noticed we were missing small chunks of data. It turned out that every time the API errored out, we’d get a valid JSON response that contained the error message, but it didn’t have the attributes we were looking for. So didn’t load anything, but updated our timestamp to say when our last successful call was.
Huge pain in the ass to troubleshoot, because the missing data was scattered with no distinguiable pattern.
Prego
From my experience, they speak mostly with their hands
This legitimately happened to me a few months ago. A vendor API was returning HTTP 200 with the error details embedded in the JSON response. It was a pain in the ass to troubleshoot.
Wait… So can you milk a dolphin?
The secret to a healthy career in IT is to let things break just a little every once in a while. Nothing so bad as to cause serious problems. But just enough to remind people that you exist and their world would come crumbling down without you.
Biden had a bad debate: faces calls to withdraw from the race.
Trump convicted of 34 felonies: record fund raising.