Pick a boring framework (Astro, Django, FastAPI)
The AI writes most of your code, so pick what it knows deeply: Astro for mostly-pages products, Django or FastAPI for app-heavy ones. Boring, documented, massively used - never exotic.
Boring beats trendy
When the AI writes most of your code, the framework question changes. You are not asking “what is nicest to write by hand” - you are asking “what does the AI write correctly, and what can I judge?”. Both point the same way: boring, massively-used, well-documented frameworks.
Three reasons:
- Training data depth. The AI has seen millions of Django and React codebases and far fewer of last year’s hot framework. More examples = fewer hallucinated APIs, fewer subtle bugs.
- You cannot judge exotic code yet. When the AI does something weird in a mainstream framework, Stack Overflow, the docs and the AI tutor can all tell you. In a niche framework you are alone with the bug.
- Boring frameworks change slowly. The AI’s knowledge has a cutoff. A framework that reinvents its API every six months guarantees the AI writes deprecated code.
Decide by product shape
Do not pick a framework in the abstract - pick it for the product you are about to build.
| Your product is mostly… | Use | On which stack |
|---|---|---|
| Pages and content (landing, blog, docs, comparison site) | Astro, with React islands for the interactive bits | A or B |
| An app behind a login (dashboards, CRUD, forms) | Django (batteries included: auth, admin, ORM) | A (VPS) |
| An API serving a separate frontend or mobile app | FastAPI (Python) or Express (Node) | A (VPS) |
| A tiny API on serverless | Hono (made for Workers) | B (Cloudflare) |
Astro is the default for the solo builder because most first products are content-shaped: pages that need to load fast and rank on Google, with a few interactive components. Astro renders plain HTML, lets you drop in React only where needed, and works on both stacks. This site runs on it.
Django is the default when your product is an app: users, permissions, forms, an admin panel. It is 20 years old, which is exactly the point - the AI knows every corner of it.
What about Next.js?
Next.js is fine and the AI knows it well. But for a first product it brings complexity you do not need yet (app router, server components, caching semantics that change between versions). If your product is content-shaped, Astro gives you the same React where it counts, with less machinery. Choose Next.js when you already know you are building a large interactive app.
The rules, whatever you pick
- One framework. No microservices, no separate “frontend repo + backend repo”. One codebase the AI can see whole.
- Server-rendered HTML over a SPA. Faster, better for SEO, and simpler mental model for you and the AI.
- No exotic build tooling. If the AI suggests a monorepo tool, a custom bundler config or a new meta-framework, say no. Every layer of tooling is a layer you will debug someday.
- Stay on the framework’s happy path. The AI is excellent at idiomatic code and mediocre at clever workarounds.
Verdict
Astro + React islands unless your product is clearly an app - then Django on a VPS. Both are boring on purpose. You can learn to read the code the AI writes in them with the React and web stack courses, and the framework will still look the same next year.
Next: set up where you develop, or if you have not yet, decide where your product runs.
New models & deals, once a month
New proprietary and open-source models worth trying, price drops, and the best deals on AI coding plans. No spam.