3 ms·
1.4 was released in 2002. If you haven't updated your code in over a DECADE, you are being incredibly lazy or incompetent.
by arkitaip 13y ago
1.4 was released in 2002. If you haven't updated your code in over a DECADE, you are being incredibly lazy or incompetent.
- lttlrck 13y agoOr you did a good job in 2002.
- icebraining 13y agoOutside the SaaS world, software often runs for much longer than the developer supported period - it's not rare for the software company to go bust way sooner than the software itself.
- nknighthb 13y agoIf the requirements haven't changed, why should the code?
- derleth 13y agoIf the requirements include "keeping time with up-to-date knowledge of time zones without costing us money", guess what, the requirements now mandate a code change. Requirements may not change, but environments do, and continuing to meet requirements in the face of changing environments is something that will often mandate changing code or requirements. When the world shifts, something often has to shift along with it, lest the whole thing break.
- nknighthb 13y agoTime zones are not code, they are data in a defined format that the code is already equipped to handle. Updated time zone data is not a reason to change code.