4 ms·
Now is a good time to think that the code you write today might live forever and in that context stop writing bad code for employers and instead write good code
by bullen 6y ago
Now is a good time to think that the code you write today might live forever and in that context stop writing bad code for employers and instead write good code for people.
Good code runs on both Windows on X86 and Linux on ARM.
Good code can hot-deploy. Good code is fast!
For me that means Java SE on the server and C+ (C syntax with string, stream and objects for project organization only) on the client.
HTML, CSS and JS is ok for GUIs only, everything else should be native with command line!
Please comment if you down vote.
- weego 6y agoGood code doesn't project intent into the future, it is written for now. Good code doesn't paint the future into a corner.
- jacobr1 6y agoProgramming for longevity is probably less about the specific language or tooling choices and more about things like: can you reproduce the build or does it presume a specific environment? How is the source code stored and how can it be recovered if the primary location is lost? Is the system well documented? Are the abstractions robust, and well composed? Many mainframe systems survived while desktop based systems have been killed because of the server/client architecture that has allowed for new front-ends to built separate from the backend. In this sense, if you are building for malleability, things like good test coverage become very important to support refactoring and changes. I'm sure many other considerations apply.
- bullen 6y agoSure, that's why github backed up everything in the Arctic now. But C and Java will remain longer than anything else, for good and for bad.