What problem did you face when you started writing Django projects?

Question

Django

I know from my own experience that theory/documentation is about 20% of what a developer needs to know. The rest of the knowledge comes with practice. This especially happens when you solve a problem that is not in the official documentation or when your tool stumbles over internal limitations when solving a particular problem.
So, I want to collect some top-priority list of "rake", about which there is not a word in the documentation and which you have encountered in your practice. Or maybe someone even knows about the existence of such a ready-made list.
For example, I once studied symfony and came across the fact that the standard form rendering function is too complicated and it was easier to write my own parser / mapper of form fields and object (well, then I generally scored on this framework, because I realized that it too "ethereal" some)

Answer 1

1) Documentation was 70% for function-like coding style, not through classes. (But now, like already caught up). But I must admit the dock is very cool.
2) It suddenly turned out that there is no normal way to generate a PDF document from an HTML page (For php / java / .net there are some that do it in one click, but on django it was suggested to manually figure out the canvas).
3) There are two options for deploying django, and everywhere they argue which one is better with all sorts of benches and so on. As a result, it turned out that there was no difference at all (the difference was negligible). I checked with the guys from mail.ru at their conference.
4) Sometimes there are too many different libs to solve a problem. But most of them are either miserable, fragmentary and secondary. It is quite difficult to choose the most promising option.
5) Python + django => bourgeois stack (in our case, php occupies its niche in most cases), so get ready for the fact that all Russian-language vids will be with a Ukrainian accent, and some vids on Django Rest Framework and so on will be exclusively in English .
6) The Django admin panel is very cool for some simple crud and single-linked models, but something more complicated cannot be done, and you need to write your own admin panel.

Answer 2

1. Not knowing python as a language - it's very difficult to find out what I need in this or that situation.
2.

I know from my own experience that theory/documentation is about 20% of what a developer needs to know.

Documentation is 70 percent because everything comes from it, everything repels from it. Practice cannot completely replace documentation. And the remaining 30 percent is knowledge of python.
3. Few "Russian" videos about django and an explanation about it. I don’t rummage in English, yes, there are such, and when I watched a video like “a year” ago, there was one, but django quickly changed and became irrelevant.
4. It seems like all the problems described in the Django doc. With which middles in python I didn’t communicate, everyone told me that they say look for the answer in the docs.