3 ms·
I am 67, but this story occurred when I was young and just out of college: there was a very old computer programmer at work who had great skill but he miss-appl
by mark_l_watson 8y ago
I am 67, but this story occurred when I was young and just out of college: there was a very old computer programmer at work who had great skill but he miss-applied it. The worse thing he did was writing tortured FORTRAN code that self modified itself at runtime - hardware architecture and operating system dependent binary patches. I promised myself I would never be that guy, read the book ‘The Egoless Programmer’ and followed a different career path from my old friend.
- diego_moita 8y agoYou touched a different but very important issue: in this industry you need to recycle yourself, you need to stay up to date with new technologies that overcome the old ones. Being old doesn't necessarily means being obsolete, but you need to deliberately avoid obsolescence. Sometimes the new shiny things are actually good. Some technologies fade and you should avoid fading with them. Assembly programming has become a niche for people that write compilers. FORTRAN is giving space to R and Python. Very few people still write COBOL.