Unfortunately there is absolutely no incentive structure in place anywhere to reward someone for writing code that lasts a decade or more without major maintenance. How would you do that? Send a check a decade later?
Even setting aside the impossibility of knowing whether the choices you're making will stand the test of time, how do you convince your boss, PM, director etc that it's worth spending extra time now rather than accepting some tech debt?
When I look back at the code I've written which has lasted the longest --- was not yet made obsolete by some product or technical redesign --- it is generally not the code that I was proudest of at the time I wrote it.
And to the original point, yeah, my CS degree is fairly useless at this point but it did prepare me for constantly wrapping my head around new abstract concepts I guess.
Even setting aside the impossibility of knowing whether the choices you're making will stand the test of time, how do you convince your boss, PM, director etc that it's worth spending extra time now rather than accepting some tech debt?
When I look back at the code I've written which has lasted the longest --- was not yet made obsolete by some product or technical redesign --- it is generally not the code that I was proudest of at the time I wrote it.
And to the original point, yeah, my CS degree is fairly useless at this point but it did prepare me for constantly wrapping my head around new abstract concepts I guess.