Do I need a Python reference guide?

Question

Django

Good afternoon. Do you keep Python references (electronic, printed) handy? Or programming in general? Is it worth buying, spending? And if so, is it a reasonable choice of Drones, Prokhorenok. Python 3. Or this one in particular?
In general, I wonder who reads what literature when questions arise? I think the respected toaster is not worth mentioning ;-)

Answer 1

Yes and no. Everything depends on the goal. I'll try to explain.
I have already mentioned the fact that people perceive information differently. My priority is books (rather than audio/video, for example). My approach to learning is step-by-step, from simple to complex, one technology in favor. But this sequence is not linear - at a certain stage it becomes cyclic, or, more precisely, spiral: in the material you have passed, as it seems to you, you begin to notice new moments that were previously overlooked.
Example:
I started with Dawson . Having worked thoroughly, he took up Lutz . After - Fluent Python, Python Cookbookand others like that... (HTML, Django, CSS, working on my own project - I omit everything as irrelevant details. We are talking only about Python and books.)
So, I didn’t return to Dawson anymore, to Lutz - sometimes I return, and " like them " I re-read in a circle and each time I discover something new for myself. This is most likely due to the fact that every time you return to the starting position with more advanced knowledge / understanding, the absence of which does not allow you to cover everything at once on the first try; plus, each author presents the same material from a different angle (with other examples), which further deepens your understanding of what has been covered.
And the material can be considered worked out, the work with which no longer gives you either new knowledge or a new understanding. But, as it always happens, by that time you will have other, relevant material in your hands - after all, the process of development, raising your professional level is actually bottomless.
I note that all of the above is based on the assumption that you are striving for maximum development within your technology. In my opinion, it is impossible to grasp the immensity and grab onto everything at once; step by step, as I said. There must be at least one strong base + accompaniment. But this baseshould be polished to a shine, like the bird-fruits of one of the infamous bronze figures located north of Bowling Green in New York's Financial District, two blocks south of the New York Stock Exchange.
For me, such a base, at present, is Python. I devote most of my time to him, distributing the rest to Other. But when I absolutely and completely exhaust Python, I will look for the next Priority Goal in its place. Etc. The process is, in fact, endless.
That's why you don't need a guide. It just doesn't make sense. You should always have up-to-date material at hand that will move you forward. In this sense, the reference book is a kind of crutch for the zen-wise, experienced Serpent, who is already too lazy to think, has nowhere to develop, but sometimes you need to quickly remind yourself of the times of violent youth, memories of which can be refreshed by opening the 135th page - first paragraph, second line :)
Well, if all of the above is not about you, Python just passed by, then maybe yes. Here is a very good option.
PS About literature in general, you can see HERE .

Answer 2

They were useful in the 90s.
But with the massive advent of the Internet, I see no reason for their existence.
As for the listed books, I would not buy them, but for other reasons.

Answer 3

Enough with the head
https://www.google.com.ua/search?q=django+whatever
If it does not find anything, then I read the code It is concise
and well documented

Answer 4

I read google. Books about "how to do X with Y" are not needed.

Answer 5

I have never seen a better official documentation on Python and Django ... Although I use reference books, including this book. But specific tasks are easier to search on github or stackoverflow.com