Python backend folder philosophy
In Python web backends, frameworks rarely enforce a folder layout, so it falls to team agreement. A well-organized layout shortens onboarding for new members; without it, the same patterns get scattered everywhere.
Posts tagged fastapi
AI/LLM topics — agents, prompts
HTML, CSS, JS, HTTP, URL basics
TypeScript, Java, Python, Rust
Data structures, Big-O, patterns
React, Next.js, Tauri, Tailwind
Spring, FastAPI, SQL
Claude Code · MCP · Context7 · Figma — overview of AI coding tools
Deployment options and decision criteria
PostgreSQL · Kafka · data strategy notes
Docker, Compose, Caddy, SSH
Windows vs Mac and other dev-environment notes
Cross-platform options compared (Tauri · Flutter · RN)
pnpm, uv, Gradle, Git, regex
KISS · DRY · YAGNI · naming — development philosophy
OAuth · JWT · security fundamentals
Testcontainers, Vitest, pytest
Searching, reading docs, debugging
In Python web backends, frameworks rarely enforce a folder layout, so it falls to team agreement. A well-organized layout shortens onboarding for new members; without it, the same patterns get scattered everywhere.
FastAPI moved into the Python web framework mainstream in a relatively short time. Behind that quick rise is a design that ties type hints, Pydantic, and async into a single coherent sentence.
There is a standard for expressing the shape of an HTTP API as a machine-readable document. That is the OpenAPI Specification (OAS). Once it is written well, doc pages, client SDKs, mocks, and contract tests all flow fr…