3 ms·
A lot of the people who complain about the bad code of legacy systems don't understand that their code has a good chance to be legacy in 20 years. Makes me wond
by rqtwteye 4y ago
A lot of the people who complain about the bad code of legacy systems don't understand that their code has a good chance to be legacy in 20 years. Makes me wonder how well the "microservice/k8s/many third party packages" apps will age. I suspect not well.
I am always shocked when I learn the some code I wrote as throwaway-tp-be-done-right-later 10 years ago is still in use.
- orangeoxidation 4y ago> I am always shocked when I learn the some code I wrote as throwaway-tp-be-done-right-later 10 years ago is still in use. That's because your "quick throwaway" code solves a real problem. It is useful, it works, it is very likely easy to understand. In short: It's good code. (It might not be "elegant" or "clever" or even "neat". Those things are overrated.)
- MathMonkeyMan 4y agoI hadn't thought of it this way. Good perspective. I'll inject some cynicism, though: > It is useful, it works, it is very likely easy to understand. It probably mostly solves the intended problem, and might be so close to coming apart that nobody dares improve it.
- MagicMoonlight 4y agoAll those stupid front end libraries will be the new mainframe. >Guys I’ve been stuck with this application that says its a web app doesn’t render in the browser engine. It has its own version of a browser engine that’s from thirty years ago and it needs 200 dependencies from a repository that doesn’t exist anymore. How am I supposed to maintain this?