"What can be said of this? If, in order to 'really' enter a programming culture, I need to both 'be solving a significant real problem in the real world' and exercising 'the freedom to change the language, the compiler, the OS or even the hardware design', then there are very few options for entering this culture indeed. The requirement for 'real world work' is almost by definition incompatible with 'the freedom to change the language, the compiler, the OS and the hardware design'."
Of course lacking such a facility I just end up scattering extra locals even though I end up feeling like the output is rather archaic. a = ...; b = ...; c = f(a,b);
The real problem is that it's hard to distinguish "best" practices from conventional practices. Innovators are necessarily unconventional, but the ones we care about are also necessarily demonstrably good (in some sense). So there is this claim from the innovator side that "unconventional" is not a valid argument.
This claim only makes sense in the presence of an "unconventional" judgment -- i.e. that this creative work is necessarily deficient simply because it is unconventional.
Now, of course, no critic would put it so bluntly. But I think it illustrates the underlying dynamic.
That is a conditional statement, not a biconditional. Which is why for every single successful innovator, we can often find thousands of nutcases, inventing floating shoes, helmet mounted rifles, and Forth (just kidding, mostly). Therefore, an unconventional person should be especially careful that they do not find themselves on the wrong side of the thin line between genius and insanity.