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.
AWS's open-source agent framework, already running inside Amazon Q Developer and AWS Glue internally. The leanest of the four by a real margin.
Core concepts
The agent is callable: agent("...") both sends the message and runs the tool-calling loop — no separate Runner or .run() call needed. Strands Docs
@tool decorator: Same lightweight registration pattern as the other frameworks, minimal ceremony.
Bedrock-first, provider-neutral otherwise: Defaults to Amazon Bedrock with zero configuration; OpenAI, Anthropic direct, Ollama, LiteLLM, and Gemini are all supported.
Native MCP support: Thousands of pre-built tools available through MCP servers with no custom integration code.
AgentCore: A companion runtime for deploying Strands agents — positions the framework as the agent-building half of a two-piece AWS-native stack.
Why it matters
If you're on AWS with Bedrock and IAM, Strands cuts the glue code. Off AWS, another framework is usually simpler.
Where people get stuck
Broad IAM roles on tool permissions. An agent uses whatever you give it, so grant the minimum.
Assuming Strands replaces tracing and evals. It doesn't.
Choosing it with no AWS footprint.
Try this
Sketch an agent that calls one Bedrock model and one MCP tool, then list the IAM permission each call needs.
Interview question
When is Strands a good fit?
When you deploy on AWS, use Bedrock models, want MCP-compatible tools and prefer an AWS-supported SDK over your own boto3 loop.