[naitbit]

In the beginning I too wanted to write that I don't agree with this split. Then I come to conclusion that he met far more programmers then I so he probably knows better.

Anyway I'm not sure were to put myself on this axis. My behavior changes depending on other variables(what consequences would bug have/how many times code is going to be executed etc).

FE: critical part of commercial software (like money calculation) would be written in a way that would try to make it obvious that there are no errors, in language with type checking with unit tests and if possible even with mathematical proof of correctness. With code review and QA thrown at it afterwards. To sum up very conservative(and costly) approach.

On the other hand my holiday photos got completely different treatment. Short python script, that would batch their HDR process in a way specific for their content and with a lot of dependencies to my current desktop setup, without any unit tests(script thrown up few temporary files making it easy for manual debug, had backup of my photos in case script ate them). The only conservative thing that I could think of in this setup was that I made it concurrent to use 4 cores because it was only one line change and 4time speed up in lengthy process was worth it.

Can someone suggest were on liberal-conservative axis am I?