Productivity
fromTNW | Artificial-Intelligence
4 days agoWhy probability, not averages, is reshaping AI decision-making
ChanceOmeters measure uncertainty directly, improving decision-making by providing odds rather than relying solely on averages.
We're investing a lot in AI - we're doing a lot, but we're stopping at individual productivity. We're not taking the next step. You can't just screw AI on everything - it only makes you faster. It means you need to think about, 'how are our teams collaborating? How are people collaborating?' You probably need to change the way you work.
Which Algorithm Is This? If you step back, this maps almost perfectly to the Top K Frequent Elements problem.We usually solve it for integers in a list. Here, the "elements" are audience profiles age and body-type combinations. First, define what an audience profile looks like: case class Profile(age: Int, height: Int, weight: Int) What we want is a function like this:
When discussing their results, they tell us that Facebook's reporting or Google Analytics show the ad campaigns as barely breaking even. Yet they keep investing in this channel. They reason that Facebook can only see a fraction of the sales, so if Facebook is reporting a 1x return on ad spend (ROAS) then it's probably at least 2x in reality.
The title "data scientist" is quietly disappearing from job postings, internal org charts, and LinkedIn headlines. In its place, roles like "AI engineer," "applied AI engineer," and "machine learning engineer" are becoming the norm. This Data Scientist vs AI Engineer shift raises an important question for practitioners and leaders alike: what actually changes when a data scientist becomes an AI engineer, and what stays the same? More importantly, what skills matter if you want to make this transition intentionally rather than by accident?
Every year, poor communication and siloed data bleed companies of productivity and profit. Research shows U.S. businesses lose up to $1.2 trillion annually to ineffective communication, that's about $12,506 per employee per year. This stems from breakdowns that waste an average of 7.47 hours per employee each week on miscommunications. The damage isn't only interpersonal; it's structural. Disconnected and fragmented data systems mean that employees spend around 12 hours per week just searching for information trapped in those silos.
What happens under the hood? How is the search engine able to take that simple query, look for images in the billions, trillions of images that are available online? How is it able to find this one or similar photos from all that? Usually, there is an embedding model that is doing this work behind the hood.