> This comes off as very "well akchtually"; more snarky than helpful. Agreed. It would have been much more useful if the article was upfront about its intent,

> This comes off as very "well akchtually"; more snarky than helpful. Agreed. It would have been much more useful if the article was upfront about its intent, rather than stating it in the last paragraph along with categorizing the potential pitfalls in writing such code (e.g. time, international, cultural, historic, etc.). The categorizing is important since most, if not all, of the cases will be relevant in some circumstances and not in others. A day planner may need to consider international variation, you may need to consider leap seconds in log files, while historic and cultural variations is useful for some planetarium software.