Some notes on starting to use Django
1–10 of 145 posts
Re: Some notes on starting to use Django
#2Claude Code is also very good at building basic CRUD apps with Django.
Re: Some notes on starting to use Django
#3Thanks for this! I wish there were more cross-comparisons like this out there of what it is actually like to use some of these frameworks, the note on Django being a little less magic than Rails makes me genuinely interested in it.
Re: Some notes on starting to use Django
#4I always return to Django for any project. It's fantastic. Enough batteries are included with it that it is very powerful.
Re: Some notes on starting to use Django
#5Django is objectively the most productive "boring technology" I've ever worked with for developing web applications. They don't regularly add too many bells and whistles on every release, but they keep it stable and reasonably backwards compatible.
Re: Some notes on starting to use Django
#6Django aside, I think this is a really important point:
Being able to abandon a project for months or years and then come back
to it is really important to me (that’s how all my projects work!) ...
I, too, have found found that my interactions with past versions of myself across decades has been a nice way to learn good habits that also benefit me professionally.
Re: Some notes on starting to use Django
#7After spending a lot of my time on Django, it's fine for simple to moderately complex things. The ORM mostly good. DRF is fine for APIs. And the admin is super nice as well.
But once something gets significantly complex, the ORM starts to fall down, and DRF becomes more of a hindrance.
But if you're just doing simple CRUD apps, Django is perfectly serviceable.
Re: Some notes on starting to use Django
#8> I love being able to backup by just doing a VACUUM INTO and then copying the resulting single file.
Naively, I would probably just copy the sqlite file. Is that a bad idea?
Re: Some notes on starting to use Django
#9> I love being able to backup by just doing a VACUUM INTO and then copying the resulting single file. Naively, I would probably just copy the sqlite file. Is that a bad idea?
I learned about the VACUUM INTO command through the following guide on how to backup your sqlite database: https://litestream.io/alternatives/cron/
Re: Some notes on starting to use Django
#10The Django ORM / migrations are still basically unmatched in happiness factor.