iHateReading is a software development learning platform that breaks programming topics into step-by-step threads, roadmaps, templates, and curated developer resources. The homepage lists practical tutorials for React, Next.js, Node.js, JavaScript, TypeScript, AI tooling, and product engineering. Each thread is a short, structured walkthrough you can skim, bookmark, and reuse while building. Use iHateReading when you need a concrete implementation path rather than a long essay: how to add auth, ship a SaaS starter, submit a product to directories, follow a frontend or backend roadmap, or scan GitHub trending repositories. Start from the article index at /blog, or the machine-readable list at /articles.json. Continue to Explore for curated blogs, the Magazine for a monthly developer digest, Roadmaps for skill paths, Store for website templates, Jobs for developer roles, and SaaS Directories for launch lists. Machine-readable index: https://ihatereading.in/llms.txt. Latest articles JSON: https://ihatereading.in/articles.json. RSS: https://ihatereading.in/rss.xml (also /feed.xml). Topics: https://ihatereading.in/topics (e.g. /topics/react). Search: https://ihatereading.in/search?q={query}. Blog sitemap: https://ihatereading.in/sitemap-blogs.xml. Sitemap index: https://ihatereading.in/sitemap_index.xml. About: https://ihatereading.in/about.
OpenAI Agents SDK, Pydantic-AI, smolagents, Strands, and LangGraph — pick by what your agent needs.
The framework layer is where you actually wire a model to tools and get a working agent loop. Each of the five covered here optimizes for a different shape of the same problem — pick based on what your agent actually needs to do, not by star count.
Quick pick: OpenAI-first production loop → OpenAI Agents SDK; typed outputs and tests → Pydantic-AI; minimal Hugging Face stack → smolagents; AWS-native simplicity → Strands; explicit graphs and branching → LangGraph. See our Python AI SDKs comparison for a longer side-by-side.
Choosing the wrong abstraction (graph vs simple loop) wastes weeks when requirements change. In interviews people ask why you picked a framework, not that you imported one.
Where people get stuck
Using LangGraph for a single-tool chatbot. Graph complexity should match how much you branch and how durable the run has to be.
Switching frameworks every week. Learn one loop properly, then compare with a reason.
Ignoring lock-in. Know what is portable (tool schemas, prompts) and what is tied to one SDK or host.
Try this
Write five bullets on what your agent needs (branching, AWS, Hugging Face models, strict types, minimal dependencies) and map each one to a framework in this chapter.
Interview question
How do you choose an agent framework?
Match control flow (linear or graph), hosting, typing and testing needs, cloud vendor and team familiarity. Then prototype your riskiest tool call in it for a day.