Central argument

  • Theo rejects the idea that better prompting mainly requires more elaborate prompt engineering. He argues that engineers over-engineer requests while underestimating the range of work agents can perform. 0:00 0:19
  • His phrase "prompting hard enough" means reconsidering what to delegate, including everyday work beyond coding. It is an invitation to ask for broader outcomes, rather than a recipe for more detailed wording. 0:19 1:19
  • The question driving the talk is where to use a prompt and where to build software. His examples first expand what users ask for, then reconsider what developers should build to support those requests. 0:19 13:49

How to read the examples

  • The talk starts from Theo's conversations with other engineers and his own early experiments. Treat the broad claims as his position, supported by the specific demonstrations and personal experiences in later notes. 0:51