You are right Erik that one should never create code like this for production use.

However, the ability to read and understand such code is a valuable asset.
in other words: because there are burglars detective skills is a valuable asset.

Statements like this is the very reason the Cidiots keep on pumping out their crap.

such code It is NOT 'code' it is CRAP!!!!

In all but the most insulated positions, you will eventually have to maintain code written by someone else, and who knows what code you will come across.

From my experience it's always much easier to write code than to read it. I've seen programmers who just "glaze over" when they need to look at some code, figure out what it does, and modify it. They will say: "I'll rewrite it", because they don't have the skill to "read code". Of course, the existing code probably does things a certain way because of issues found long ago (that might not be documented), so a "rewrite" often introduces more problems than it fixes.

When I 'inherit' crap the first thing I do is to convert it to code by analyzing and commenting it. In this process I run a constant compare of the binary generated by the tools to make sure I do not generate any errors or introduce any changes in the process. Just imagine how long it takes me to do this commenting compared to the time it would have taken the Cidiot that wrote the crap in the first place.

Yes 'crap' no other word can be used to describe uncommented crap DO NOT, in my presence, ever call such anything but CRAP, OK I'll accept 'scribbles'.

Erik