Explore eight major AI problem families—computer vision, tabular data, recommendations, time series, audio, image generation, reinforcement learning, and domain-specific models—each with purpose-built tools that outperform LLMs. Learn to recognize problem structures and match them to specialized architectures rather than defaulting to language models.
Large language models have become the default hammer for many developers building AI-powered systems. They are capable, accessible, and increasingly easy to integrate. But a hammer is not always the right tool — and in AI, reaching for an LLM when the problem calls for something else carries real costs: lower accuracy, higher latency, unnecessary complexity, and avoidable expense.
This course is organized around a single practical skill: recognizing the shape of a problem and knowing that a purpose-built tool exists for it. You do not need to become an expert in every AI subfield covered here. You need enough awareness to make better architectural decisions — and to know when to bring in someone who is a specialist.
If you have spent time building with LLMs, you have probably run into their edges. They are slow compared to lightweight classifiers. They are expensive at scale. They hallucinate on structured data problems. They are overkill for detecting a wake word or flagging an anomaly in a time series. The wider AI ecosystem has spent decades developing specialized tools for exactly these problems, and those tools routinely outperform general-purpose language models on the tasks they were designed for.
The goal here is not to replace your LLM skills — it is to surround them with context, so you know when not to use them.
This course is organized by problem type rather than by technology family, because that is how these decisions actually arise in practice. You are not sitting down to choose between XGBoost and a transformer in the abstract. You are building a feature that needs to flag suspicious transactions, or recommend products, or detect a sound event, and you need to know what kind of problem you are actually holding before you can choose the right tool.
The central organizing question is: What is the structure of my data, and what kind of output do I need?
The central question — what is the structure of my data and what kind of output do I need — branches into distinct AI problem families, each with its own purpose-built tooling.
When your data is images or video, the computer vision ecosystem offers purpose-built architectures — convolutional networks, detection models, segmentation networks — that are faster, cheaper, and more accurate than asking a vision-capable LLM to do the same work. Tasks like image classification, object detection, facial recognition, and medical imaging each have well-established model families with pre-trained weights you can fine-tune or deploy directly.
Rows and columns of records — user transactions, sensor readings, clinical observations — are the natural habitat of gradient boosted trees. Models like XGBoost and LightGBM consistently outperform deep learning on tabular data and are far simpler to train, explain, and deploy. If your problem involves predicting a numerical outcome or classifying records with structured features, this is usually where to look first.
Matching users to items at scale is a domain with its own well-developed toolkit: collaborative filtering, matrix factorization, two-tower networks. These approaches are built for the structural properties of recommendation problems — sparse interaction matrices, millions of items — in ways that prompt-based LLM approaches are not.
Forecasting, anomaly detection, and trend analysis all share a defining structure: observations ordered in time, where the sequence matters. Specialized models — from classical ARIMA to LSTMs to Temporal Fusion Transformers — exploit this structure directly. LLMs treat text as a sequence, not sensor readings; the tools designed for time series understand the domain.
Wake word detection, speaker verification, and sound classification are handled by dedicated audio architectures trained on audio features, not text tokens. These models are leaner and more accurate for their specific tasks than general-purpose language models.
Diffusion models — not LLMs — are the technology behind modern image generation systems like Stable Diffusion and DALL-E. Understanding this distinction helps you integrate the right generative tools for visual applications rather than misattributing the capability to language models.
When a system must discover a strategy through interaction with an environment rather than by pattern-matching on static data — game-playing agents, robotics, optimization — reinforcement learning is the appropriate framework. LLMs have no native mechanism for learning from trial and error.
Protein structure prediction (AlphaFold), weather forecasting, and drug discovery use architectures purpose-built for their domains — graph neural networks, domain-tuned transformers, physics-informed models. Landmark results in these fields have come not from scaling general-purpose language models, but from encoding domain structure into the architecture itself.
For each domain, you will encounter the same sequence of questions:
You are not expected to implement these methods from scratch. You are expected to recognize the shape of a problem, know that a better tool exists, and know where to reach for it — or when to bring in someone who knows that tool deeply.
LLMs are remarkable general-purpose tools, but general-purpose is not the same as best-in-class. Every problem family covered in this course has specialist methods that have been refined over years or decades for exactly that problem. The developer who knows when to use them — and when to step away from the LLM — builds systems that are faster, cheaper, more accurate, and easier to maintain.