Have you heard about concept of code rigidity, fragility, immobility and viscosity?
You may have a piece of code that works now. But if it is rigid changing anything will be hell and require touching almost every part of the code. This of course will eat up time.
If it works but it is fragile, changing something in one place may break something else in very different place.
If your code works but is immobile, you will have to rewrite it if there is similar need in another system, but your code is not easy to reuse.
If your code works but has high viscosity future changes will be most likely done as the ugly hacks which won't help with any of the features listed above.
(I've omitted three more characteristics, because they are more of the result going overboard trying to avoid these four).
So to answer who cares about good code: anyone who will have to deal with it later.
I have worked on code that was working, fragile, rigid, and viscous, all at the same time. Clearly someone didn't respect those principles yet still produced code that works.
You may have a piece of code that works now. But if it is rigid changing anything will be hell and require touching almost every part of the code. This of course will eat up time.
If it works but it is fragile, changing something in one place may break something else in very different place.
If your code works but is immobile, you will have to rewrite it if there is similar need in another system, but your code is not easy to reuse.
If your code works but has high viscosity future changes will be most likely done as the ugly hacks which won't help with any of the features listed above.
(I've omitted three more characteristics, because they are more of the result going overboard trying to avoid these four).
So to answer who cares about good code: anyone who will have to deal with it later.