It would've been nice to see why a particular book was included in the list. I certainly don't agree with the addition of Clean Code, but I may be missing something, hence my wish.
I read it two years ago. I personally believe it's amazing as an example of what 150% of a good thing looks like, and the point is deciding what 1/3rd to cut to make a neat 10/10.
Without that book, you barely see what 50% of programming goodness looks like. The only way to 100% is to go too far and dial it back. Offering 150%, imo, is a humble way to offer a path forward without getting the reader all the way there. Maybe it's better that way.
*Most influential books for programmers
These are books considered most influential for programmers from this StackOverflow thread.*
That was point farming question on SO and people were voting on what was most influential for them.
Title might be tricky to read. Because title is saying that those books are not influential on the scientific field but are about that field. Problem is that there are books that are not about that topic so it adds to the confusion.
Books are about "computer science" topic and those books are meant to be influential in general.
It is by popular vote of how influential those books are on practitioners of software development.
