Address issues with Confusing Dates section

This section was by far the weakest since it focused too heavily on
issues with the U.S.-based date formats and not enough on justifying
the recommendation.

Addresses #191 #178
This commit is contained in:
Olivier Lacan 2017-07-18 12:54:17 +02:00
parent 0c53c7de4d
commit c81765b3ea

View File

@ -167,13 +167,16 @@ version: 1.0.0
Confusing Dates Confusing Dates
%p %p
In the U.S., people put the month first (<code>06-02-2012</code> for Regional date formats vary throughout the world and it's often
June 2nd, 2012), while many people in the rest of the world write a difficult to find a human-friendly date format that feels intuitive
robotic-looking <code>2 June 2012</code>, yet pronounce it to everyone. The advantage of dates formatted like
differently. <code>2012-06-02</code> works logically from largest to <code>2017-07-17</code> is that they follow the order of largest to
smallest, doesn't overlap in ambiguous ways with other date formats, smallest units: year, month, and day. This format also doesn't
and is an #{link_to "ISO standard", iso}. Thus, it is the overlap in ambiguous ways with other date formats, unlike some
recommended date format for changelogs. regional formats that switch the position of month and day numbers.
These reasons, and the fact this date format is an
#{link_to "ISO standard", iso} are why it is the recommended date
format for changelog entries.
%aside %aside
Theres more. Help me collect these antipatterns by Theres more. Help me collect these antipatterns by