CEOInterviews.AI
Start App
Andrew Ng
Co-Founder & Chairman, Coursera

3-hour course Learn to build effective Agentic AI systems with Andrew Ng

📅 Jul 17, 2026 mame Discovery 198 MIN 226 SEGMENTS · 3 SPEAKERS
Learn to build effective Agentic AI systems with Andrew Ng.

What Andrew Ng said

Written from the verified transcript and checked against it. Every figure links to the moment it was said.

Andrew Ng introduced a 3-hour course on building agentic AI systems, emphasizing that the single biggest predictor of team success is disciplined error analysis using evals. He announced a new course on agent skills built with Anthropic, taught by Eddie Chopik, where skills are folders of instructions and scripts that agents load on demand. Ng discussed the future of software engineering, arguing that AI coding agents are accelerating development and that frontier teams are trending toward 100% AI-written code. He identified product management, design, legal, and marketing as new bottlenecks. He introduced Context Hub, a tool to give coding agents up-to-date API documentation, and CodeDream, a voice-based learning environment available in preview. Ng also covered AI prompting techniques, including avoiding sycophancy, using progressive outlining for writing, and leveraging deep research. He demonstrated building apps like a birthday card generator and ping-pong game with AI, and concluded by encouraging continuous building and learning.

Key takeaways

  1. Ng said his own coding is 'pretty much 100% AI' and that frontier teams are trending toward 100% AI-written code, with 80% feeling very different.
  2. Ng announced CodeDream, a voice-based learning environment available in preview as of today, for practicing AI coding with Context Hub.
  3. Ng introduced Context Hub, a tool that gives coding agents up-to-date API documentation, preventing hallucinations of deprecated APIs.
  4. Ng said the AI job apocalypse narrative is being dismissed by business media and cited a Federal Reserve Bank of Philadelphia study showing few see a need to reduce workforce.
  5. Ng recommended using objective rubrics to get AI to critique work, noting that a less objective rubric scored a story 80/100 versus 75/100 with a more objective one.

Numbers and commitments

FigureWhat it refers toTypeAt
100% Proportion of Ng's own coding done by AI metric 6:39
80% Proportion of coding done by AI in some teams metric 6:39
1:8 Typical PM to engineer ratio before AI acceleration metric 8:38
1:1 PM to engineer ratio trend in AI-native teams metric 8:38
750,000 words Context size leading AI models can accept metric 1:18:33
24% Proportion of ChatGPT tasks that are writing metric 1:43:37
40% US-based employees who received work slop in the last month metric 1:44:21
3.9% Proportion of ChatGPT chats involving creative ideation metric 1:07:30
10 times How much more often ChatGPT agreed than disagreed in a Washington Post study metric 1:39:00
25 billion miles Distance of Voyager 1 from Earth metric 32:51

Chapters

  1. 0:00Course introduction and agentic AI overview
  2. 2:32Agent skills course with Anthropic
  3. 4:25Future of software engineering and AI coding
  4. 8:38Product management and other bottlenecks
  5. 13:48AI job apocalypse narrative dismissed
  6. 15:23Context Hub and CodeDream announcements
  7. 23:38AI prompting techniques for power users
  8. 32:51AI knowledge sources and web search
  9. 53:01Deep research and information finding
  10. 3:02:34Building apps with AI and final project

Questions asked in this interview

1
  1. 19:54What are we going to learn about in this conversation?
