Claude Academy
Loading

AI capabilities & limitations

Lesson 325 min
In this lessonBy the end, you’ll be able to
  • Define generative AI and explain how it differs from other AI types
  • Explain the three developments that made modern LLMs possible
  • Identify what current AI does well and where it reliably falls short

What is generative AI

Loading

What is generative AI · 12 min

SummaryTranscript

This video covers how large language models like Claude are built and trained, and what that means for what they can — and can’t — reliably do when you put them to work in your business.

Key takeaways

  • Generative AI creates new content rather than analyzing existing data.
  • Three developments made modern LLMs possible: the transformer architecture, vast training data, and massive compute.
  • Training has two stages. Pre-training learns patterns from billions of examples. Fine-tuning teaches the model to follow instructions helpfully.
  • Current strengths include versatility across tasks, conversational fluency, and tool use.
  • Current limits include knowledge cutoffs, hallucinations, and unreliable complex reasoning.
  • The best applications pair your judgment, creativity, and oversight with AI’s speed and scale.

Exercise

Testing the edges

This exercise gives you firsthand evidence of what generative AI does well and where it falls short, using a coding problem you already know cold — so you have a concrete gut check, built from your own observations, when deciding what to trust AI with.

Part I: Self-Reflection (on your own)

Pick a coding domain you know well, where you’d immediately spot an error. Jot down:

  • The topic (e.g., your rate-limiting logic, how you handle async state, the DB query you optimized last quarter)
  • Two or three things about it any competent engineer should get right
  • One common misconception or tricky implementation detail
  • One thing that’s changed recently — a library update, a deprecation, a new best practice

Part II: Collaboration (with AI)

Open a conversation with Claude (or any AI assistant you prefer) and run three quick chats. Write down what you notice after each one.

  1. Versatility test. Ask the AI to explain your topic three different ways in a single response: once for a non-technical PM, once for a mid-level engineer joining your team, and once for a senior engineer doing code review. Did the shifts in depth actually land, or did it just change vocabulary? Which version was strongest?
  2. Hallucination test. Ask the AI to recommend specific libraries, packages, or documentation for your coding problem. Spot-check at least one: does it exist? Is the API accurate? Is the version current?
  3. Knowledge cutoff + reasoning check. Ask something time-sensitive about your domain: a recent framework update, a deprecated pattern, or a security patch. Does it flag that its information might be outdated — or present stale info as current? Then ask it to work through the tricky implementation detail you wrote down in Part I. Did it actually resolve the confusion, or just restate the correct answer?

Part III: Reflection

Which capability from the video showed up most clearly? Which limitation surfaced — and would you have caught it if this weren’t a domain you know well? Based on this, what’s one task you’d feel fine handing to AI, and one you’d want to keep a closer eye on?

Stretch goal: Run the same topic through a second AI tool. Were the errors and strengths the same?

Lesson reflection

  • How does knowing how these systems are trained change the way you’ll work with them?
  • What ethical considerations come to mind given how generative AI works and where it falls short?

What's next

Now that you’ve tested AI’s edges firsthand, in the next lesson we go deep on the first D: Delegation. You’ll frame a real problem, map it across the builder’s toolkit, and make deliberate choices about where AI plays a role — before writing a single line of code.