> "But maybe I'm wrong." I don't think you are wrong. Timing APIs are tricky and complicated. The small print really matters. Experienced engineers will know t

> "But maybe I'm wrong." I don't think you are wrong. Timing APIs are tricky and complicated. The small print really matters. Experienced engineers will know this, and so the answer in this instance, as annoying as it may be - absolutely RTFM. Also, funky documentation/APIs exist everywhere, unfortunately. Quoting the article: > "You're a new coder, and you find yourself tasked with taking a Unix time_t type value and turning it into some kind of human-readable format" I'd argue that's exactly the kind of mistakes inexperienced coders are prone to make. Hence we have code-reviews.