| 1 | [Transition] So when should you reach for these more complex patterns? |
| 2 | |
| 3 | The answer starts on the left: most of the time, you should start with single LLM calls optimized with retrieval and in-context examples. This covers the vast majority of applications. |
| 4 | |
| 5 | When you do need more, workflows give you predictability for well-defined tasks, while agents shine when flexibility and model-driven decisions are needed at scale. |
| 6 | |
| 7 | [Interactive] Think about your current project — where does it fall on this complexity spectrum? |
| 8 | |
| 9 | And a crucial piece of advice about frameworks: start with raw LLM APIs. Many patterns need just a few lines of code. If you do use a framework, make sure you understand what's happening underneath. |
| 10 | |
| 11 | Key points: ① Start simple — single LLM calls first ② Workflows for defined tasks, agents for flexibility ③ Understand your frameworks |
| 12 | Duration: 2 minutes |