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.)
> 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.
>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?