Live data from Hacker News

Django Newbie Mistakes

code.djangoproject.com

1–10 of 225 posts

Re: Django Newbie Mistakes

#3
Django’s documentation is still the best I have worked with so far of any software project I came across to date. It not only explains, it educates.

Re: Django Newbie Mistakes

#4
I doubt it's still the case but for a long time the default "Authorization" was effectively fail-open so a newbie mistake was to use that and then not customize it leaving your API vulnerable to any logged in user reading anything.

There was a bright red box effectively saying "Don't use this module without customizing it" in the documentation but that didn't stop newbies going live with it in place.

Re: Django Newbie Mistakes

#5
I absolutely love Django's documentation. As a desktop developer looking to get more into web stuff, Django has been super attractive as a backend to get my hands dirty with.

Re: Django Newbie Mistakes

#7
Django’s documentation is excellent, but parts of the wiki are out of date.

This page has barely been updated in the last four years. It mentions MIDDLEWARE_CLASSES (deprecated in Django 1.10) and using strings in url() (deprecated in Django 1.8). There may well be other bits which are out of date.

The entries in the faq [1] are more likely to be kept up to date.

[1]: https://docs.djangoproject.com/en/2.0/faq/

Re: Django Newbie Mistakes

#8
Django is a hell for APIs and big projects. It's good for beginners and small projects, but once you need the least amount of actual control, you will find it's too late

Re: Django Newbie Mistakes

#9
This is very useful for beginners.

I hope more frameworks/languages have a page of common "gotcha's" in their documentation in the future. Then again, it's sort of a right of passage to spend a couple of hours debugging common mistakes when you're learning something new: you'll definitely not repeat your mistake in the future that way :)

Re: Django Newbie Mistakes

#10
post #2

If you're writing a REST api, invest the time to learn Django Rest Framework. It is well worth it.

Agreed, but with the caveat that there are a lot of bad parts of DRF. It's probably the best tool to build a REST API, but only if you're using some minimal subset of the tools available.
Post reply on HN