by John Galt » Fri Oct 03, 2014 11:57 am
well the issue is third part application with legacy code (which i totally believe is the real cause, because it can be a headache), which in turn was a direct result of microsoft's terrible naming scheme of jumping from numbers to years to arbitrary concepts back to the same numbers, forgetting that years are also numbers...
in a sci fi book in the distant future, there are professional "archaeologists" who study old programming and then fix ancient (centuries old) code. these specialists will exist sooner than later
Americans learn only from catastrophe and not from experience. -- Theodore Roosevelt
My life has become a single, ongoing revelation that I haven’t been cynical enough.