what django feels like after react

#webdev #backend #django #react

after spending the last 10 months in the frontend world, javascript started feeling like home. react made sense, its ecosystem made sense, and i got comfortable there.

but i wanted to go full stack. so i spent nearly a month just… deciding. which backend, which language, which path. longer than i’d like to admit.

i ended up picking django. which was surprising even to me, because i had zero python background. it meant leaving behind everything familiar and starting from scratch. new language, new mental model, new way of thinking about web apps. still felt like the right call though.

so i learned python. then jumped into django.

i’ve been going through views, urls, and templates lately. posting about it a bit late, but that’s genuinely where i am right now.

to actually understand how things connect, i built a small project. calling it an “app” is generous. it was mostly just me poking around trying to make things work. but it helped.

one thing that actually surprised me was django’s url routing. the moment i saw it, it reminded me of react router. same core idea, different syntax. that one familiar thing made the whole thing feel less foreign.

honestly, i’ve enjoyed django more than i expected to. there’s some setup at the start that feels like a lot, but once you’re past it, the framework just gives you things. you’re not stitching packages together to get basics working.

i’m still a beginner. there’s definitely harder stuff ahead. but after months in react-land, django has been a genuinely refreshing shift. seeing a completely different philosophy for building web apps changes how you think a little.