{"id":24840,"date":"2019-04-02T15:21:36","date_gmt":"2019-04-02T19:21:36","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=24840"},"modified":"2019-08-05T16:47:22","modified_gmt":"2019-08-05T20:47:22","slug":"falsehoods-about-time-and-csvs","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/04\/02\/falsehoods-about-time-and-csvs\/","title":{"rendered":"Falsehoods About Time and CSVs"},"content":{"rendered":"

Zach Holman<\/a>:<\/p>\n

\n

I’ve made notes of the egregious things I’ve learned about programming with time and pulled them together as a talk. This is the written companion piece, which is sort of a super set of the talk, since I had way more notes than what I could shove in a single talk.<\/p>\n

Beyond that, though, there’s also a lot about time itself that is properly hilarious, and it’d be a travesty to not talk about the country that recently decided to skip a certain day, or that the Unix epoch isn’t technically the number of seconds since January 1970, or that February 30 happened at least twice in history.<\/p>\n<\/blockquote>\n\n

Jesse Donat<\/a> (Hacker News<\/a>):<\/p>\n

Much of my professional work for the last 10+ years has revolved around handling, importing and exporting CSV files. CSV files are frustratingly misunderstood, abused, and most of all underspecified. While RFC4180<\/a> exists, it is far from definitive and goes largely ignored.<\/p>\n

Partially as a companion piece to my recent post about how CSV is an encoding nightmare<\/a>, and partially an expression of frustration, I've decided to make a list of falsehoods programmers believe about CSVs. I recommend my previous post for a more in-depth coverage on the pains of CSVs encodings and how the default tooling (Excel) will ruin your day.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n