Practical AI
Practical AI

GenAI hot takes and bad use cases

It seems like all we hear about are the great use cases for GenAI, but where should you NOT be using the technology? On this episode Chris and Daniel share their hot takes and bad use cases. Some may surprise you! Sponsors: * Domo – The AI and data products platform. Strengthen your entire data jour

Topics Discussed

Episode Summary

Executive Summary: The hosts identify situations where generative AI is currently a poor fit: fully autonomous agents, time-series forecasting and other numerical predictions, end-to-end software development, high-throughput low-latency decisions, and work involving underrepresented languages or cultures. Their central advice is to use AI as a human-supervised assistant, pair it with purpose-built tools, and apply stronger safeguards wherever errors could have serious consequences.

Main Topics: Fully autonomous agents: Agents that independently handle complex, multi-step work—such as an entire sales process—remain fragile and error-prone. The hosts favor human-triggered agents that support specific tasks, such as prospect research, with people deciding what to do next. Forecasting and numerical prediction: General-purpose generative models are not dependable tools for time-series forecasts or high-stakes financial predictions. They may help interpret data or generate code, but purpose-built statistical forecasting methods perform the actual forecasting. End-to-end software development: AI coding tools can accelerate constrained tasks and assist developers, but the hosts caution against expecting them to create complex, production-ready applications without skilled human direction, review, and iteration. High-throughput, low-latency decisions: Generative models may be too slow and insufficiently accurate for time-critical tasks such as inspecting every item on a fast manufacturing line. Specialized models can be better suited to those decisions, while Gen AI can help people analyze results. Language and cultural coverage: Current models and their surrounding tools work unevenly across the world's languages and cultural contexts. The hosts note gaps for less-represented languages and practical accessibility issues, including right-to-left script support. Human oversight in high-stakes settings: For outcomes that can significantly affect people—such as legal, medical, financial, manufacturing, or defense decisions—generative AI should not operate without guardrails. It can assist, but should not be the sole authority.

Key Arguments: Complex autonomous agents are unreliable because multi-step plans, tool interactions, and decisions compound the chances of errors; human oversight makes the systems more useful and controllable. General-purpose language models are not grounded or numerically reliable enough to serve as forecasting engines. If they generate code that calls a statistical package, the package—not Gen AI—is doing the forecasting. Coding assistants are valuable when treated as collaborators for bounded tasks, but current tools do not justify handing them a complex application and expecting production-ready results without developer involvement. Latency, throughput, and task-specific accuracy matter: specialized models can be faster and more accurate than generative models for repetitive real-time inspection, while Gen AI may still help staff interpret the resulting data. Model performance and supporting software reflect uneven language and cultural representation, so users should not assume that a tool will work equally well across languages, scripts, and contexts. The greater the possible harm from an error, the more important it is to use guardrails, specialized systems, and human review rather than relying on a general-purpose model in isolation.

Data Points: Spoken languages worldwide: About 7,000 - Daniel cites this figure to illustrate the gap between global linguistic diversity and the languages adequately represented in current generative AI systems. Languages in which models may work relatively well: Roughly 5–10 - The hosts characterize current model performance as concentrated in only a small number of major languages. Illustrative response time for a generative model: 10 seconds - Used as an example of an impractical delay for a manufacturing quality check that must happen in a fraction of a second. Newsletter reasons advertised: 29 - The closing promotion mentions 29 reasons to subscribe to the Changelog newsletter; this is promotional rather than a technical claim.

Pivotal Quotes: "Completely autonomous agents of any type are currently, you know, well, who Knows how long this will be the case, but currently and for some time, generally a source of sadness for people when they try to create them." — Daniel Weitenak: Introduces the episode's warning that fully autonomous agents often disappoint in practice. "So it's not so much that I'm just now a not complete non-developer, right? I have no technical skills, and I just say I want this application, and it is generated for me." — Daniel Weitenak: Clarifies that AI coding tools assist development but should not be treated as a substitute for the skills needed to build complex software. "You probably want to have guardrails around it across many, many different industries." — Chris Benson: Summarizes the need for oversight in high-stakes applications, including legal, medical, financial, manufacturing, and defense contexts.

Implications: Adopt Gen AI selectively: use it to augment people and automate bounded tasks, not as an unchecked decision-maker. Match tools to latency, accuracy, language, and risk requirements, and retain human review and safeguards where mistakes could cause serious harm.

🔓 Sign Up for Unlimited Episode Search

About Practical AI

View all episodes from Practical AI