I picked up the SQL Cookbook 2nd edition for SQL, and it has helped me with one query since I got it a week ago. I think it is good, but have no real reference since I only have used the one book.
I should probably go to the library more often.
@pascal.fragnoud do you have a recommendation?
Did you write a book on Python yet haha?
I was leaning toward :
Python Pocket Reference: Python In Your Pocket (Pocket Reference (O'Reilly)) Fifth Edition
I don't know the best choice.
I went with this after about 2hrs research.
Thanks for helping me Alec and Pascal.
I am going with The Pragmatic Programmer 20th anniversary
I saw Raymond Hettinger mention it in a PyBay 2017 video
Effective Python: 59 Specific Ways to Write Better Python
The book says Raymond Hettinger contributed
Pascal, Raymond, and the previews were my main factors.
I thought the table of contents/organization were telling.
What I think was the biggest leap for me was learning about code smells, what they are, how to avoid and perhaps most importantly WHY they are code smells. This will really help keep your code clean (ie not smelly).
Know when you're doing something wrong and the right way to do it has helped me the most. There's one youtuber I like, ArjanCodes, who has a couple video on Python Code smells that are good. He also has "Code Roasts" where he goes over what looks like decent enough production python code, and then explains the code smells in that and how to improve it. Learning what is bad about code and how to improve, and WHY it is an improvement, I feel is probably one of the biggest things you can do for yourself. He does all his work in python 3 but many of the things are applicable to 2.5/2.7.
I think code smell originated from the book "Clean Code" but I am not sure, however now it is a common term now for code that is showing some common design flaw. Not production breaking flaw necessarily but a flaw that could become a bigger issue down the line if you try to develop on top of it. Not all code smells are equal.
You got that right.
As Phil said, underscore is a legal name for a variable in python, so you can use it just like any other valid name.
But, being an underscore, it's often used to say "I'm using a variable here but I'm not gonna use it".
Another example (that's python3 though, don't try this with 2.7):
Imagine you want the first and last elements from a list.
You could use
a, *b, c = [1, 2, 3, 4, 5]
# a == 1
# b == [2, 3, 4]
# c == 5
But to show that you only care about the first and last element, you could use an underscore:
Languages are not much different from each other, (data structures, conditional statements, repetition loops etc), but I am yet to see a good explanation of JYTHON/JAVA integration. How does it work under the hood! I understood it more from some blogs by enthusiasts but couldn't find a proper explanation in any of the books available freely on internet. How they thought of such an amazing concept! This is the key differentiator and the most interesting and practical aspect of Jython in my opinion. It is not a very obvious concept!
If someone can give me a good reference explaining how JYTON/JAVA integration works under the hood, I would be grateful.
You should start with Jython's own site. The Documentation links, in particular. If you really want to know how stuff works, I recommend studying the source code. A strong background in Java is helpful.