Are you kidding? Compare to software: There is a lot of bad code in the word. This code was written by hacks, who in my experience, seem to have no idea why their code is bad -- to the point of justifying it beyond absurdity\
. Showing these people beautiful, well factored, well commented code frequently has no impact on them, they say "Oh, that is nice", but don't understand what makes it different than their hacky version.This is within the field. From the outside, this is even more dense and impenetrable, and probably looks almost masturbatory. Despite this, there is a fairly strong correlation of "good style" and "good software" so there is at least some objective measure there.
Of course, since there are hacks in the software world (arguably the majority of them, since very few HNers run in the circles of bank software engineer or .Net programmer, and those people are the majority of programmers), the discussions on what makes good software probably don't result in anything worth knowing, or barely anyway.
I am not commenting on your overall conclusion, I don't know if lit. crit. is a worthy pursuit, but your argument is definitely lacking a sound basis.
\ I worked with a guy who would copy and paste program, with many many repetitions of blocks. After of getting a barely working result, would seemingly decide "oh functions are important in programming" and randomly break the code into a few functions, which each took 10+ arguments to carry state over from chunk to chunk. Since these were essentially just chaining the calls, none of the functions would be called elsewhere, no repetition was avoided, and extra cognitive load was added to reading the results. When this was done, the original author could not understand how it was different, let alone better.