Like in this example, these books I have mentioned are not even a matter of opinion, they are such masterpieces, without which no list could be considered worth having.
You probably pissing up the wrong tree.
In software engineering there are other aesthetics. The famous maxim "for people to read and accidentally for machine to execute" sums up almost everything. Clarify, conciseness, readability, modularity, compossibility, loose coupling, design around protocols and interfaces - every decent programming guidelines, such as Google's Common LISP or Python style guides will show you a set of variables to optimize. Norvig's LISP style guide is also nice read.
Like it is in arts, each genre has its own aesthetics, and there are universal ones, such as non verbosity, clarify, following standard, familiar idioms. So, some artifacts are objectively better (according to certain human-universal aesthetics or those derived from laws of complex systems of Nature) than others no matter what conditioning you have in your head. Haskell's syntax, for example, is aesthetically better than Java's no matter what opinion you, or even majority hold.
Do you have sheriff's bage or something?
If you'd like to list your favorite books, you should do so (somewhere else, though, since it would be off-topic here). But scorning someone else for not sharing your taste violates the spirit of this site, not to mention was guaranteed to lead the thread further into off-topic bickering.