| ▲ | boredtofears a day ago | ||||||||||||||||
There's no guarantee your code will be rewritten or refactored. I have code written over 15 years ago that I know is still in production because it is stable and core to the application. I suppose one day it probably will be replaced but I'm pretty satisfied with that piece of work and found it to be, if anything, more life affirming than draining. You can have your cake and eat it, too: if your work is satisfying and seeing people use the things you built gives you joy, you can make good money doing something you life without optimizing your entire life solely around ladder climbing or bigger paychecks. | |||||||||||||||||
| ▲ | mjr00 a day ago | parent [-] | ||||||||||||||||
yeah, if anything it's dangerous to assume that your code will get thrown away soon-ish. as an extreme example I'm aware of, the core AWS infrastructure is still heavily dependent on Perl scripts mashed together 15+ years ago. | |||||||||||||||||
| |||||||||||||||||