Congressional Black Caucus members on Capitol Hill have nominated Henrietta Lacks for a posthumous Congressional Gold Medal for her contributions to modern medicine.
Read more. 👇🏾
https://t.co/YjRfeGdrsb
Everyone is talking about OpenAI's implementation of function calls. But there is a much important problem that's being swept under the rug:
Many of us have used GPT to generate functionality in real time. In their example, the model decides that it needs to know the weather, and we want to give it access to call a weather api. The immediate problem is the impedance mismatch between unstructured language from the model and the structure needed by the api.
We ask the model to generate json, and sometimes it's not well formed so things break. No problem, OpenAI now fixes this by giving us reliable json. Great.
So what's the real issue? That the language model is now generating programs on the fly, that will be executed by calling arbitrary resources on the internet (to clarify, of course you are responsible for these calls, OpenAI won't make them for you). And the logic of these programs is unreliable, because it depends on two things:
1) the questionable "reasoning" of the LLM.
2) user input (which can be malicious).
With regular glue code, we can run regression tests and make sure we patch obvious vulnerabilities. But with this "language glue" spontaneously created by LLMs, there is no such thing. Even if we could, if OpenAI changes the behavior of the model then we are back to square one.
Let's brace ourselves for years of the most absurd security holes imaginable.
I love everything about this simple thread from @jayclouse. Using data **IS** decision-making. But here, Jay is talking about making HARD decisions. And while data helps, the most important thing is knowing where you want to get to.
One of my favorite things about Data Council is that it is a glimpse into the future of the data industry. That they film all the talks and make them freely available is a gift to the #datacommunity. In the DataPM substack below, I…https://t.co/3OADdTOpoI https://t.co/sGM8k0iYoF
One of my favorite things about Data Council is that it is a glimpse into the future of the data industry. That they film all the talks and make them freely available is a gift to the #datacommunity. Below is my talk and a roundu…https://t.co/7LIx3K3q1O https://t.co/sGM8k0iYoF
Better autocomplete is less interesting than prompt-driven development. We just don’t have great tools yet for the latter. When we do we’ll see at least 100% efficiently increases in places. In lots of cases though we’ll write more software rather than have less developers.
**Data Product Manager enthusiasts** I'll be closing this out after the Memorial Day weekend. If you are interested in joining the first or second cohort of the Data Product Management workshop, please add yourself before end of…https://t.co/gHSyZYc764 https://t.co/TRVeOCPhXx
Decisionology 101: What is a #decision, and why defining it is a keystone of #DataProductManagement
If we do not understand decisions and how people make them, how effective can we be? https://t.co/mnxMbq7prm
Hi folks, I am putting together a workshop on how to manage data products and how to transition into the role of a #DataPM
If you are interested, details are in this post on LinkedIn https://t.co/zhXcqFXP8a
#DataProductManagement#workshops
Howell, Lakewood, Ramtown, Brick, you should all be taking cover now! A possible tornado is coming your way. Get to the lowest possible floor, an interior room, away from windows. Cover yourself with a mattress or pillows. #NJwx#Tornado#TORNADOWARNING