Advertise on podcast: Compiler

The relationship between data and AI is...complicated. AI is built on data. It often needs more. A wealth of data can make AI strong. But it can also be a weakness. Clarence Clayton, Director of Global Privacy + AI Risk and Compliance at Red Hat, helps us understand the increasingly complex interplay between data and AI—because the flow of information isn't a one-way street.

They say "data is king." From secret recipes to performance metrics and beyond, organizations use mountains of data every day. It's important to keep that data safe from scammers, the competition, or anyone else who could misuse it. Securing that data isn't easy. Clarence Clayton, Director of Global Privacy + AI Risk and Compliance at Red Hat, lays out the foundations of data security. He covers what needs to be protected and explains some of the basic principles you should follow to keep data thieves out of your database.

The rapid adoption of AI often means security is an afterthought. And let's face it—humans are not always great at assessing risk. But how has AI transformed the security landscape? What can the industry do to stay informed and ready to respond to threats? And what does this mean for product security? Jeff Crume, distinguished engineer at IBM, stops by to talk about AI as "the new attack surface", and explains why the technology, like so many others, can be used for both altruistic and malicious intentions.

Our trust in the internet is the lowest it’s ever been. In spite of our vigilance, we face more threats than ever before. Product security is a vital element in the defense against malicious incursions. This season of Compiler covers the particulars of product security.  With some help from Emily Fox, Portfolio Security Architect at Red Hat, our hosts kick off the season with a simple question: What is product security?

Phishing. DDoS attacks. Social engineering. These are not new terms if you know anything about cybersecurity. But emerging technologies are making these well-known methods of attack easier than ever.   Bad actors are paying attention—and they are leveling up their skills accordingly.   It isn’t just cybersecurity professionals who have to be aware and responsive– people working in product security are a part of the effort, too. What do they need to know to respond to these newer attacks?   This season, hosts Emily Bock and Vincent Danen will dig into how the security landscape has changed, and how IT professionals can work together to prevent and prepare for whenever, wherever, and however threats emerge.

Sure, AI has made a splash. And it's on us to level up, learn the ropes, and roll with it. But how do we even do that? And what cool human stuff might we accidentally ditch along the way? The Compiler team ends the season discussing the importance of context, creativity, and applied knowledge.

Agentic AIs are showing promise for tedious work. But it’s hard to explain exactly how you want it done—and getting it wrong could create big problems.  This episode of Compiler investigates how Agentic AIs could carry out their tasks and how some agents are taking their baby steps in the wide world. The team also considers the difficulties humans have expressing what we want computers to do for us, and how that could create unintended consequences.

Does your health insurance chatbot need to tell jokes? No. Does it need to be accurate? Absolutely. That's hard when biases get in the way. The introduction of bias into a model can be unintentional, but it can have significant consequences for those relying on its guidance. The Compiler team examines the ways bias can creep in, and what steps can be taken to address it.

AI is notorious for making stuff up. But it doesn’t always tell you when it does. That’s a problem for users who may not realize hallucinations are possible. This episode of Compiler investigates the persistent problem of AI Hallucination. Why does AI lie? Do these AI models know they’re hallucinating? What can we do to minimize hallucinations—or at least get better at seeing them?

With the massive flow of AI-generated content onto the internet, it was only a matter of time until all of those bits of data found their way back into AI models. But what do you get when generative AI models start getting their answers from that content? The Compiler team digs into AI feedback loops, and the unique challenges they present for technologists...and everyone else.

Copyright infringement is a huge issue for AI training and use. Can LLMs give you copyrighted content? What data can you use to train and tune your own model? In this episode of Compiler, we explore who owns what when AI models learn from protected content—and why it matters.

There’s no one AI model to rule them all. Each project has its own requirements. Where do you get started building your own model? Compiler continues its conversations with big dreamers about their big projects—and how they’re piecing together the building blocks of their AI models.

There is a lot of excitement around AI models, but can it meet the expectations set by blockbuster movies? What’s the current inflection point between what’s feasible and what’s not? The Compiler team talks to both big dreamers and heavy adopters wading into the space, hearing their thoughts on how AI can help scale daunting work, fill in the gaps, and make the fantastic into reality. 

Everyone’s talking about AI. Everyone says it’s the future. To find out where we’re going, we should know how we got here—and exactly what we’re working with. We hear a short history of AI development before diving into how it’s already changed the ways we learn and code.

Online multiplayer games are a staple of modern entertainment. But internet connectivity is an unpredictable factor in the experience. That’s why netcode exists. But what is it? And how does it really affect players?