Why does code rot? Wikipedia lists a bunch of reasons — some make sense to me, some leave me meh.
From the vantage point of my battered years of experience, I’ve come to classify code into three areas:
If you are a professional software developer, or aspire to be one, you will need to know a lot of of things. Various maths, stats, languages, frameworks, methodologies, tools, etc. Fads and buzzwords will come and go, all during your career. You’ll master some, ignore some, laugh at some.
But aside from the desire and ability to work in abstracts for concrete results, there is one skill that is an absolute must-have.
My last post stirred up a lot of interesting feedback; some folks thought calling yourself a Software Artisan was pretentious (which is true, used in general conversation), some people thought it was a reasonable term, and some thought of other even more pretentious terms (My favorite: Software Auteur. It would be an amusing world where you could break the ice telling someone you were a Software Auteur.)
And some folks denied that software is handmade at all.