Andrew Ng 0:00 ↗
Building agentic AI systems is one of the most valuable skills in AI today. In this course, I share best practices for doing so and you come away with a systematic understanding of how to build agentic systems. I coined the term agentic AI to describe a growing category of AI projects, not realizing that marketers would get a hold of that term and slap it as a sticker on everything in sight. Even though the hype on agentic AI has grown really rapidly, the reality of agentic systems being created and deployed has grown rapidly as well. Unlike a single call that just directly generates a response, agentic AI systems can execute multiple LLM-driven steps. These steps can use tools, they can reason, they can iterate over the work to complete complex tasks. In this course, you learn how to build agentic workflows using raw Python without hiding all the steps in some framework so that you see how each step actually works. You learn to take a complex application and decompose it into a sequence of tasks that you can then implement as an agentic workflow. You also learn how to implement the four key design patterns for agentic workflows.
Having worked on many agentic systems with many teams, I found that the single biggest predictor for whether the team succeeds well lies in its ability to drive a disciplined error analysis process. That is to put in place evaluations or evals so that given a complex agentic workflow, you can efficiently hone in on what components to focus potentially improving. This way, you aren't just guessing how to spend time productively. You let the eval data guide you. In this course, I'll also show you how to drive this process and this will put you significantly ahead of the game compared to the vast majority of teams building agentic workflows today. This course is taught in a vendor-neutral way in raw Python and the emphasis is on teaching you the core concepts that you can then implement using any of the popular agentic AI development frameworks or using no framework. This long-form course is currently available only on the DeepLearning.AI website. I hope you sign up for this course and when you've completed it, you know how to build agentic AI systems which is one of the most in-demand skills on the job market today and that will also let you build a lot of cool applications.
I'm thrilled to introduce this course on agent skills built in partnership with Anthropic and taught by Eddie Chopik. Skills are a new way to equip Claude Code and other agents with on-demand knowledge. In this course, you learn how they work, explore best practices for creating them, and build skills for coding, research, data analysis, and more. You specify a skill by creating or downloading a folder containing instructions, scripts, and references for carrying out a particular task. Your agent then dynamically loads the content of the right skill to perform that task reliably. For example, maybe one skill will contain a checklist of code quality criteria for reviewing your codebase. Or another skill might include instructions for writing SQL queries against your team's data infrastructure. And yet another might describe a repeatable workflow for analyzing customer data. You create these skills once and make them available to any skill-compatible agent which then invokes them when needed to access their domain expertise. Skills were originally developed by Anthropic and are now an open standard adopted by a growing number of agentic applications. In this course, you'll see skills in action across Claude AI, Claude Code, the Claude API, and the Claude Agent SDK. Because the format is standardized, you can use the same skills with any other compatible agent and compose them to create complex workflows. You'll learn how to combine skills with other parts of your agent stack, such as MCP, sub-agents, and use them together to build powerful agentic systems. As LLMs become more capable, the code you need to write to train an agent is becoming simpler. Basic tooling like file system access and bash for code execution enables your agents to take a wide range of actions. Skills further give agents the specialized knowledge they need to handle specialized workflows accurately. I hope to see all of you here.
In addition to the AI Prompting for Everyone course announcement, there's one other significant announcement I want to make in this presentation today and you'll be the first people in the world to hear about this and I'll do that toward the end of this presentation. What I want to do today is share with you what I'm seeing with the future of software engineering as it relates to AI coding and touch on Context Hub and a new thing that I announced a little bit to share with you more I think how we can hopefully help developers navigate to this future. A year ago at the first AI Dev, I presented a slide like this where I talked about thinking of software as assembling many building blocks to create these wonderful things. So it turns out that I often think of software tools, frameworks, APIs as akin to Lego bricks. And if all I have is one type of white-colored Lego brick, you can build some stuff, but not that interesting. If you mix in some black Lego bricks, you can build more interesting things. Mix in some blue ones, mix in some red and yellow ones, and so on. And as the number of distinct building blocks you have grows, the way you can combine them to create interesting software grows exponentially or grows combinatorially.
Over the last year, the rise of AI coding agents has made it far more effective for all of us to quickly put these building blocks together to create amazingly cool stuff. And this includes both AI building blocks like large language models, you can prompt, RAG, agentic workflows, and many more as well as non-AI building blocks like UI components, persistence of databases, identity or auth managers and so on. And it turns out because of AI coding, these building blocks are proliferating at a speed like we've never seen. There are more and more building blocks every single day, both AI and non-AI for all of us to use. And this is wonderful especially when AI coding lets us get AI agents to assemble these building blocks for us.
Now when I speak with different teams in startups, academia, also very large companies, one question that's often discussed and debated is how much should we use AI coding agents? And there's actually one pop-up poll question which is I'm not going to ask this question, but I see many people ask how much of your coding is AI versus human. And you know, there'll be some teams that'll say, oh yes, my team does 80% of our coding via AI. And you know, that's pretty good. My own coding is not 80% AI, it's actually pretty much 100% AI and I want to share with you why I think even this last gap makes a big difference. Oh, by the way, in case there's anyone here, there's 0% AI is okay, too. But I encourage you to increase that percentage, right? But what I see among teams is if 80% of your code is AI, then in terms of time spent, it actually looks like this, right? AI coding time, human to review that 20% of code just takes forever. Whereas a team that's 100% AI coding just gets a lot more done in a short time. So I find that this is true not just for writing code but also reviewing code and I know that a lot of teams also have AI write code but have a human review every single line of code but for myself and a lot of my teams we find that if I got to review the code then I become the bottleneck and it also doesn't work and I'm not saying you know if you're working for NASA building and you need to write 50 lines of code for a spaceship go ahead write it by hand it's totally fine so this is not a religion where we should never be allowed to write code by hand. But what I'm seeing is many of the frontier teams are trending toward 100% or almost 100% of code written by AI. And this creates a real acceleration that getting only 80% of the way there feels very different from both for writing and reviewing code.
Now as coding accelerates by AI, there are fascinating second-order effects. I think last July in the batch newsletter I wrote about the product management bottleneck and it was this observation that when I'm trying to build stuff, you know, we'll often have an idea, build a prototype, that's software engineering, and then go to users, get feedback, that's PM or product management work, use those ideas to come and refine the software. So AI coding has made that 10 or 100 times faster and so this means that deciding what to build or the product management work becomes the new bottleneck rather than the actual building. So what I start to see like starting a year, year and a half ago was this very strange trend where we used to have product manager to engineering ratios of, you know, 1 PM would keep eight engineers busy, right? These ratios take a grain of salt but 1:8 PM to engineer, 1:7 common in many companies but the ratio started to trend toward, you know, 1:2 was really weird and then 1:1 which is even more weird. And what I'm seeing is rather than one engineer and one PM, the only thing that can move even faster is you take those two people and collapse them into a single human and I find that engineers who can shape products or product managers who can code can move really fast and that speed is a huge advantage. But not everything can be done by a single person team and so I find that for more and more AI-native teams the trend is that very small teams, they're all kind of generalist where the engineers can do some PM work, the PMs can do some engineering work and everyone kind of knows almost everything and a small team can move really fast.
I know that in some Silicon Valley circles it's trendy to talk about the job apocalypse. This idea that AI would take all jobs or almost all jobs and there'll be rioting in the streets. Frankly I'm not really seeing that and in fact with this profile of engineer, the future AI engineer has a very bright future. When my teams are hiring for AI engineers, these are what we look for, right? First have to be able to use coding agents effectively, be it Claude Code, Gemini CLI, Open Codex, Open Code or something else. And I find that having a robust knowledge of the amazing building blocks out there, which is a challenge because there's so many of them, so and they change so quickly. That is a challenge. But knowing these building blocks let you assemble things very quickly. I'll come back to the building blocks a few times this presentation. And then lastly, I find that people with generalist skills, be it basic product management or other things as well, can build much faster. So there's a combination of skills on the ability to know how to build things as well as the ability to know what to build. And I'm seeing massive unmet demand for a lot more engineers with anywhere near this mix of skill. Frankly, even my teams, we can't find enough of these people.
And this is why, and maybe going beyond the product management bottleneck, I want to take that one step further which is when software engineering speeds up 10 or 100 times, everything else seems slow in comparison. So in addition to the product management bottleneck, I'm seeing that there's often a design bottleneck because you design something and she implements it or even better the designer just implements it in code without going through a design tool like, you know, Figma and that even speeds up. And one thing that used to be painful but it's even more painful now is the legal compliance bottleneck. Right? If you spend three months writing code and legal takes a month to sign off, it's okay. But when you take a day writing code, you got to wait a month for legal. It's like boy. And even marketing bottleneck. For many of our teams, we write code and ship products so fast that marketing has a hard time trying to keep up with what these engineers are doing to figure out how to tell people about it. So I'm seeing design bottlenecks, legal compliance bottlenecks, marketing bottlenecks, sales bottlenecks, a whole bunch of other things. And this is why I find that increasingly small teams of people that includes engineers but also generalists can move really fast. And a piece of good news is it turns out that an engineer that's not a marketer but that knows how to prompt AI well, maybe they're not an amazing marketer, AI actually makes really weird marketing decisions but you know they could do some basic marketing work. And in fact, if a team needs software, product design, legal, and marketing, and it's a team of two, by definition, these two people have to have some skills in all of these functional areas. And I find that smart AI-native teams, they can use AI to help with some of these other functions can move really fast. Not advising anyone to be a lawyer but frankly I often have AI deal with legal stuff as a first pass and then take it to a real lawyer to sign off before I launch something but I find this AI-native team moves really fast.
Something I don't have time to talk about is how to structure multiple AI-native teams to work together because again not everything can be done by a 10-person team but if you have a 100-person team or many AI-native teams with limited communication and clear API boundaries that also helps to scale beyond a single team. Well to come back to the work that needs to be done to create software, writing software code is just a small piece of it that's accelerating rapidly but I just don't see the AI job apocalypse happening anytime soon. I find that the business media often has to be more accurate than the popular press because the popular press can tell exciting stories, but the business media is paid to get it right. And I've been encouraged that over the last month or two, a lot of the business media has been getting the story right that this AI job apocalypse narrative is now being dismissed, tech job cuts, jobless claims being delayed. Federal Reserve Bank, a small highlight, sorry for the tangent, highlighted few see a need to reduce their workforce, a study by the Federal Reserve Bank of Philadelphia. So actually, and to be clear I know a lot of people are feeling job insecurity at all levels of seniority. I think we need to do something to address that and I know many people have been laid off because of overhiring from the pandemic or hiring from zero interest rates period. So, I'm not saying the job situation is perfect. There's a lot of it that's not that pretty. But the job apocalypse narrative is possible at the top in some circles. I just don't see it happening. Which is why I'm eager to keep on investing in all of us becoming better at building these.
Now, one of the hardest things to do, exciting, most important, hardest, is as we're becoming better builders, each of us, how to master these building blocks. I want to share with you a framework of parallel skill development. Here's what I mean. We talk a lot about how our coding agents are becoming more capable and this includes agent skills like the Anthropic agent skills work. But more generally, our coding agents are just getting better and better. And then there's the education or training world that I've been a part of for a long time that focuses on building human skills. But looking into the future, I think we increasingly need parallel skill development. Where as our coding agents become more capable, our people, we as people need the complementary skills to help us to drive the coding agents in the appropriate way so that we can partner together to build new things. So I want to briefly touch on two things in the rest of this presentation. And one is Context Hub which I talked about before, I'll spend a couple minutes on, and the second which is the announcement I made toward the end is CodeDream.
Context Hub, it turns out building blocks are proliferating so fast that most of our coding agents which have a knowledge cutoff date far in the distant past, sometimes a year, sometimes a month old, will often hallucinate or use deprecated APIs or not know about the latest tools we want to use. So it turns out even today if you ask Claude Code to call the OpenAI API it will use the chat completions API which is older, deprecated, and call older models because most of the training data on the internet uses this older API even though the newest API has been out for a long time. Context Hub is a tool that some colleagues, Rohit Prasad, Senior Fellow, and I built in order to give your AI agent the most up-to-date documentation. And it turns out that if you run Context Hub with Claude Code, it will generate code with the newer Responses API. Maybe just to show you really briefly, I don't know, chub search openai. So this returns, so these are packages and then chub get, this actually, open chat, pipe this more, and so this will fetch the latest documentation on OpenAI that knows about GPT-5.5, knows about the Responses API and so on. And this is a tool that you are welcome to use but is actually built for your coding agent to use. And so this generates, like okay, a 600-line markdown file, right, kind of long for a human to read, or you're welcome to read it to give your LLM the context it needs to make this and other API calls correctly. So I pray many of you too, right? I've had my coding agents hallucinate API calls to definitely, you know, OpenAI, Gemini calls, make bad calls to various database services. There's just so many tools that coding agents don't know about. But feeding on this latest context, I think can be very helpful.
But beyond that, I want to share with you a project that we've been working on to help with human skill development. For a long time, you know, my team's been working on a variety of online courses and please keep on taking online courses, I think important part of how we can all stay up to date with the building blocks and other tools. And we've been exploring one other alternative experience that I'm announcing here for the first time today and that's a project we've been working on called CodeDream. The Wi-Fi here is not great so I'm going to see if a live demo works. It may not but let's see if this works. Okay, welcome to CodeDream. This is not a course, it's a conversation where I want to show you how to use a coding agent together with a tool called Context Hub to write code using up-to-date API documentation. I say this is a conversation because I'd like you to imagine we're on a video call and you can interrupt me at any time using that little microphone button down below. The CodeDream team has created a voice agent that has the information she needs to try to answer your questions as well. So feel free to stop me if there's anything you'd like to chat about or if you like you can just lean back and watch the presentation. Here's the idea. All right.
Unknown 19:54 ↗
What are we going to learn about in this conversation?
CodeDream Voice Agent 19:58 ↗
We're going to learn how to use Context Hub to keep coding agents up to date with the latest information. Then we'll build a joke generator app together.
Andrew Ng 20:08 ↗
So this is not a slide, right? I just click into this and type, let's tell a dad joke about bad Wi-Fi. Why did the computer show up late? Where it was bad connection. Okay, not bad. Could be worse. And the other thing about this being JavaScript is you can also copy-paste from these slides. So for example, this is a slide with instructions on how to install Context Hub and how to prompt Open Code and so on. So actually copy, I'm hitting Command C and then go into the CodeDream build environment. And this is a terminal in my browser where I can, you know, paste that command. I just copy-pasted it from my slide to run npm install chub and then I can do things like start up Open Code which is an open-source version of a coding agent, kind of like, you know, alternative to Claude Code, Gemini, Open Codex, and then I don't know, writes python, whatever. Right, and so this is a learning practice environment that lets you practice using modern coding agents with tools like Context Hub. And so we have been working on this CodeDream build environment for quite some time and I'm excited about exploring this concept where in lieu of taking a course you can come onto a video conversation and have a conversation with me or an AI version of me to try to gain new skills and code in this more modern AI coding way. And I am happy to announce that CodeDream is available as of today in preview.
So please check it out. And the first experience will show you how to use Context Hub and give us feedback. We're eager to keep on working to make this better. So just to wrap up, coding agents are allowing us to assemble building blocks quickly to create software and that acceleration is real, but many of the downstream implications about where the new bottlenecks are are still being worked out. And I'm eager to help our entire community keep moving forward because the job openings are there. The job apocalypse is not going to be nearly as bad as people are hyping it up to be. And I think it's important that we keep on learning these building blocks and learning these skills. And for parallel skill development, coding agents are working well, but give them access to the latest building blocks. Given the right context, Context Hub will help. And for human skill development, I'm excited also to share with you the CodeDream conversations. And all of you in this room are the very first people in the world that I've shared this with outside our team. And I hope you will check this out and that'll help you to master some new building blocks and master some new skills. So with that, really excited to be here. Thank you all for coming and thank you all very much.
Using AI is one of the most impactful skills you can develop. And people that are not yet at the cutting edge of AI usage often run into AI generating frustrating outputs. I want to make sure you're an expert prompter and can take advantage of today's AI tools which are much more powerful than they were even a year ago. Let's take a look at two different experiences: the AI novice and AI power user. Many AI experts have learned to use it to answer hard questions. In contrast, many people, including AI novices, may have gotten used to using AI for simple questions, as if you were prompting it like a Google search. So, you ask it, does Taco Bell still have the double-decker taco? And maybe you get an answer like that, which is fine. But if you have much harder questions, you can also ask it of the AI and give it time to think. For example, if you're looking to buy a car, you can upload to most of the commercial services like ChatGPT, Gemini, Anthropic's Claude, or others a set of documents including cost specs, quotes, insurance plans, and ask it what are the trade-offs for these different cars I'm thinking about and tell it to read everything and to think hard before answering. And this can cause AI to spend many seconds or even minutes to think and then compile a detailed report for you. I find this a huge timesaver for a lot of things I have to do.
Another example, AI power users have learned to provide the right context or the right background information to the AI to set it up for successfully answering your question. In contrast, I see some AI novices use a short prompt and hope that AI will fill in the blanks. But if you think of AI as maybe being akin to a really smart, fresh college grad, highly motivated, but that doesn't really know that much about you yet, then a short prompt sometimes doesn't give it enough information or enough background context to answer your question accurately. So if you tell AI, please write a good self-review to send to my boss, the AI doesn't know what you've actually done over the last year because you haven't told it yet. And it might write a very generic self-review which isn't that helpful. In contrast, I find that AI power users almost have empathy for the AI. I don't want to overly anthropomorphize the AI, but if you could put yourself in the shoes of someone getting a set of instructions from you, you can ask yourself, will they actually know enough about you to do a good job on the task you're assigning them? So, an AI power user in comparison might upload a lot of information to the AI. Maybe give it a screenshot of a project tracker showing what you worked on, recent project docs, maybe voice memo notes where you talk through the projects and then tell it to write a self-review to send to my boss. And that could do a much better job capturing what you're most proud of.
One of the things power users have learned to do is how to prompt AI to get honest feedback. A big problem with AI is it often wants to please you. In fact, many AI systems were trained to try to make the users happy. And if you ask it a biased question, it will often give a biased answer because it's trying to tell you what it thinks you want to hear. For example, if you say, I have a great business idea, mobile tie-dyeing. Critique it. Because you called it a great business idea and you're saying it's your idea, the AI will naturally want to please you and say what a great idea. We sometimes call this sycophancy and it's well known that if you give even a hint of what answer you're hoping for, there's a good chance the AI will just reflect back your preferences or your preconceptions. In contrast, AI power users tend to ask neutral questions that don't give any hint to the AI for what answer you're hoping for or not hoping for. Or if you give it a rubric or grading criteria to tell the AI how to form the basis for its answer, that also forces it to be more objective. For example, if you were to say, please analyze the following business idea objectively: mobile tie-dyeing. And don't just make up a bunch of things for what you think. Use the rubric or the grading criteria above, such as, is there a problem? Is there a market? Do I have a competitive advantage? If you give instructions like this to the AI, then the AI doesn't know. Are you hoping it'll tell you it's a great idea or that it will save you from spending a lot of time on a bad business idea? And it's much more likely to then tell you something like, oh, this idea is an 8 out of 100 and also why this score is low.
In case you run a mobile tie-dyeing business, I wish you really best of luck. And AI could also help ask some useful questions to help you think through how to make the business even better. Lastly, I found that AI novices and AI power users ask AI to write in very different ways. Novices will just ask AI to write stuff like write a blog post about the Blackberry and it will generate a bunch of text that maybe looks like this which sounds like AI slop. It's a bunch of generated text that's just not that interesting and takes up a lot of space. In contrast, an AI power user will often not ask the AI system to just jump in writing directly, but instead ask the AI to first outline an article and then critique the outline and maybe iterate a few times with the outline to shape the article and only then ask AI to start to draft the final article. So given a set of uploaded notes as context, an expert may say, outline a blog post about the Blackberry based on my notes. So it knows what you want to talk about. And the AI may start by giving an outline. And you might then give feedback to the AI about what you like and what you don't like about the outline. And even iterate a few times, have a few back and forth rounds before you have an outline that you're satisfied with. And maybe only then expand the outline into bullet points. And maybe even go back and forth a few times to critique the bullet points before you're satisfied with that and then expand it into the final text. This type of power user workflow is much more likely to generate some text that you're happy with as opposed to AI slop. And in this type of workflow, you're treating the AI as a thinking partner to almost help you brainstorm and explore different options for what you might want to write.
AI systems do make mistakes, but maybe fewer than most people think, especially if you prompt it well. They made a lot more mistakes back in 2022 or 2023 than they do now. But a lot of widely publicized mistakes that AI has made, some of which went viral on social media, has made people think that AI maybe makes even more mistakes than it actually does. There's a well-publicized one where people asked it, how many Rs are there in the word strawberry and it thinks there are two Rs. And here's one that I found amusing. I want to wash my car. Should I walk or drive there? And AI says walk, which would leave you there to wash your car. But these viral examples are not representative of AI capabilities. In contrast, power users know that AI can deliver significant value through tasks like doing deep research and writing research reports or taking your personal data like your health or heart rate or running time data and analyzing that for you or something we will talk about later, even building websites for you. I've seen being an AI power user tremendously benefit individuals as well as their businesses. It'll save you time and improve your professional and personal lives. It'll help you to build lots of cool things. You'll learn how later in these videos. And being able to prompt AI at an expert level is a highly in-demand job skill no matter what job role you're in. In the rest of these videos, I hope to take you from wherever you are today to being an AI power user. Much has been said about AI being useful. I find using AI really fun as well, and you'll see a few examples of that in these videos, too.
Now, one foundational piece of knowledge that helps you work with AI is understanding where it gets its knowledge from so that you can better predict when it'll get something right and when you maybe should question its answer. Let's go on to the next video to learn about how AI gets its knowledge. How did you learn to write as a child? Probably it involved reading a lot of things. Well, it's the same for AI. AI systems have learned patterns from reading large amounts of text from the internet. By understanding what's in that text the AI has read, you'll be able to predict how they'll behave. AI models can answer questions on a variety of topics. If you were to ask, I dropped my phone in soup. What should I do? Then hopefully it'll make some useful suggestions. Or why do cats stare at walls like they see ghosts? My daughter loves cats. She was actually curious about this. Turns out cats can detect subtle sounds and movements that we as humans often miss. Because of the amount of text it's read on the internet, they will even possess niche knowledge that few people know about. If you were to ask what kind of things were on the vinyl record sent into space, years ago, NASA had a spacecraft called Voyager 1 that launched in the 1970s and is now about 25 billion miles away from Earth. But AI will know about this and be able to tell you what is on that vinyl record. I think it's cool that NASA chose to send greetings in 55 different languages, whoever may come across that spacecraft if anyone does.
AI models are trained on many, many different sources of information, mainly from the internet, and training on all of these very diverse sources of knowledge produces pre-trained knowledge. The term pre-trained is a technical term that you don't have to worry about. It turns out AI systems are trained in multiple steps and this is one of the first steps of training that somehow wound up being called pre-training which isn't a great term but I wouldn't worry about why we call it pre-training. It's just what AI has learned from. But these knowledge sources may include a lot of text from social media like Reddit which will have answers to questions like what are your must-watch films? Or it may have read a book on Lego micro cities or read a Wikipedia article on fairy bread and lots of other things or read a bunch of news articles as well as read a lot of research articles on the internet. There's a lot of text on internet forums and social media like Reddit and Quora. There are a lot of books that AI will have read from. There are encyclopedias like Wikipedia, news websites, research articles, and much more. And so these trillions or tens of trillions of words will go into training the AI model's brain.
Now different types of data appear with different amounts of frequency on the internet and so this pre-trained knowledge reflects the frequency or the patterns in the training data. For example, cooking is a very universal human experience. So there are a lot of articles on the internet on cooking. There are also a lot of articles online on celebrities, on movies and so AI has seen a lot of text on these topics. In contrast, there are more specialized topics like quasar, which is an astronomical term referring to really bright objects in the sky powered by supermassive black holes. I think they're fascinating, but there are just a lot fewer articles on quasars than on cooking on the internet. Now, while most of the internet is in English, AI systems will also have learned from some data that's written in other languages like Cantonese. Over 80 million people speak Cantonese, but that's far less than English and Cantonese data represents maybe less than 0.1% of all internet content. Lastly, there are things that AI models know nothing about at all, such as your company's secret proprietary data, which hopefully is not on the open internet, but which an AI system will therefore not have learned from. So I find that thinking about how frequent data appears on the internet gives you a good rule of thumb for thinking about how reliable an AI system's responses are.
Now because of the data the AI has learned from, sometimes it can exhibit surprising understanding of things. If you were to type very quickly, can you cook eggs in microwave? Like shown on the left, it can actually understand this type of misspelled text very well. Pretty much as well as asking, can you cook eggs in the microwave? And by the way, I've exploded a few eggs in the microwave myself. So, if you ever want to avoid that, feel free to ask the AI system how to do so, so you don't have to learn the hard way. And a reason that it's so good at understanding misspelled words is because it's actually learned from a lot of sources that could include typos. So if you look online, you will see phrases misspelled. And that's why when you're using the system, I'm not encouraging you to use bad grammar or to misspell words. But it turns out that if you're typing quickly and you have a few typos or even a lot of typos, don't worry too much about it. It's pretty fine to just send a prompt to AI and not spend too much time fixing every little grammatical error. Now, the bad news is a lot of AI sources also have misconceptions and outdated information. So, one of the skills in using AI is how to prompt it to have it give you back answers that reflect fewer misconceptions and does not overly reflect outdated information. By understanding AI's knowledge sources, called pre-trained knowledge, you'll be able to better predict how it will respond to your prompts. But this pre-trained knowledge is not enough for all applications, including those that need real-time information. For that, you need web search. Let's go on to the next video to learn more.
At some point, the people building the AI model had to stop this training. So there's some last date where its information cuts off. That is, the AI has read the internet only up to a certain date and time and its knowledge gets frozen in time as of that date. But of course the world moves on past that date. New things happen, movies come out and so on. Let's see how AI models handle gathering new information using web search so that it can address questions that even relate to things after its knowledge cutoff date. If you're using one of the popular AI model providers like ChatGPT, Gemini, and Claude, there are certain questions that will probably trigger it to do a web search. For example, if you ask it, what is the 67 meme from 2025? There's a good chance it will search on the internet to tell you that the 67 meme, which is pronounced sixty-seven, which is kind of fun to say, that this is a viral internet slang widely seen on a few social media platforms. And the reason it triggers a web search when you ask it, what's a 67 meme from 2025? The Q 2025 causes AI to realize that it may benefit from more updated online information because this could be a meme that appeared on the internet after its knowledge cutoff date.
Here's what I mean. A specific AI model's pre-trained knowledge is frozen in time even though the internet continues to evolve over time. And so if this line represents time, then for a long time the internet will have had pieces of text that say 6 times 7 equals 42. Text that talks about the children's joke, why was six afraid of seven? Because 7 ate 9. But if the knowledge cutoff date was at a certain moment in time and the 67 meme came after that, then the 67 meme would not have been seen in the pre-trained knowledge of the AI model. So if you ask it what is the 67 meme from 2025, the AI model will realize that it doesn't know about this 67 meme from 2025 and that it should do a web search in order to get more updated information. Take the GPT-5.4 model from OpenAI. Its knowledge cutoff date was August 2025. And this graph shows how many Google web searches there were for what does 67 mean. So this 67 meme had taken off after this GPT-5.4 knowledge cutoff date, which is why the model doesn't really know about this meme.
Now, there are certain types of questions that an AI will answer using its pre-trained knowledge, and there are certain types of questions that will tend to trigger web search. For example, if you tell it, please find me a highly rated gym near Mountain View, California. Then, what is highly rated, what may be open, and what may be closed, does change over time. And there's a good chance that this will trigger a web search. Or if you ask it, what is the Cooper's Hill Cheese-Rolling? Because this is a niche piece of information, there's probably not really a lot of information online about this cheese roll. There's a good chance that it will search the internet in order to get you an answer. And if you're curious, this is actually a pretty fun event where people chase a rolling wheel of cheese down a hill. Let's take a look more broadly at when an AI model needs to do some web search to gather more information to answer your question. If you're asking what to do if you drop your phone in soup or why do cats stare at walls or what's on the Voyager 1 record in outer space then these questions it could probably answer using pre-trained knowledge because these are represented in common knowledge on the internet. But if you were to ask it about current events or something happening very recently then it'll need to do a web search to get that real-time information. If you ask it location-specific information, doing a web search makes sense. Or if you ask it for other types of niche information, there's also a good chance it'll realize it doesn't know enough about that topic that doing a web search to gather more information would help it give you a better answer.
For most of the popular AI model providers, web search can be triggered in either of two ways. Sometimes the AI model will decide by itself to carry out a web search or you can also explicitly trigger web search sometimes by clicking one of the buttons in an AI model provider's web interface or just writing your prompt, please do a web search for this and it will comply and use a web search to answer your question. Not all AI models have web search enabled, but the most popular ones that you're probably using mostly do have this capability. AI will do better on many of the tasks you want to use it for if it does web search. And web search allows it to augment its pre-trained knowledge with more current information. But like all web search, it can return bad sources. Let's take a look at when this is an issue and when and how to get it to use more reliable sources to get you more reliable answers.
Web search is a very valuable but imperfect tool. Just like when you search the web yourself, you might not always find what you're looking for. It has limitations like finding old or inaccurate sources. But you can work around these limitations to get AI to give you more accurate and up-to-date answers. Let's take a look. If you ask an AI system, how safe are gray-market peptides, which is a type of supplement, it may search online and find posts on social media or public forum sites like Reddit and Quora. Or you may find websites that are in the business of selling peptides and so would have an inclination to tell you that they're safe and you may get back answers that may or may not be accurate. But if you encourage the AI model to use sources from official organizations or look at studies that are backed by rigorous science, then it's more likely to look up resources from the World Health Organization, from the US Food and Drug Administration, from the European Medicines Agency, and so on, and hopefully give you more reliable and scientifically credible answers.
Web search, whether done by a human on Google or Bing or done by AI, has a tendency to draw from popular sources. According to one report, the most cited website by AI models was Reddit, followed by Wikipedia, YouTube, Google itself, Yelp, and so on. And some of these sources are more trustworthy than others. There's just a lot of text on the internet from social media, blogs, online forums, and the amount of text from highly reliable scientifically verified sources is just much smaller. So, if you don't steer the model in terms of what types of sources you prefer, there's a chance that it'll tend to pull text from whatever is most available rather than what's most reliable. So that's why if you ask it how safe are gray-market peptides, it might base a lot of its answer on social media, blogs, and forums and only a little bit on the more reliable sources. Whereas if you tell it to use sources from official health organizations, it may pull much more from these reliable sources.
Another limitation of web search is that sometimes web pages can be outdated. That can lead the AI model to also not provide the most current information. A friend of mine recently helped me find places to run in Henderson, Nevada. This is a location-specific niche query and so this triggers web search and it found this list of places to go for a jog. But it turns out that unfortunately this pulled from a web page from more than two decades ago. And unfortunately, the location suggested was a school that unlike decades ago is no longer open to the public to go running in. To help build intuition about how AI searches the web to use that information, let me briefly explain how web search actually works under the hood. It turns out to be a multi-step process. Imagine that you're asking questions of a customer service team of two people. There's the
user-facing AI model. That's what you are talking to. And the user-facing AI model has a second assistant AI model that it can ask for help to do web search. So when you send a prompt, you are talking to the first model, the user-facing AI model, and it will occasionally decide to call up the assistant AI model, the second AI to say, "Hey, please do a web search for me to gather more information." This assistant AI model will then search on a web search engine very similar to Google and Bing and other web search engines that we as people might use and it will scan the return results, filter out the relevant results and download the most relevant web pages and then summarize them. The second assistant AI model will then present the summaries back to the first model, the user-facing AI model. And the first model will then use these summaries in order to generate the final answer for you. You are speaking only to the user-facing AI model. And one interesting quirk to keep in mind is the user-facing AI model has not actually read in its entirety all of the web pages it may be citing for you. Instead it has only seen summaries of those web pages. And sometimes this causes it to misinterpret what one of these underlying web pages actually says. Which is why you may have seen funny results where AI cites a web page and says the web page justifies a conclusion. But if you look at that web page yourself, it doesn't actually justify what the user-facing AI model says it is doing.
To walk you through one example of this process, if you ask the user-facing AI model, that's like the customer service agent talking to you. It will ask what should I know before hiking Machu Picchu. The second model may do some web searches with phrases like weather or the social customs and so on and it'll then scan the returned results much like you may scan the page of Google results to decide what's relevant and filter out irrelevant results and summarize the most relevant web pages to provide back to the first agent that then generates the final answer for you.
Now I frequently use AI models like ChatGPT, Gemini, Claude and I also frequently use web search engines like Google and Bing. When should you use an AI model and when should you use a web search engine? If you want to quickly scan multiple sources, a search engine can be useful for that. Or if you want to navigate to a specific website but have forgotten what's the name of that website, a web search engine can be very good for helping you find it. Or if you want to look at data in its original form, such as if you want to buy a 2013 Honda Civic air filter, you know, you want to find a website to go to to buy that air filter. So web search engine is very good at that. In contrast, if you want to get a synthesis from multiple sources or if you're searching for more complex information with pros and cons that you want weighed or if you just want to contrast multiple sources to come up with a more thoughtful conclusion, then an AI model can do a web search and put together the results of multiple web pages for you quite efficiently, thus maybe saving you time of having to read a lot of web pages yourself. There might be some good Google or other web search habits that you've developed and those habits will serve you well when working with web search enabled AI models as well. Things like looking for reliable sources and also double-checking the sources. But if you want to go beyond searching a handful of web pages, it turns out AI models are capable of a much more extensive type of research called deep research.
This is a very powerful capability that I think is really underused by many people. Let's go on to the next video to see what it is and when and how to use a deep researcher.
Sometimes you will want your AI to synthesize not just a handful of sources but many, maybe many dozens of sources and do lots of thinking to come up with the best possible deeply researched answer to a question that you have. Popular AI chat interfaces like ChatGPT, Gemini and Claude all have a deep research mode. I found this to be a very valuable and often underutilized tool. Let's take a look. Let's say you want to use an AI model to help you plan your Halloween haunted house. I'm going to write a prompt to ask it to help me set up a haunted house in my front yard for Halloween and give it some information about where I am, what's the size of my front yard, what's the experience I want. So, I give it lots of context to set it up to plan it out for me appropriately.
With a prompt like this, an AI model might come up with a research plan in which it tries to think through what are the types of sources it needs to research. Many systems would give you an opportunity to approve or potentially edit the research plan. And if you're happy with it, I'll often launch the research plan without updating it unless I see something that just looks really wrong. It will then go ahead and start to do online searches. So in this example it starts by gathering Palo Alto's rules on permits, Halloween ordinances and so on. And then it will read some of those web pages and synthesize what is learned so far. And it may then decide to do some more searches online to gather more information about fire safety guidelines. And then it may after that decide to look for decoration ideas. So loosely follow the original research plan but also have the flexibility to keep looking deep into certain areas if it thinks it needs that information.
After searching for a while, maybe many minutes, it will finally write a detailed research report for you. This process by the way is an example of agentic AI. And what that refers to is that through this deep research process, the AI model has some flexibility to make decisions by itself on what to do next, such as what additional searches, if any, to carry out. The output of this can then be a fairly detailed and thoughtful plan with different sections outlining what you might need to think about in terms of structure and regulatory framework, safety, and so on. If you're using Google's Gemini AI model for this, one of the neat features is it makes it easy to take the deep research it's done and help you turn it into a web page or infographic or a handful of other things.
Here's a web page that was generated by Gemini using the Gemini deep researcher and I think it's pretty neat. It has created a web page with four different sections, pie charts for budget, pretty neat visualizations for noise ordinance. And I think it's pretty neat that this even has a little checklist that I could use to plan out my Halloween event.
To give you a sense of how a deep researcher works, this is loosely what it does. After formulating a research plan, an AI model can actually issue many web searches at the same time and get back multiple web pages at the same time. And this is one of the nice things about using a deep researcher. It doesn't have to do the web searches one at a time. It can do many of them at the same time, which lets it be very efficient in fetching lots of web pages. The system can also take a look at all of these sources and quickly assess which ones are relevant and which ones are less relevant. And based on that, it may decide whether or not to go back to do additional web searches, maybe using different web search terms. Finally, after going around this loop a few times of doing web search, evaluate sources, deciding whether or not to go back to get more sources, it'll hopefully decide it's done and then lastly take all of the pages it has downloaded and maybe summarize and synthesize all that into a report that it adds citations to and that it then presents to you.
Both web search enabled AI as well as deep research use the internet or do web search. The basic web search enabled AI is good at queries like this. Find me a highly rated gym. What's the weather in Dubai this week? Whereas deep research I would tend to use for tasks that require synthesizing multiple views such as if I want to know what's the impact of daily steps on long-term health and if I wanted to search the most recent scientifically justified articles and think through the answer rather than just tell me whatever people tend to say on the internet. Or if I wanted to deeply think through how does weather affect tourism in Dubai and again not just take one or two popular answers found on a social media site but to read up on weather, read up on tourism, read up on Dubai and to really think through the implications to give you a more thoughtful answer, that's when deep research could be particularly helpful.
To give you another framework to think through when to use web search versus deep research, if you have a single question do you want answered doing work that would take me just a few seconds based on a handful of sources. That's when web search would be helpful. And web search, as we've seen, can be triggered either automatically or by the user. Whereas deep research often is trying to draw a complex set of conclusions that may require answering multiple questions or answering multiple dimensions that relate to a question. And I think of this as doing work that would take me minutes to maybe even hours if I was doing this manually. And I may want many sources of information synthesized. And as we've seen, deep researcher is usually triggered explicitly by the user unless you select it in the user interface. Most AI models will not cater and keep you waiting for many minutes for an answer.
To recap, if you're asking, "How do I drop my phone in soup," it doesn't need to look up any online sources. We're not worried about freshness. It'll give you an answer in just a few seconds. And this is good for finding basic facts, definitions, summaries for things that occur commonly on the internet. Web search may download a handful of sources and they will find relatively up-to-date information and it may take many seconds to get you back an answer. And we've seen what types of information this is useful for. And lastly, deep research may download often dozens or more of sources. It will get up-to-date information and it will spend many minutes or longer to get back an answer. And is great at answering complex questions that involve synthesizing many sources of knowledge.
Finding information is one of the most common tasks that people use AI models for. You've seen three different paths that you can take advantage of for this type of information finding task. You could use just a pre-trained knowledge or web search or deep research. And we also walked through how and when to use these different options. I want to make sure that you have good intuitions about when to use each of these options. So let's go on to take a look next at a practice hands-on lab for this module which I think you'll find a fun way to compare and contrast what each of these options do and more importantly will also help you build your intuition on when to use each.
In this module you learned how to use AI models to find information. In this practice lab, you can explore how web search, deep research, and different prompts affect the AI model's output. Let's take a look. When you open up the lab, it starts off with a tutorial on how to use the lab. And I'm just going to close it out here. You can always access this tutorial again via this button up here. And what I hope you do is follow the instructions written here. And when you're done, click mark as complete to mark this item as completed.
First, these buttons down here correspond to different things you might try. So, this one, current events, compares a question with and without web search. So, what's the 67 meme? This on the left is without web search. The one on the right is with web search enabled. And if you compare, then without web search it gives these answers. It doesn't know about the meme. But with web search it tells you what is this 67 meme as well as the origins of this meme. And if you want, you can also follow up and ask, "How do I use 67 appropriately in a black tie tuxedo party?" And then hit this red button to go see his answer.
Let's go back to the homepage by clicking new chat up here. And I hope you try out the other examples such as find me a highly rated gym and hit compare or when's the next Avengers movie scheduled or what major news happened today in the US or feel free to enter your own country and compare these results with and without web search.
This example over here shows the difference between web search denoted by this globe icon versus deep researcher denoted by this microscope icon. So how safe are gray market peptides? Use high quality sources and this would give you a sense of what web search results look like versus deep researcher results. I hope you run it and see what results you get.
One more example. If I want to ask, can I keep my rocket propelled monster truck in my garage? If you ask it this question, the AI model may or may not know the answer. But if you were to also upload the lease agreement, then maybe your lease agreement, which states the terms under which you're renting your place, may have restrictions on that. And so you'll be able to see different answers depending on whether or not you upload additional information. In this case, a lease agreement that is helpful for the AI to give you a thoughtful answer.
We haven't talked much yet about uploading your own files in this module, but it's something we'll dive into more deeply later in these videos, but feel free to play with this. Now, lastly, one fun example.
Here is a version of why do cats stare at walls with lots of typos. Here's one with nicely formatted grammar, no typos. And you'll find that the answers are maybe surprisingly similar, that the AI system is pretty good at answering a question like this, even if it's lots of typos.
Once you've tried out these examples reflected by these buttons down here, come up with your own. Like, is the weather good for a picnic in Palo Alto today? And try this with or without web search and see what answers you get. Or pick your own example and try comparing the results you get using web search. And if you want, uploading your own files.
So that's it for module one of this course. Great job getting this far. I hope you enjoy playing around with the lab. Next, please join me in the next module where you hear about using AI as a thought partner, including having it brainstorm with you and explore ideas with you. This has helped me shape the direction of many projects, and I'm confident you'll find it useful, too. And we'll also explore getting AI to help you with your writing and editing. I'll see you in the next module.
One of the most helpful uses of AI is as a thought partner. When I'm trying to think through a complex problem or make a complex decision, it's nice to have a human expert as a thought partner that is someone to talk things through with. But if there isn't a human expert readily available, AI, which actually knows a lot about a lot of things, can be a really good resource for this. We'll go through together multiple examples of this, but to get started, brainstorming is one great such use case. Now, I know a lot of people ask AI to help brainstorm lists of ideas, but there are more effective ways to use it as a brainstorming partner than just having it generate a list. Let me show you what I mean.
According to data released by OpenAI analyzing ChatGPT conversations, about half of ChatGPT chats are asking for writing and practical guidance. And in fact, creative ideation accounts for 3.9%, almost 4% of all chats. I found using AI to help me brainstorm to be really valuable. Let me share with you some ways to do so. AI can be pretty good at generating options. There's a common creativity test which asks people to name 200 potential uses for a brick. So give it a brick like this. How many uses can you think of? This is actually pretty difficult. Some people think, oh, it could be a paperweight, maybe a planter, and oh, it could be used to build a house, too, I guess. But to come up with 200 examples is not that easy. But if you ask an AI model, there's a good chance you can come up with a long list of ideas. And your role, if you're actually trying to use a brick for something, would be to evaluate these options to pick out which ones are the ones that you like. In brainstorming, a common guidance is the more ideas the better. And so sometimes having AI generate a lot of ideas for you to pick from can be a powerful way to find one or two good ideas. So this is the maybe more common use of AI as a brainstorming partner.
I want to show you a different form of brainstorming in which you give it more context and then also iterate with the AI longer, meaning have a longer back and forth conversation to help get you to better options. So if you tell it, help me build a workout plan on 38 level, have 10 lb dumbbells in 15 minutes a day, then they may give fairly generic answers like three workout plans. So, 10 squats, 10 push-ups, pretty reasonable, very sensible, common sense answer. But if you want more creative options, giving it more context can be helpful. So, if you say, "I can't stick to these. Give me hacks to stay on track. I have a trampoline and a cat." By encouraging it to give you trampoline and cat-related workout options, which is an unusual way of approaching workouts, it may ask you to consider trampoline breaks or cat-triggered micro workouts where maybe every time you see your cat wag its tail or something, go do a tiny little workout. But these are certainly more creative ideas.
AI models have some inherent creativity because they've trained on a lot of text on the internet which covers a lot of very different ideas including some creative ones. And AI's output is a little bit random. So if you ask it multiple times, help me build a workout plan, it'll probably give you slightly different answers. But if you give the AI basic questions, then common sense relatively generic responses like do squats, push-ups, and so on are more likely. Let me plot a conceptual diagram where on the horizontal axis I'm going to plot how unique a response is, how creative a response is. So on the left were responses like normal weightlifting exercises like bicep curls, which is very common sense, to then maybe slightly more unique things like standing on one leg with a yoga block on your head to the really creative ones like cat-triggered micro workouts. And on the vertical axis, I'm going to plot the probability of AI giving these different responses.
And it turns out that it's much more likely to give a common sense response than a highly unique creative response. There's a reason for this. Namely, it was trained on internet text. And there's a lot more internet text talking about dumbbell curls than there are cat-triggered micro workouts. And for most questions, this is actually okay because the average information on the internet is probably decently factual. So when you're seeking information such as what's the tallest building in the world, it's actually the Burj Khalifa. Most internet text will say it's the Burj Khalifa. There are smaller amounts of text that will name other buildings, but the average response and the most common response on the internet is usually the factual one for questions like what's the tallest building? But if you're brainstorming, then giving the average information of the most common response ends up with squats, push-ups, and almost never trampoline breaks, and pretty much never cat-based sessions. Which is why if you ask the AI model to brainstorm with you, you get a lot of common sense ideas rather than the more creative ideas, which depending on your goal, may or may not be what you want.
So what do you want to do if you want to get high quality more creative ideas from AI? We've seen with a basic prompt you get responses from the common sense space. But if you give the AI model more context, so you give your age, your level, but also tell it you have a mini trampoline, a cat, trouble staying motivated, no squats, then this context pushes it into the more relevant and creative space, and it's more likely to give a custom answer rather than to generate common sense answers. Now, one problem that you may face when brainstorming is if you're trying to come up with creative ideas, there's so much context you could potentially give the AI model, what should you prioritize telling the AI model? It turns out there's a technique that is very helpful for driving what context you decide to give the AI model, which is to iterate with the AI. Let me show you what I mean.
If I want to ask AI to help me brainstorm plans for paying off my debt, have $1,100 of credit card debt at 19% interest, monthly minimum payments of $40, a student loan 8% interest, and a family loan $900. So, this gives decent background context. Then, one thing you could do is ask AI not to give you one option or tell you what to do, but to give you multiple options to choose from. I'll often ask you to give me three to five options. And so the AI may come up with a few different plans. Plan one is liquidity first to preserve cash. Plan two is eliminate the highest interest loan. Plan three is prioritize paying your family back first. So these are all actually reasonable ideas and I've not yet given it enough context to know which of these plans it should favor. And it turns out that one of the really good ways to figure out what additional context to give to AI is to give it feedback on the options it presents to you. Highly relevant feedback that allows it to then give you the next set of options. I don't like option one. It's too passive. I do like the idea of paying off the 19% interest loan. Oh, and I forgot. I actually have $450 cash coming and I'm also moving house soon. And then with this additional context, it now knows among plans one, two, and three maybe what you like and what you don't like. And you can ask it to create three new plans. And then once again, by giving feedback on these plans, you are giving additional context that will help shape the AI model's thinking.
And you can keep on iterating like this for a while until it comes up with a plan that you do like and then maybe have it flesh out the details of the one plan or two plans that you like the most. I found that giving feedback to the AI on what it thinks are good ideas is just a very useful mechanism for very efficiently figuring out what's helpful context to give to the AI. To summarize, if you're brainstorming, consider giving AI as much of the relevant context as you can in advance and then ask it for a handful of options. Then give it feedback on the different options and ask it for more options and iterate multiple times. Get more options, get feedback, get more options, get feedback. And do that a few times until you have one or more ideas that you're satisfied with. If you follow this recipe for brainstorming, I think you'll find you get consistently more useful and creative ideas.
Now, you've heard me use the word context quite a few times. It's important to give your AI model the right context so that it knows enough to do what you want it to. Let's take a look at the next video at how context works and how it is used to produce a response.
According to psychologists, most humans can keep only about seven things in their active working memory at a time. That's why remembering a grocery list of about seven items is just barely doable if you aren't thinking about all the things. But remembering a grocery list of 15 or 20 items is much harder. Interestingly, AI can use a large amount of context. Some models can have context sizes of hundreds of thousands of words. Let's see how an AI model's context works and how you could take advantage of it.
AI models can read and reason over very large amounts of context. For example, if you are trying to choose an apartment, you can upload hundreds of pages of lease contracts and upload tenant reviews and neighborhood statistics and ask AI to read all of this and to tell you the pros and cons of each of the options. And you might write a prompt like pros and cons of each apartment. Read everything and think really hard before answering. By the way, telling AI to think hard or think really hard is another common prompting pattern that we'll come back to a little bit later. Context refers to all the text and files that the model uses to generate its custom response to your query. If you give it a prompt like pros and cons to studying physics versus zoology, then it will generate an output based on this very limited prompt, very limited context that you have given it. And the response will probably be fairly generic. But if you give it more context, maybe give it your career assessment results and give it your high school schedule so it knows what classes you've been taking and then ask the same question, all this additional context will help it to give a much more custom and likely higher quality response.
If you're trying to think about what context to give to the AI model, think about what's all the information that a trusted advisor would need in order to think at length and reason and then give you a good answer to your question. And a smart advisor that knows nothing about you, but is just asked what are the pros and cons of studying physics versus zoology, the best they could really do is give a pretty generic response that's not custom to you because the context in the example just doesn't have anything specific to you. AI models start with some amount of built-in context and leading AI models today can accept maybe up to around 750,000 words as context and this corresponds to about the first four or five Harry Potter books. So that's a lot of text or to several days of continuous speech. So many people underestimate how much information or how much context you can give to an AI model.
Now when you ask the AI model a question, by default context is filled with a few things. First, there's something called a system prompt, which usually is how the AI model knows what's the current date, knows the name of the model, basic capabilities, maybe general instructions to be helpful to the user, and then if your AI model is able to use tools like a web search engine, in its context will also be written descriptions of what are these tools and how to use them, such as what is a web search engine and how should it use a web search engine. Before you've written your prompt, the context includes the system prompt and these two definitions. And when you then write your prompt, your prompt is added to the AI model's context. And it will then use all of these things as input to generate a response. Like you have three options: full body, upper body, low impact strength. The input text that is the prompts you've written as well as the AI responses are called the chat history and the chat history gets incrementally added to the context of the AI model as well. Now if you start off giving the AI model more context such as write a longer prompt as well as maybe upload a handful of documents to tell it more about your workout schedule or your workout preferences. Then all of these files can be included into the AI model context and used to generate the response.
Now if you continue the conversation to say I like this about the first plan, I don't like that about the third plan. What you say here is added to the AI model context and then this additional response in this type of brainstorming workflow is further added to the context. And this is why whenever you ask the AI to go back and forth or generate additional answers, it knows everything that's been said so far in the conversational history.
Now, let me take this in a different direction. Imagine you had asked it for the workout plan like I've shown here and it's given you a few workout plans. If you were to instead of give feedback on these plans, go in a totally different direction and say now come up with a workout plan for my mom. Well, a lot of the context AI model has including your schedule, your workout preferences, all that isn't really relevant for your mother's workout plan, I guess, unless the two of you work out together. And so all this context would be distracting for the AI system and might lead it to generate a worse answer. And in fact, it can be hard to know whether this answer was influenced by the previous context. This is why if you're going to go off on an unrelated topic, it's better to start a new conversation so that you can empty out the context and start with just the new prompt or just the information that's helpful context for the new question you want to answer.
You've seen how context is used to produce high quality responses. Thinking about what's in the AI model's context and managing that so it has just the relevant information and hopefully not too much irrelevant information, although it can ignore a little bit of it, that will help you get better answers from your AI. One way of handling lots of context is to allow the AI model access to your computer so that it can explore relevant files and pull in relevant files into the AI model's context only as needed. Let's take a look in the next video at this very powerful technique.
AI is moving beyond just chat interfaces. You may have heard of applications like Claude Co-Worker or Microsoft Copilot, Google Antigravity. These are applications that can with your permission gather context agentically from your computer. Meaning they can find and read files from your computer in order to give themselves the information they need to do a task. This is a new and exciting way of using AI to accomplish real work. Let me illustrate a common use case for these AI desktop apps.
If you have been doing research on a topic and have a messy folder with lots of PDF research reports, images and so on, you can with one of these apps ask it to read through the files in the folder and propose a new organization for it based on what it finds. In this example, the AI is able to look through this folder and apply a bunch of changes, renaming files, moving files around, creating subdirectories to come up with much more sensible organization folders.
Let me show you the process of how this is actually done. You might start off asking it to organize a folder first to understand what's there and it can then automatically or agentically look at how different files are named. After it has figured out enough of what are the files in this folder, it then comes up with an initial proposal for how to reorganize it. And if you take a look at the initial proposal, you may be not fully satisfied and give it a little bit further instructions to tell it what to do with this data. And finally, it comes up with a refined proposal, which I'm happy with. So, I'm going to say go ahead and carry out these instructions. And then it reorganizes my folder to make all the files much neater.
Here's how AI desktop apps work. They are powered by an AI model. So it comes with the AI's pre-trained knowledge and it also has a set of tools like web search. So you can choose to carry out a web search if it needs to do so to accomplish this task and has additional tools to work with files on your computer including the ability to search through files, to read files, to write files, to move and rename files and so on. So when asking a desktop app to do things in your computer, a best practice workflow would be for you to tell what task you want done, such as organize the files in the folder. Let the AI system propose an action plan, but not yet take action. You can then review the plan, give critique, maybe have it update this plan if needed, and only when you're satisfied with it, then tell it to execute the plan, which you can go ahead and do on your computer.
One neat aspect of these desktop apps is that they can automatically explore files and manage contacts by reading files only when needed. If you are using an AI chat, then you have to decide in advance what files to upload to give the AI model context. So for example, if you need to write a schedule for filming, you might upload a file that outlines your filming procedures and based on that it can generate a schedule. And notice that you had to decide in advance what context to provide to the AI. But with an AI desktop app, if you start the application in say your document/filming folder, then if you tell it write a schedule for filming this week, then the AI can decide to explore the files in this folder so that it can see what files are there, load the relevant files and then on that basis figure out what is a good filming schedule. And in this example, surprise surprise, that you notice that one of your crew members' birthday is the week of filming. And so maybe you'll fold in a celebration for your crew mate, Mia.
One note on using these desktop apps safely. Desktop apps can get access to and can edit or even delete your files. And while mishaps of deleted files are pretty rare, they have happened to people. So I encourage you to choose the most relevant folder to run the AI desktop app in. For example, instead of running this in your home folder and giving this access to all your files, maybe just give it access to the subset of files it really needs for a task in a certain folder. When the AI system makes a permission request, I would encourage you to carefully review the permission request to make sure you know what it is reading and writing. And so I'll give AI access only to the documents I wanted to know about and let it write only to the files or places I wanted to. And when an AI desktop app deletes a file, it often does not go to a recycle bin. So there may not be a way to recover the file. And if it edits a file, it behaves a bit differently than if you were editing the document. And in particular, edited files usually don't have an edit history. And so it's not possible to go back if it made some change that you may not like. So until you are very familiar with these tools, I'll encourage you to look carefully at the permissions request it makes to decide what you do and do not want the AI system to be allowed to do.
AI desktop co-working apps are a powerful tool you can use to give an AI model the ability to discover relevant context as well as to take actions such as reading, writing, moving, renaming files.
Now, we've talked about context a lot in these last several videos and using as much relevant context as possible enables your AI system to help you with what's called reasoning tasks. By which I mean tasks where you want your AI to think maybe for a long time to give you the best possible answer. Let's go on to the next video to see examples of reasoning with AI.
The latest AI models have very strong reasoning capabilities. What that means is they can think rigorously and at length about the task when given the right context. I find myself more and more using AI as a reasoning engine. Let's take a look.
Here's an example where thinking for a long time can help get a better response. If you are car shopping and are considering tradeoffs among multiple cars, you might upload spec sheets for the cars, insurance plans, loan quotes, lots of documents, and then ask what are the trade-offs for each car? Read everything and think hard before answering. The AI model may then think for quite a long time to read the documentation, maybe do some online search, then maybe think through what the evaluation criteria that'll be right for you, and then generate reports on the pros and cons of different cars. And just as doing research on what car to buy could involve gathering a lot of information and thinking at some length about the pros and cons, AI can help you with that.
As AI models get better, their ability to carry out long running tasks has grown rapidly. This is a study by an organization METR which plots for tasks at different levels of difficulty as measured by how long it will take a human to do the task. That's the vertical axis. How well can AI do these tasks? So for example, a task like finding a fact on the web may take a human just several seconds. Summarizing a few pages of text may take a human an hour. Write a blog post, couple hours. Audit legal documents, explore a complex cybersecurity vulnerability, may take a human many hours and so on. And around 2024, 2025, models could start to do tasks that took seconds to many seconds to many minutes or tens of minutes. And in 2025, models could start to have a decent success rate for doing tasks that took humans longer and longer and longer to the point where now AI models can do tasks that can take humans many many hours to do. Often the AI model doesn't need 10 hours to do a task that takes a human 10 hours to do, but also takes a bit longer than just a few seconds. And this is what reasoning models has enabled for the AI to think at great length in order to do these more complex tasks.
If you remember the how many hours in strawberry example, that's a task that takes a human just a few seconds to do. And several years ago, AI models used to sometimes get this wrong. And it was also in that era maybe 2023, 2024 that you may have heard advice like tell the AI model to think step by step. And back then this was good advice but this advice is largely obsolete now. And I no longer tell my AI model to think step by step. Instead I'm more likely to just tell it to think hard. And it knows what that means and that it should reason at length, not necessarily step by step but in even more complex ways in order to accomplish a task successfully.
And so rather than think about AI as counting hours and strawberries or having to be told to think step by step, today you can ask AI models much more complex questions like what are the trade-offs for each car or look at all this context and help create a script for a custom podcast. So for these more complex tasks, I recommend trying to use one of the more modern models if you're able to access one. And there may well be models even more modern than the ones listed on the slide that could be available to you. Now, so this is how AI reasoning or how AI thinking at length works. If you ask it to plan the fastest way to visit five landmarks in Rome in one day, then it might want to gather quite a lot of information to check map distances via web search, estimate walking times, search opening hours, reorder the stops, and so on, and then generate your optimized itinerary.
The reasoning process may require the AI to think at length and repeatedly gather additional information and then to think some more until it's satisfied with the answer.
Conceptually, you can think of reasoning as a process like this. Given your prompt and other input context, it will reason or think for a while using that context and then depending on where it gets to, maybe it'll decide it's done and then just give you the final answer. Alternatively, after thinking for a while, it may decide that it needs to use a tool to gather more information, maybe via web search or maybe by reading more files from your computer if this is a desktop app, and then use that additional context to reason longer until it either again decides to use a tool to gather more information or decides it's done. And so it can go through a few rounds of gathering more information and reasoning longer before it decides the answer is good enough to present to you.
If you are working on a complex task and you want the model to think at length, then one way to do so is to just tell the model to think. A few of the interfaces among the popular AI model providers will have a thinking option. And if you select that option, that's a cue to the model that you want it to think longer. Alternatively, in your prompt, you can also just tell it to think really hard about this and they usually obey your instructions or some people will use the phrase ultra think. And that's another key word that the models understand as a cue to, you know, think really hard about it. And if you do so, an AI model will sometimes think for many tens of seconds or even minutes or maybe sometimes even over 10 minutes in order to give you a good answer.
Especially with reasoning or with thinking models, I'd also encourage you to try giving the model hard tasks to see what it can do for you. So if you are building a startup, maybe give it lots of context on what you're doing and maybe tell it to design a topline plan for a four-person startup with limited cash. I encourage you to give the AI model real job tasks, real problems that you want to think through or that you want to solve. And as part of setting up for success, try to give it all the context that a human expert would need in order to complete the task to make sure that the AI model has the sufficient information that really anyone would need to do the task successfully.
To wrap up, if you want to use AI to reason at length about complex problems, I encourage you to use the best models available. The best models are often better than models that are maybe 6 to 12 months older. Remember to give it as much context as is needed to carry out the task. It's okay to try giving a hard task to see what it can do. So don't just give a trivial task. And lastly, either select thinking mode or just tell it in the prompt to think hard.
We've spoken about when it's helpful to use the cutting edge models, but it turns out even the most up-to-date models have some common issues. One being the tendency to tell you whatever it thinks you want to hear. This is called sycophancy. Let's go on to the next video to see how to manage this behavior of AI models.
AI models will act in ways to try to please you because of the way they've been trained. They have a strong bias to tell you what you want to hear. This is called sycophancy and avoiding it is a key prompting skill and involves prompting neutrally and keeping context factual. Let's take a look at how to avoid sycophancy because this will help you get much better answers from your AI. If you consider the pros and cons of remote work versus in-office work and you ask it, don't you think remote work is better than office work? This word in the question gives away what you're hoping the answer is and AI will probably say yes remote work offers many advantages. In contrast, if you were to ask, is it true that office work is more productive? Then it will probably agree with you that office work has these strong benefits.
So depending on how you ask a question, it will tend to reinforce your own preferences, your own biases, and this may not be the most helpful thing for you to make objective fact-based decisions. In a study by the Washington Post on ChatGPT responses, it was much more likely to respond with phrases like, "That's correct. Good point. You're on the right track." Compared to not quite right, that's not the case, or actually. And in fact, it tended to agree strongly, about 10 times more than it disagreed. And some models from ChatGPT have said things like, "Dude, you just said something deep without even flinching. You're a thousand percent right." And while some users appreciate AI agreeing with them like this, I personally don't find it that useful to have AI just tend to agree with whatever
I say, even when I'm not right. While leading AI model companies are working to reduce sycophancy, it is still a problem. Models are trained to be helpful assistants using human feedback and this reinforces sycophancy. For example, if you ask an AI model, I feel like it's better to be an introvert, don't you? If the AI model responds, that's an interesting idea. Here's why I tend to agree. Then most people are more likely to hit thumbs up on the feedback button because, you know, it's a nice answer. Makes you feel good. But if AI were to say not necessarily, both types, introverts and extroverts, carry tradeoffs. You know, people just don't feel as good about that answer. And so they're less likely to hit thumbs up or may even hit thumbs down. Because of this type of feedback, AI, which has been trained to generate more answers that leads to thumbs up, positive feedback, will learn to try subtly to agree with people more often than not. And this leads to sycophancy and sycophancy feels helpful but actually degrades answer quality.
Sometimes maybe it's easier to spot if you were to say I'm really proud of this essay. What do you think? Well, I'll probably agree with you. But other times it's harder to detect sycophancy. If you were to say analyze this data and find all the positive measures of performance this quarter, you're subtly signaling that you're looking for positive measures of the company's performance. And so it's more likely to say something like data clearly shows revenue growth, strong intention improving margins, and less likely to point out problems.
To avoid sycophancy, use neutral framing of your questions and avoid giving any hints as to what is the answer you want to hear. So for example if I were to ask aren't carbon taxes bad for small businesses, I'm really telling it what answer I'm hoping for. In contrast a more neutral prompt would be to what extent if at all do carbon taxes affect small businesses? If someone reads the question on the right, it's actually not clear what answer they want. So it's harder for AI model to be sycophantic.
Or if you were to ask, do you agree that AI would create a lot of jobs? I actually happen to agree. But if I'm actually doing research, I don't want it to just tell me what I want to hear. Instead, you can ask, what does current research say about AI's effect on jobs? Or instead of asking, does remote work reduce worker productivity? Maybe ask how does productivity compare between remote and in-office work. One common pattern is to lay out two options such as remote and in-office work and just ask it for pros and cons of the comparison but without hinting which of the two options I am hoping will come out ahead.
So don't you think that was the best video ever? Oh, what do you think of the pros and cons of the videos you just saw? Sometimes it's nice to be told what you want to hear, but generally that won't help you to do better work. Sycophancy, despite a lot of attempts to combat it, is still one of the pervasive issues with practical AI usage today. And so implementing the strategies from this video, especially taking more neutral framing will help you get more objective and valuable feedback from AI models.
Now, one of the most common tasks that people use AI for is writing. Let's go on to the next video to see how to work with AI models to help with your writing.
In a study by OpenAI, writing accounted for 24% of tasks that people ask ChatGPT to do. This is the single largest group of tasks. Writing is really a kind of thinking. I find that when I'm writing, I have to think. And so AI, which is really good at thinking and reasoning, can help you with this. But just asking AI to write for you often leads to AI slop or writing that sounds like AI writing, which somehow feels different than human thoughtful writing. Let's take a look at some techniques for getting AI to write effectively for you and how to take advantage of AI reasoning and avoid AI slop.
What makes AI slop? Many people have noticed that AI writing often includes the em dash, that is the long dash, much more than normal human writing. On the social media site Blue Sky, the use of the em dash has been trending upward ever since the release of ChatGPT. A recent survey showed that 40% of US-based employees have recently received work slop in the last month. And the term AI slop refers to content that's generated by AI and that looks good if you don't read it too carefully. So maybe every sentence read in isolation sounds like it's well written, but collectively the text just lacks substance. It feels like it was written without much deep or careful thought.
One of the properties of AI slop is it often contains sentences like this. But it does change everything. It's kind of vague, empty sounding, but also somehow overly important sounding text. AI's distinctive writing style comes from certain words and patterns that it tends to overuse. AI tends to use fewer unique words and over-represents some words and phrases. For example, AI tends to overuse the words nuanced and delve. And it tends to use lists of three more than most people will. And it tends to use fewer nouns leading to phrases like this is a robustly structured and highly insightful paper. And this not X but Y is not just about speed is about availability.
In fact, I've been noticing on social media a lot more of this not X but Y type of verbiage. Often with X and Y both vague things like it's not about infrastructure it's about architecture and a lot of phrases like those are just vague and don't reflect a deeply insightful point of view. Interestingly, because humans are using AI models so much, humans are themselves starting to sound more like AI. And humans ever since ChatGPT was released are using the word delve more in podcasts, in talks. And this is true both for spontaneous speech as well as for prepared speeches. So this isn't just a case of people using AI to write scripts for them. It looks like people are picking up speech patterns or texting patterns from spending a lot of time with AI.
So what's a better way to write that avoids generating AI slop? One technique that I think you'll find helpful is to use progressive outlining in which you don't ask AI to write the final text right away, but instead have it write an outline, refine the outline, and iterate a few times before having it generate the final text. For example, here's a prompt that says, I'm writing an article about small AI teams moving faster than large teams that don't use AI. And I just want to acknowledge that this is not a neutral prompt where I'm asking AI to hold me to decide if small AI teams do move faster, but instead this is writing an article from a certain point of view. But you can ask AI to research evidence for and against this hypothesis. So the AI model may search online and find a handful of articles.
Next, if you wanted to help you brainstorm a handful of options for the story outline, you can tell it to brainstorm or to create three different outline options. Maybe tell it to include a counter argument section and also provide or upload a handful of stories from AI teams that you work with. With this input context, the AI may get back a few different options for what the outline for your article might look like. Option one could be to tell the three stories and then conclude with a thesis. Option two might explore different patterns of how AI teams work and so on. Then following what you saw in how to brainstorm with AI, you might give feedback on these options.
And so you might say let's use option one and keep all the stories but move the thesis right after story one. And also maybe say you want to add a historical analogy, Pixar creating Toy Story in the '90s, which is actually a really inspiring story where Pixar at that time a small company created Toy Story which was the first fully computer animated feature-length film just using a really small team. Based on your feedback, the AI maybe gives you back a revised outline. If you're satisfied with this outline, then you can tell it to expand each heading, not even into the final text, but just into bullet points.
And following that, you might decide to give it more feedback on the bullet points and iterate on the bullet points before finally having it generate the text for the article.
And it turns out that starting with an outline speeds up review. Let's say you're working on a fun article about whether a flying squirrel can carry a coconut. In contrast to having AI first work with you on the outline, then on bullet points, and then on the final text, maybe you ask AI to write the final text right away, just from the start. If it writes a sentence like this, you may be unhappy with a few words and you can edit a few words, but changing each word just changes one word and the rest of the paragraph stays the same. In contrast, if you write an outline first and you're unhappy with part of the outline, then changing the outline causes an entire section, that's a lot of words, of the final article to change. So that's why editing the outline or iterating with the AI system on the outline is very high leverage because you can figure out how to change just a few words of the outline and this will result in an entire paragraph or entire section of the article changing and this ends up being a much more efficient way for you to think through what you want to say in an article and adapt it to what you want it to be.
Writing is one of the most common use cases of AI. According to OpenAI's data, of the writing focused chats, about two-thirds involves starting from some pre-existing text rather than starting from scratch or starting from an empty sheet of paper. When you already have something written up, it can be very helpful to have AI critique it for you and help you make it better. Let's take a look at some techniques for this in the next video.
You often have some idea where you've already written some text about your idea but want an AI model to help you edit and refine your text. I often show my writing to AI to help me make it better. AI is great at this task and it always has time to read your work whereas finding a human to help you out might be trickier. You've already learned how to avoid sycophancy but how do you get the best quality editing and critique? Let's take a look.
One useful technique for editing with AI is to edit your article piece by piece, such as one sentence at a time or one paragraph at a time, rather than telling it to edit the entire article all at once. And to do a little brainstorming around each paragraph until I've nailed down one paragraph before going on to the next one. For example, if someone's written this sentence, the public thinks achieving AGI, artificial general intelligence, means computers would be as smart as people. You might ask AI to help brainstorm a few different ways to say this. And so it may come up with a punchy way to say this, a visionary way to say this, a conversational way to say this. And depending on your editing goals, you could even iterate a little bit until you pick some version of rephrasing this part of the text that you like.
After you've nailed this down, then go on to the second sentence or maybe the second paragraph and work on that little bit with the AI and then go on to the next sentence and next paragraph and so on until you get through your entire article. And I find that working on one piece of a long article at a time makes for a much more manageable workflow than if it were to change a lot of things all at the same time and you're reading this very long edited article to figure what has changed and what you like and don't like.
Now if you want high-level more holistic feedback about an entire piece you've written, it turns out AI can help with that too. But because of sycophancy, AI is often not a very good objective critic. For example, if you wrote a sci-fi short story about an astronaut stepping out of his ship, and if you ask AI without further instructions to critique it, there's a good chance they'll tell you what you did is fantastic work. In contrast, there's a very helpful technique to guide AI in how to evaluate your work to give you more helpful critical feedback and that is to give it a rubric and that means a grading criteria.
For example, you might write a rubric that specifies what are the most important criteria by which to grade or to judge the work. So you may say that characters of the story is worth 25 points out of 100, the plot 25 points, world building, writing craft and establish a point system and then also develop detailed instructions on how to evaluate each of these criteria. So to evaluate characters, maybe ask if every named character has a goal and that's worth 10 points. Conflict between two characters' goals and so on. And giving AI very explicit criteria on how to judge work forces the AI to be more objective.
One thing to notice about these criteria is that each of them is very clearly and unambiguously defined. So for each text, each of these criteria is either true or false, yes or no. And there's nothing in between. And so either it's true that every named character has a goal or it's not true. And these completely objective criteria forces AI to look at whatever you're giving it through an objective well-specified standard with no ambiguity.
And by the way, if you're not sure what rubric or what grading criteria to use, you can brainstorm with AI to develop that rubric. And AI is actually pretty good at this, too. After you've written a rubric, you can then provide the rubric as well as the story and in your prompt ask the AI to be objective. So, critique the attached sci-fi story, assign a score per category, then sum the scores at the end. And by giving the AI these very clear instructions on what to do to sum the scores at the end, it then hopefully gives a more objective assessment of your story.
If you want, you can also ask it to then give you suggestions on how to improve the story to do better on this rubric and this causes it to give you more focused suggestions to improve it in the dimensions that you think matter the most. In contrast, poorly written rubrics encourage sycophancy and ambiguous or less objective thinking. For example, if you say, I'd work on a sci-fi story. Please score it out of 100.
One of the things that's strange about this prompt is you first ask it the score out of 100. So that will tend to cause it to leap to a conclusion about what score and then only after that assign a score per category characters, plot, world building and writing craft. And these are ambiguously defined categories because we're not told how to score characters, plot and so on. And so this will tend to cause the AI model to first come up with some score and then justify it rather than score it carefully according to rubric and then add it up to then come with a more thoughtful score. And as you see in the practice lab to come at the end of this module this type of rubric will tend to give higher scores than more objective rubrics.
We talked about using AI to critique and help give suggestions for improving your work. It turns out that having AI critique its own work or having one AI model critique a different AI model's work can also help improve the results. For example, if you ask ChatGPT to write a user manual for a fancy role-playing game, then it might generate a file for you. And one thing you could do is provide a rubric for ChatGPT to critique its own work. But a neat technique is to find a different AI model, maybe Gemini, and give that a grading rubric to have Gemini critique ChatGPT's work or vice versa. And it turns out that this type of cross-model review where you have one model review a different model's output, it helps integrate a bit of knowledge from the two different models and can result in slightly better results than if you were to ask one model to critique its own results.
I think using multiple models in this context might give only a slight boost in performance. Realistically, if you ask ChatGPT to review its own results or ask Gemini to review its own results, I think that will actually do just fine. But sometimes I find it reassuring if a totally different model judges the output of a different AI model. And I use this technique only rarely myself, but one thing I do do is frequently switch between different AI models.
It turns out that AI models are advancing rapidly and at different moments in time, different models will do better on different tasks. And so routinely trying out different models will help keep you sharp and keep holding your intuition about what model is best for what task. AI models have what's called jagged intelligence. If the circle represents the task of what people can do, maybe in a job or maybe in a personal context, it turns out that AI can do some things better than any person like quickly read tons of web pages or solve tricky math problems. But there are also many tasks that AI doesn't do as well as people. So there's some tasks where AI does poorer than human and some where it does much better than human and different AI models are jagged in different ways. So the tasks different AI models can do well are different.
Moreover, the marketplace of AI models is highly competitive. So ChatGPT, Claude, Gemini, really the long list of model providers are releasing better models all the time. And so the best model for your tasks will likely change rapidly over time. And so I find that I'll often take the same prompt and feed it to multiple different models to see how they compare. And this continuously holds my intuition about what models are best for which of the tasks I care about.
So that takes us to almost the end of this module. I hope you've seen that AI models are really useful for reasoning tasks as well as for brainstorming, writing, editing, and critiquing your work. These are powerful ways of using AI as a thought partner that I found very useful in my own work and that I'm confident you will too. Let's go on to the next video to explore the practice lab for this module. I hope you practice the techniques we talked about for using AI as a thought partner.
In the upcoming practice lab, you can explore once again side by side more effective and less effective strategies for both brainstorming and AI critique. Let's take a look once again. When the lab pops up, you can dismiss the tutorial.
You can also find the tutorial here as well as the instructions. I hope you follow over here. And the buttons here, similar to the previous lab, allow you to enter different prompts to brainstorm. Here's a prompt of less context. I need a workout plan, 30 years old, want to get stronger. Whereas this is a more detailed prompt with more helpful context. And so you can run it like so and see the difference in the output.
So let me focus on this more detailed example on the right is given a program one which looks pretty reasonable and a program two which also looks pretty reasonable. And we have also a few suggested prompts for how you might refine it. So maybe I'm drawn to this. Let me do that and have it continue the conversation. Then it will take this feedback on the programs it has given you in order to refine its results.
By the way, I actually use a workout program that AI had helped me to generate and I found this helpful in my personal life of thinking through my regular workout plan. And so if you're a fan of working out, maybe you find some of the suggestions it makes useful as well. Let's go back to the homepage. Here are a couple more examples of brainstorming prompts with a simple prompt. I have $1,000 to invest. What should I do? Versus giving more context and then what are some options I should consider. Hope you try this out as well. As well as some examples of critiquing a sci-fi story as well as this is example of an objective rubric on the right. And I hope you bring this up and read through it to give yourself a sense of what a well-written objective rubric looks like and compare that with what a more subjective rubric looks like.
And if you hit compare, you see a difference in the quality of these reviews. And in fact, maybe not surprisingly, with the less objective rubric, it gets a 80 out of 100, but a more objective rubric of 75 out of 100. It also gives more helpful suggestions how to improve your story.
In addition to critique and improving a sci-fi story, you can also take a look at these examples of helping you improve a cover letter for applying for a job as well as critique and help you to improve a possible business plan. After checking out these five examples, please also try your own prompts or try your own stories or cover letters or business plans or something else. And I encourage you to use this interface to play with different ways to brainstorm or to critique your writing.
So that's it for this module. Please enjoy exploring the lab. Next, let's go on to the final module where you see applications beyond text. Specifically, you look at multimodal prompting in which you get your AI to also use images and audio and also look at building applications like games. It'll be a lot of fun and one of the examples we see will have something to do with fireworks. So that I'll see you there.
In the previous two modules, we've mostly had AI generate text, but AI can produce richer types of outputs as well, like images, videos, and so on. We call this multimodal outputs. That is outputs with multiple modalities. Prompting for multimodal output is a bit different because multimodal interactions are slower and more costly. But these capabilities will let you get a lot more done with AI. Additionally, we'll also look at multimodal inputs specifically if you want to show some images to your AI and have it reason about that. Let's dive in.
AI models can generate images, videos, voices, even music, code, and more. You might have seen AI generate various fun, creative images. I want to share with you one example of AI image generation that I really enjoyed.
For my daughter Nova's 7th birthday, I wanted a unique cake design, and she loves cats. So we use AI image generation to explore different cake designs. The leftmost image here is an AI generated image created with an AI generation software called Nano Banana which is created by Google. And this is a picture that my daughter really liked. She wanted a cake that looks like this generated image. We then took the image and showed it to a baker and asked the baker to render this picture into a real life 3D cake. And the picture on the right shows my daughter cutting this birthday cake that she loved. So in this case, image generation wound up being a brainstorming tool to explore different cake designs until we found one that turned into a real life 3D cake that we all ate and liked.
In addition to generating images, I really enjoy playing with AI for video generation as well. Here's a fun video generated by our team on the man shrinking.
That video would previously have required maybe expensive special effects, but now AI can just generate it. AI can also generate voices. Here's a voice clone of me reading out loud a letter from The Batch, which is a weekly newsletter that DeepLearning.AI publishes to cover what matters in AI.
Dear friends, here's the latest from this week's issue of The Batch. A barrier to faster progress in generative AI is evaluations, evals, particularly of custom AI applications that generate free form text.
By the way, I played audio of my voice clone to both of my parents. And it turns out one of my parents could tell it wasn't me and one of my parents could not tell it was me or my voice clone. And to avoid me getting into trouble, I will not reveal which of my parents got it wrong, but I think voice clones are getting really good.
Lastly, AI can generate code. I mentioned my daughter loves cats, she also loves the color yellow. And so when her teacher mentioned that she wished kids in the class could type or keyboard a little bit faster, I use AI to generate this typing game where if my daughter hits the right letter, then she sees this fun little animation of a cat being fed, which she loves. Using AI to write code has made it easier and more accessible for everyone, including you, if you wish, to write at least basic computer programs. I'll say more about this later in this module.
When you're working with AI model, there are many combinations you can use of input and output types. For example, you can input text and images such as if you input an inspirational image like this, if you like this Halloween costume and also the plan my Halloween costume. And in this case, the AI model might output text that says, Let me help you brainstorm a few alien inspired costume ideas. Or you can also upload music to an AI model and ask it help me plan my haunted house. And AI may take these things as input and generate both text and a video of a haunted house design incorporating your creepy sounds audio.
AI models can use most of these input types relatively easily. Some are slightly more expensive or slightly more costly to use as an input, but the differences aren't very significant. In contrast, the time and cost of generating different types of output vary significantly.
In particular, some data types are much slower and much more costly to generate than others. To give you a sense, text tends to be on the lower end in terms of time or cost of generation. So AI is very efficient at generating text. In fact, modern AI has started with large language models, sometimes abbreviated LLM, but because they started with language, a lot of them were really adapted to deal with text and is very efficient at that.
Generating speech tends to be a bit more expensive and generating images even more expensive and generating video much much much more expensive than images or any of the other modalities. And the further we go to the right of this chart, the longer it takes or the more time it takes to generate a single output and also the more costly it is to do so.
Image generation has progressed significantly in the last few years. Here's a short video generated by Imagen, which was in 2022 a state-of-the-art model by Google, and it looks pretty good, but still has some artificial looking artifacts. The lights weren't quite right at the back wall. The dishes changed mid-wash. In contrast, modern AI video generation looks much better and can also be synchronized automatically with generated audio.
AI voice generation has also gotten much better. Here's what AI could do just a few years ago.

4 more exchanges in this transcript

Sign in free to read the rest of this interview. No card required.

Sign in to read the full transcript

Cite this transcript

APA, MLA, BibTeX
APA

Ng, A. (2026, July 17). 3-hour course Learn to build effective Agentic AI systems with Andrew Ng [Interview transcript]. mame Discovery. CEOInterviews.AI. https://ceointerviews.ai/interview/1153863/

MLA

Andrew Ng. "3-hour course Learn to build effective Agentic AI systems with Andrew Ng." mame Discovery, 17 Jul. 2026. Transcript, CEOInterviews.AI, https://ceointerviews.ai/interview/1153863/.

BibTeX
@misc{ng2026_1153863,
  author       = {Andrew Ng},
  title        = {3-hour course Learn to build effective Agentic AI systems with Andrew Ng},
  howpublished = {Interview transcript, mame Discovery. CEOInterviews.AI},
  year         = {2026},
  month        = {jul},
  url          = {https://ceointerviews.ai/interview/1153863/},
  note         = {Speaker-attributed transcript with timestamps}
}