3 ms·

You are wrong. Just checked Django part. No annotations, `all` in serializers, exists+get instead just calling .first(), etc. It's no way a good Django code

You are wrong. Just checked Django part. No annotations, `__all__` in serializers, exists+get instead just calling .first(), etc. It's no way a good Django codebase.

whalesalad 3y ago
It might not be perfect, or live up to whatever expectations you personally possess, but it legitimately is a pretty good example of a clean and straightforward Django application.
_boffin_ 3y ago
What are your favorite repos that are built with Django that have good practices.
- rasulkireev 3y ago
  https://github.com/builtwithdjango/builtwithdjango https://github.com/builtwithdjango/builtwithdjango This is not the best practice codebase as I wrote it when I was learning Django. But is it very applied. Any beginner should be able to understand this.
  - _boffin_ 3y ago
    > Any beginner should be able to understand this Was thinking more along the lines of non-beginner stuff.
evantbyrne 3y ago
Also noticing copious use of select distinct within the views, which indicates issues with the schema. It may also partially be due to the somewhat limiting API provided by Django Rest Framework, which I personally tend to avoid. All things can be improved though.
- rokkitmensch 3y ago
  Why do you avoid DRF? It's what keeps me coming back to Django over .NET Core or other API stacks (although I have yet to tilt at RoR in earnest/anger).
  - evantbyrne 3y ago
    I just want to start by acknowledging the demo of basic functionality is fantastic and feels very magical, and–perhaps crucially–it has been a couple years since I gave up on DRF completely. With that out of the way, I've run into issues with it when building actual applications. DRF serializers were absurdly slow. Relations were handled poorly. It steers you away from many of Django's standard features, including the forms interface, which is one of Django's best features. The documentation was lacking for rough patches in the API.

You are wrong. Just checked Django part. No annotations, `__all__` in serializers, exists+get instead just calling .first(), etc. It's no way a good Django code

You are wrong. Just checked Django part. No annotations, `__all__` in serializers, exists+get instead just calling .first(), etc. It's no way a good Django codebase.

whalesalad 3y ago

It might not be perfect, or live up to whatever expectations you personally possess, but it legitimately is a pretty good example of a clean and straightforward Django application.

_boffin_ 3y ago

What are your favorite repos that are built with Django that have good practices.

rasulkireev 3y ago
https://github.com/builtwithdjango/builtwithdjango https://github.com/builtwithdjango/builtwithdjango This is not the best practice codebase as I wrote it when I was learning Django. But is it very applied. Any beginner should be able to understand this.
- _boffin_ 3y ago
  > Any beginner should be able to understand this Was thinking more along the lines of non-beginner stuff.

evantbyrne 3y ago

Also noticing copious use of select distinct within the views, which indicates issues with the schema. It may also partially be due to the somewhat limiting API provided by Django Rest Framework, which I personally tend to avoid. All things can be improved though.

rokkitmensch 3y ago
Why do you avoid DRF? It's what keeps me coming back to Django over .NET Core or other API stacks (although I have yet to tilt at RoR in earnest/anger).
- evantbyrne 3y ago
  I just want to start by acknowledging the demo of basic functionality is fantastic and feels very magical, and–perhaps crucially–it has been a couple years since I gave up on DRF completely. With that out of the way, I've run into issues with it when building actual applications. DRF serializers were absurdly slow. Relations were handled poorly. It steers you away from many of Django's standard features, including the forms interface, which is one of Django's best features. The documentation was lacking for rough patches in the API.