Tech Talks Daily
00:18:03 · Paul Speciale, Neil C. Hughes
[00:18:03] S1: Thank you. I value the opportunity, Neil. Thank you. [00:18:05] S0: I think Paul's explanation of reusing context gives infrastructure teams a way to to think about costs. The question is how much the work the system repeats, where the information is held, and whether it can be retrieved efficiently. Owning the infrastructure, yes, it brings responsibilities because teams will need to understand utilization, operating cost, model changes, and the rules that are governing their data. So I think ultimately, the business case will depend on the workload and the organization's ability to operate it reliably. I also appreciated Paul's advice on testing restrictions because trying an action that should be refused can reveal whether a policy actually holds in practice. And recovery exercises, they show whether protected data can be restored when needed. So a big thank you to my guest. You'll find all the product information, technical blog, and scale out podcast over in the episode notes at techtalksnetwork.com. But over to you, which of your AI workloads would you consider running on your own infrastructure? And what evidence would you need before deciding to do that? After listening to today's episode, show me your thoughts over at techtalksnetwork.com, and I'll get straight back to you. But that is it for today, so thanks for listening as always. Bye for now.