"You don't just make up a number and add it onto your balance sheet."
Now that's denial. I thought Enron, Worldcomm, AIG, Freddie and Fannie, Lehman, Merryl, Wachovia, and all those companies did that. Moreover every company which restated their earnings did it as well - that's all most all of the listed companies out there. So it's a rule, not an exception to make up numbers. The only point of contention is how to makeup the number.
I never understood how DST saved anything anyhow. However, I do know that it causes a lot of intricate bugs, especially when programs contain time based loops. In most of the SDKs and Frameworks the default DateTime.Now returns the local time. A lot of software applications fail during DST switching because of loops in the code that compares two different times returns wild and unexpected results. I even had to mandate using DateTime.UtcNow in the code all the time.
Slashdot Mirror
Hilarious! You should try standup...You are the Nerd Up today!
"You don't just make up a number and add it onto your balance sheet." Now that's denial. I thought Enron, Worldcomm, AIG, Freddie and Fannie, Lehman, Merryl, Wachovia, and all those companies did that. Moreover every company which restated their earnings did it as well - that's all most all of the listed companies out there. So it's a rule, not an exception to make up numbers. The only point of contention is how to makeup the number.
I never understood how DST saved anything anyhow. However, I do know that it causes a lot of intricate bugs, especially when programs contain time based loops. In most of the SDKs and Frameworks the default DateTime.Now returns the local time. A lot of software applications fail during DST switching because of loops in the code that compares two different times returns wild and unexpected results. I even had to mandate using DateTime.UtcNow in the code all the time.