You have quite overlap between some stuff. I would recommend "Clean Code", but then skip the rest from the same author, at least for a while. While "Code Complete" is good, it's loooong and also a lot of the same stuff.
For patterns, "Head First" is a bit childish maybe, but the content is fine for someone learning to recognize patterns. "Patterns of Enterprise..." is also good, but more dry. I'd stick with one of those two. And then skip the one by GoF, unless you want to read the "original" for some reason.
"The Pragmatic Programmer" is probably the book that has shaped my work the most.
Another "Patterns" book that seems to be interesting is "Pattern-Oriented Software Architecture For Dummies" by Robert Hanmer. I've actually ordered it and look forward to read it in the coming year.
There's also "Patterns for Fault Tolerant Software" by the same author that looks pretty interesting too.
Code Complete seemed to be a book with a lot of dense, redundant content. Reading what was written had me feeling like I was reading information that could have been written by myself. Clean Code on the other hand (along with Refactoring by Martin Fowler) changed the way I write code for the better.
Not a long time ago I've found this comment about how to read Code Complete: https://www.amazon.com/gp/customer-reviews/R65Q50S27SSWE - After reading the comment, maybe I'll consider to give the book another try with a different approach :)
For patterns, "Head First" is a bit childish maybe, but the content is fine for someone learning to recognize patterns. "Patterns of Enterprise..." is also good, but more dry. I'd stick with one of those two. And then skip the one by GoF, unless you want to read the "original" for some reason.
"The Pragmatic Programmer" is probably the book that has shaped my work the most.