I’m senior developer on a feature bloated civil engineering web app that has 2 back end servers (one just proxies to the other) and has 8k lines of stored procedures as the data layer and many multi k line react components that intentionally break react best practices.

I loathe working on it but don’t have the time to refactor legacy code.

———————-

I have another project that I am principal engineer and it uses Django, nextjs, docker compose for dev and ansible to deploy and it’s a dream to build in and push features to prod. Maybe I’m more invested so it’s more interesting to me but also not waiting 10 seconds to register and hot reload a react change is much more enjoyable.

▲

rick1290 6 days ago | parent [-]

whats your setup for the frontend? do you autogen your queries from DRF? do you prefer react headless over django templates?

	▲	bodhi_mind 6 days ago \| parent [-]
		If it’s something simple, I’ll use Django template because it’s very easy. Most stuff I work on these days requires more fancy ui so I’ll 100% use react or nextjs for front end (and I’ve be using zustand for state management). I’ll have an api util that uses axios and handles appending a jwt auth header to all requests and use that in my components. I like using Django-all-auth because it makes integrating email/google/microsoft auth really easy out of the box. DRF is good, ninja is a little more light weight and flexible so it really comes down to the project.