WhoBuilt

Master Cursor in 50 Minutes with Cursor's Head of AI Education

Aug 17, 2025· 50 min· 78K views·Watch on YouTube

Speaker

Lee Robinson, Cursor’s head of AI education and former Vercel developer experience lead, joins Peter Yang to discuss building apps with AI and using Cursor in established codebases.

Why Lee joined Cursor

Robinson says AI coding tools moved beyond autocomplete as models improved and agents began writing more usable code. Background agents handling small tasks, such as documentation fixes and UI bugs, convinced him software development was changing and motivated him to help developers adapt.

Plan before asking an agent to build

Robinson walks through planning a music listening tracker with Google sign-in, Spotify data, a database, and a defined frontend stack. He recommends treating the plan as a living document, asking the AI to clarify missing requirements, and understanding technical choices rather than accepting them blindly.

Give the agent ways to check its work

Robinson uses business logic tests, end-to-end tests, TypeScript, and linters to provide feedback an agent can act on. In the demo, Cursor sets up the project, runs tests, fixes a failing page check, and commits the working setup. He also shows project rules for recurring instructions and starts a fresh chat when earlier context is no longer useful.

Use AI while learning software fundamentals

Robinson distinguishes throwaway prototypes from software that must be maintained with teammates. He sees AI as useful for routine tasks such as reformatting or parsing data, while engineers still need to understand the code and systems they work with. For newcomers, he recommends learning by building and asking questions while also studying fundamentals like loops, data structures, and APIs.

Generalist engineers can connect tools and services

Robinson describes Cursor as moving quickly, with engineers taking broad ownership across product and engineering work. He recounts an engineer writing a carefully tested script to issue Stripe refunds and email customers, including dry runs and checks for failures. The example shows how engineering judgment helps turn flexible tools into reliable workflows.

Takeaways

  • Write down product requirements and technical assumptions before handing work to an agent.
  • Include tests, linters, and type checks so agents can use concrete feedback to correct mistakes.
  • Review generated plans and code, and ask the agent to explain unfamiliar files or choices.
  • Use fresh chats when old context no longer helps with the current task.
  • Build with AI while learning core programming and system concepts, especially before shipping software that handles data or API keys.

Mentioned in this talk

Search inside this talk

What was claimed 15

Related talks