• As much as the content of this editorial is good, I am amazed, stunned and disappointed that there is not even ONE single mention of the most basic element of programming - commenting your code!!!

    In my 30 years of development and managing programmers I have driven plenty of them crazy when I have rejected code that is not commented. PROGRAM CODE IS A COMPANY ASSET - and thus commenting your code is as important as being able to understand a corporate financial statement because it is explained.

    Commenting code not only benefits any new developer being able to pickup and manage code, it also helps the very developer who creates the code. When you have been at this as long as I have, you are going to run into times when you are asked to go back to old code (sometimes even a decade old) and make changes - when you comment your code you capture thoughts of what you were doing and what your approach was.

    To pen an editorial about "readability" is nice - but it is NOT readability that truly matters - code comments do, and as I have said and will stress again - its a company asset, developers don't "own" code, the company does. Just as you might have some new appliance added to your house and then have it explained by the installer, code comments are simply essential and the FIRST element to any "readability".

    Its a shame that he author left this out of the editorial - thats like talking about a sandwich and never mentioning bread.

    There's no such thing as dumb questions, only poorly thought-out answers...