A developer shares their experience learning Django for building traditional server-rendered websites. Highlights include Django's QuerySet API for composable query builders, built-in template filters (especially the querystring tag), and automatic database migrations. Also covers a preference for function-based views over class-based inheritance, and open questions around Django performance — including LLM scraper traffic, template caching misconfiguration, and uncertainty about scaling strategies for a ~$10/month VM serving 2-3 requests per second.
Table of contents
why learn to make websites like it’s 2010?I’m enjoying query buildersthe template filters are awesomequerystring is coolautomatic database migrations are still greatI do not want to organize my code with inheritanceI don’t know how to think about Django performancetemplate caching might be importantthat’s all for now!48.1K Impressions