When AI Calls You: The Library vs Framework Shift

A Small Moment That Stuck Last week I was working on a side project. I had an AI agent running in the background, managing tasks, writing code, filing PRs. At some point I realized I'd been sitting there for twenty minutes, just... waiting. Waiting for it to finish so I could review the output and approve the next step. I wasn't driving anymore. I was being called on. That moment stuck with me. Because there's a pattern in software engineering that describes exactly what happened, and it maps onto something much bigger than my Tuesday afternoon. Libraries and Frameworks If you've written code, you know the difference between a library and a framework. With a library, you're in charge. You call sort() when you need to sort something. You call fetch() when you need data. The library sits there, waiting for you. You decide when, where, and how to use it. A framework flips this. You write small pieces of logic, and the framework decides when to run them. You define a route handler, and Exp