✳flâneur — a map of the web's best reading

Understanding about RFC 3339 for Datetime and Timezone Formatting in Software Engineering | by Iman Tumorang | Easyread

medium.easyread.co · 1,293 words · saved by 1 readers

A few days ago, when building the Mabar, we have a great debate about Datetime formatting. There’s an issue that our timezone is not consistent. So, later after a long fight and discussion, we come to an agreement to use a standard for our timezone. We finally decide to use the RFC 3339 as the standard for the date-time format. Means, both backend and frontend will use this format to communicate about the DateTime format. And also, we agreed to use UTC+0 as the default timezone, even when creating the event and receiving the event detail from the server. And let both frontend and backend convert it based on their timezone. So what is RFC 3339? RFC stands for Request For Comment. RFC is a formal document from the Internet Engineering Task Force (IETF) that is the result of committee drafting and subsequent review by interested parties¹ There are already so many RFC documents released by this committee. And become standard in every business. One of their documents is the RFC 3339, a docu

Understanding about RFC 3339 for Datetime and Timezone Formatting in Software Engineering Small and simple things that not every engineer knows, but very important things that every engineer should understand. Iman Tumorang 6 min read · Oct 14, 2019 -- 8 Listen Share Press enter or click to view image in full size Photo by Aron Visuals on Unsplash A few days ago, when building the Mabar , we have a great debate about Datetime formatting. There’s an issue that our timezone is not consistent. So, later after a long fight and discussion, we come to an agreement to use a standard for our timezone.

Explore this link on the map →

related reading