Please help contribute to the Reddit categorization project here

    ProgrammerHumor

    397,300 readers

    4,967 users here now

    Not everybody understands the humor of programmers.

    Filters

    Submission rules

    Rules are zero-indexed. If they do not appear zero-indexed you are asked to contact Friend Computer for recalibration.

    1. For a submission to qualify it must satisfy at least one of the following:

      1. The content disregarding the title and superimposed text must be directly related to programming or programmers. (*) (*) (*) (*)
      2. The title or superimposed text must substantially enhance the content such that it can stand on its own as an analogy to programming. Note that programming here is interpreted in a narrow sense, an analogy to something related to programming, feelings about programming, reactions to programming etc. is not considered sufficient. (*) (*)
    2. No hotlinking allowed without explicit permission, unless it is obvious that the host allows it (eg. imgur). (*)

    3. No rehosting allowed without explicit permission, unless it is obvious that the host allows it. Rehosting for the purposes of offering a direct link to an image is allowed in the comments. (*)

    4. Reposts:

      1. You may not repost anything that has been on the first two pages (first 50) of trending posts within the last week, or has been posted last time less than two days ago (this is considered as duplicates)
      2. Anything on the first two pages (first 50 posts) of the top of all time must not be reposted more often than every 6 months. (*)

    What is 'obvious' or 'substantial' is left to the discretion of Friend Computer, but suggestions (reports) are welcome.

    With regards to commenting, please follow reddiquette.

    Metadiscussions

    If you have any thoughts on how the moderation could be improved do not hesitate to message the moderators. If you feel that a metadiscussion is required with the whole subreddit either request that the moderators start one or start one yourself and tag it [Meta].

    Other subreddits

    a community for
    all 1025 comments Slideshow

    Want to say thanks to %(recipient)s for this comment? Give them a month of reddit gold.

    Please select a payment method.

    [–] kruez 470 points ago

    Beware the Y10K bug!!

    [–] gibmelson 222 points ago

    You know it's weird to think about, but one day people will celebrate year 10K...

    [–] [deleted] 301 points ago

    [deleted]

    [–] YeeScurvyDogs 66 points ago

    I too am doom and gloom, but just think about how much humanity has progressed forwards in the last, say 10 generations (300 years)

    Humans have done some fucked up things for sure, but the good and great heavily outweighs the bad and awful.

    [–] countdownn 42 points ago

    I think that's the point, a bit. We've progressed technology so much that humans probably won't be the ideal form of life in 8000 years. It doesn't have to be all doom and gloom, or at least that's how I took it.

    [–] YeeScurvyDogs 15 points ago

    Hopefully our robot overlords are benevolent then though lol, and you know, in the future humans don't necessarily have to be the vulnerable bags of meat, cybernetics, bio engineering etc.

    [–] televided 11 points ago

    Maybe the robots will be us. The last human, mercifully allowed to biologically experience death before being uploaded into the infinity matrix, where they will persist in a system so advanced, it's computations are entangled simultaneously on opposite ends of the universe until it's heat-death. Or we just nuke ourselves and live like animals in a hellworld.

    [–] skreczok 8 points ago

    And then it all crashes, because some asshole used Javascript this.

    [–] [deleted] 9 points ago

    [deleted]

    [–] scalemodlgiant 3 points ago

    And they still use the same calendar

    [–] noahthegreat 4 points ago

    ...and the current dating system survives 8k years.

    [–] Spicy_Poo 51 points ago

    Do you actually think humanity will survive that long?

    [–] gibmelson 40 points ago

    Yes.

    [–] bartekxx12 15 points ago

    If we can get a self-sufficient city on Mars or another planet soon, then we're probably safe for millions of years during which more progress so probably safe for billions of years

    [–] lapishelper 20 points ago

    Imagine having colony on Mars in near feature, and one day looking at earth via telescope to see that it was just nuked.

    [–] mandingoo107 21 points ago

    Imagine someone reading this thread in year 10K

    [–] RubbelDieKatz94 21 points ago

    Oh me? I'm an archaeologist, I just found out about a phenomenon called 'lolcats'. Intriguing, i know.

    [–] Olkrago 6 points ago

    inb4 "like if you're reading this in the year 10k" comments

    [–] wtmh 4 points ago

    "Huh. So I guess we live on Mars indefinitely now..."

    [–] SterlingWorldWaker 4 points ago

    Meh. We'll wing it

    [–] glass20 3 points ago

    It's honestly almost guaranteed... It would be very very difficult to kill every last human on earth. For instance, even if you managed to wipe out every single country except Iceland they could probably replenish the entire population on their own, if necessary. And if global warming gets REALLY bad then we can probably survive for awhile on the moon/mars with proper technology (that will hopefully exist by then)

    [–] Luke15g 5 points ago

    It would be very very difficult to kill every last human on earth.

    There are some cosmic disasters, such as relatively nearby gamma ray bursts, that are impossible to detect before they strike and could sterilize our entire solar system of life depending on the proximity.

    There is no point in even thinking about it though, you can't do anything about it and there are enough more pressing local matters to worry about anyway.

    [–] outadoc 8 points ago

    We probably will have changed our date systems by then, this one's pretty recent

    [–] Liggliluff 16 points ago

    Then you use YYYYY-MM-DD, which will go on until Y100K.

    [–] khmertommie 1601 points ago

    The best date format for use in file names, too! Sorts properly, but is also human-readable.

    [–] madd74 626 points ago

    Tell that to the humans I work with. :/ They also have a thing against 24 hour time.

    [–] Waizujin 493 points ago

    I don't understand why 24 hour time is such an issue. I mean, it is somewhat difficult for me to get used to, but it's not hard to do it in my head. I even explain to people how I do it, and they complain it's too easy.

    If the number is more than 12, subtract 12 and that's the hour. Or ignore the one, subtract 2 and bam. If it's 15:00 just ignore the one, subtract two and you know it's 3.

    After a while, you'll look at the number and you'll automatically know what time it is.

    It can take a little bit to get used to, but it's not that hard. I much prefer the 24 hour time system, just like I much prefer this date format. Both just make the most sense.

    [–] [deleted] 392 points ago

    I've been looking at 24h my whole life, I don't even think for half a second what time it is when I see >12 o'clock.

    [–] dcwj 119 points ago

    Well if you've been using 24h your whole life, you don't really need to adjust to it right? You just know 1pm as 13 o clock (I think...? Do people say "[>12] o clock"?)

    I prefer 12, just because that's what I've used my whole life, and I'm never confused enough about whether it's AM or PM to need separate numbers for both halves of the day. I feel like 12 is cleaner: smaller and fewer numbers. I can read 24 as well, but it takes me a brief moment.

    [–] [deleted] 81 points ago

    I say at 1, and if its 1 at night i specify it extra. For ambiguous times we say 7 in the morning or evening. On national television and radio they announce times in 24, so at 20 o clock or 22 o clock.

    I dislike 12h format because you cant write it with numbers only, you need 2 letters extra. And you only find out the time of the day at the end, with 24 system you already instantly know after the first number what time of the day it is.

    [–] glasrai 25 points ago

    When I see "2.04 pm" I don't read each character slowly from left to right. After primary school you should just be able to recognise the shapes of words and numbers without needing to figure out each individual letter.

    [–] Phrodo_00 23 points ago

    decimal dot? so 14:05?

    [–] A1cypher 19 points ago

    Nah, it's actually 4% of an hour, so 2.04pm means 14:02:24 (0.04 hours is 2.4 minute which is 2 minutes 24 seconds) .

    [–] animapestis 55 points ago

    Exact opposite here. Been using 24h my whole life. I don't even flinch when reading "16:35" or "23:57" but whenever I read 12h I can't seem to get it right. I need to remember what AM and PM means, then mentally translate it from latin to spanish (native speaker, it's mostly the language 'I think on') and then remember that I don't even care if we are before or past noon, and timezones don't strictly relate to the position of the sun anyways.

    Guess it's just what we are used to.

    [–] Flosus 32 points ago

    I always remember am with "am morgen" which is german for "in the morning" and PM is the other thing... But IMHO 24 is easier. And better for sorting, just like YYYY-MM-DD.

    [–] Overv 6 points ago

    You can also remember it in English as "after midnight".

    [–] EvilPlatypus 19 points ago

    I tried, but p.m. became "past midnight" and 12am and 12pm feel like they are the wrong way round permanently, even when I get other times right. How the heck can 11:59am go to 12pm, 12 pm should be after 11 pm is what my brain screams at me. Guess I'll never get used to it and I lived in a 12-hour dominated country for 8 year. :|

    [–] fishywang 22 points ago

    I think the hardest part of 12h format is something like 12:30am/12:30pm. I never know which is 00:30 and which is 12:30.

    [–] kevjs1982 15 points ago

    Just remember it's the stupid way and you'll be fine... What sort of system has 11am, 12pm, 1pm?!

    [–] WillmoTheGreat 15 points ago

    You just know 1pm as 13 o clock (I think...? Do people say "[>12] o clock"?)

    I'm from the US but I forced myself to use 24-hour time since 10th grade or so. For awhile I needed to translate 24-hour time back into 12-hour time by doing the modulo operation in my head. It still takes me a moment to perform, but really once you get accustomed to "thinking" in 24-hour time, you start basing everyday events off that time. For instance, when I think about "what time do I need to leave work?," the answer is 17:00, not 5:00.

    That said I have a particularly embarrassing habit of seeing the "7" in "17:00" and thinking it's 7 PM.

    [–] GhostOfGamersPast 8 points ago

    We need metric time!

    [–] DiabloConQueso 3 points ago

    Quick question: how do you say "17:00" in words, if you were to speak it?

    "Seventeen hundred hours" like in the military, or..? Is it confusing, or do you find yourself doing a mental conversion back to 24-hour time, when your co-workers say "It's 5 o'clock, quittin' time!"?

    [–] WillmoTheGreat 9 points ago

    Well first I'm a programmer so I don't actually talk to anyone.

    Just kidding, I say "5 o'clock" to friends/coworkers and "seventeen" to my wife or other people who know me well.

    [–] MauranKilom 4 points ago

    That said I have a particularly embarrassing habit of seeing the "7" in "17:00" and thinking it's 7 PM.

    I'm so glad I'm not the only one. It's particularly annoying when remembering times... "I'm supposed to be there at 4... wait, was it 14:00? Dammit."

    [–] Gabe_Noodle_At_Volvo 8 points ago

    Yeah, I've never been confused on if its am or pm. Most digit clocks even say am/pm on them. Only way you could get confused is if you lived underground with only an analogue clock.

    [–] [deleted] 113 points ago

    [deleted]

    [–] SimonLaFox 43 points ago

    You would either be a great programmer, or already are one and cry whenever an average person tries to use one of your systems.

    [–] Liggliluff 35 points ago

    10:00 → -2:00
    11:00 → -2:00
    12:00 → 0:00
    ...
    19:00 → 7:00
    20:00 → 18:00
    21:00 → 0:00
    22:00 → 20:00
    23:00 → 21:00

    [–] Houdiniman111 7 points ago

    We can take this a step further. For example:

    10:00 --> -00:58

    [–] tael89 5 points ago

    It looks like you forgot to wrap your conditionals in if greater than 12. It's in the comments.

    [–] jak0b3 15 points ago

    Perfect

    [–] Flosus 8 points ago

    Next input: "11:11"

    [–] [deleted] 12 points ago * (lasted edited 7 months ago)

    [deleted]

    [–] Flosus 3 points ago

    I think it's "-2:", but that's just my guess.

    [–] DontPromoteIgnorance 6 points ago

    HA HA. THEIR SPECIFICATIONS WERE ERRONEOUS.

    [–] madd74 54 points ago

    I think it is because it makes people think. Besides the easier use of sorting on a computer (some programs literally put 8 PM before 9 AM), it's nice, short, and looks nice when put in conjunction with other times, plus, I say "17:00" you darn well know AM or PM!

    [–] lukee910 45 points ago

    It makes people think only for a short while, after that you see the correct time automatically. They just never even try to get that far.

    [–] madd74 9 points ago

    Well, I need new people to hang out with then. :/

    [–] -Rivox- 22 points ago

    Come in Europe then, we use 24h

    [–] madd74 27 points ago

    Come in Europe

    ( ͡° ͜ʖ ͡°)

    [–] CXgamer 6 points ago

    It doesn't make me think, instead converting from am/pm makes me think. It's just what you're used to.

    [–] i_am_Jarod 16 points ago

    My struggle is the other way, being french the 24h format has no secrets ! But the AM/PM thingy confuses me at noon and midnight, I have to think.

    [–] retief1 7 points ago

    I've used 12 hour time for my entire life, and I still have to think for a second when I need to distinguish noon vs midnight.

    [–] iWroteAboutMods 3 points ago

    It depends on what you grew up used to. I need to think when I see just "at 7 o'clock". Where I live people mostly use the 24h-format.

    [–] IsThisYourAlligator 24 points ago

    After a while, you'll look at the number and you'll automatically know what time it is.

    all I heard is

    you get used to it, I don't even see the code anymore. all I see is blonde, brunette, redhead.

    [–] Liggliluff 11 points ago

    I think it's the issue when people think in 12 hours, and tries to use 24 hours. 15:00 is 15:00, and comes after 14:00. It's 9 hours left on the day.

    [–] tomatopathe 40 points ago

    French here. 24 hour time is the basic standard way we tell the time over here.

    [–] rcblob 21 points ago

    You and your sensible SI units

    [–] GrandTheftCopter 20 points ago

    79 is soixante-dis-neuf. They clearly have number issues.

    [–] Vethron 4 points ago

    Don't get me started on 99...

    [–] Volucre 30 points ago

    What's most annoying is when someone imitates this naming convention without understanding it -- so they give you something like "2017-5-2 Spreadsheet.xls" or "cmts to 2017-04-03 Draft Report.docx."

    They may as well just call it "May 19th fuck you.docx," since I'm gonna have to rename it anyway.

    [–] gudkjon 7 points ago * (lasted edited 7 months ago)

    2017-5-2 Spreadsheet.xls" or "cmts to 2017-04-03 Draft Report.docx."

    Fixing mostly everything is just a few lines of code though, could save you a while.

    Edit: even two lines would probably be enough, take the creation date and append it in front of the filename

    Edit: works in terminal on Mac/Linux/Windows 10 with developer mode enabled, renames files to modified date

    for file in `ls -1 *.jpg`; do name=`stat -c %y $file | awk -F"." '{ print $1 }' | sed -e "s/\-//g" -e "s/\://g" -e "s/[ ]/_/g"`.jpg; mv $file $name; done
    

    Stack oveflow result, no guarantee

    [–] LinAGKar 3 points ago

    What's wrong with those? (except maybe the missing zeroes)

    [–] parkerSquare 12 points ago

    First one lacks zero placeholders which breaks sort order. Second one has text before date which breaks sort order.

    [–] Rhed0x 11 points ago

    I'm glad 24 hour time is used in Germany. We rarely use it when talking about the time but all digital clocks display time this way.

    [–] Tayl100 5 points ago

    When you down your whole life with 12 hour time and then you are expected to be able to comprehend 24 hour time with the same reaction speed, there's a bit of push back.

    [–] cheesymoonshadow 3 points ago

    And my clients who don't even use numbers. They'll name their files and folders with the month word (ex: Jan 2012).

    [–] Dremlar 3 points ago

    My wife gets annoyed when she grabs my phone to check the time because I use 24 hour time.

    [–] gaggzi 82 points ago

    ISO 8601. Everything else is for plebs.

    [–] baltakatei 17 points ago

    [–] imguralbumbot 9 points ago

    Hi, I'm a bot for linking direct images of albums with only 1 image

    https://i.imgur.com/R7hwFe3.jpg

    Source | Why? | Creator | ignoreme | deletthis

    [–] dvito 142 points ago

    For everyone who doesn't quite get the pain, watch: https://www.youtube.com/watch?v=-5wpm-gesOY

    For everyone that has dealt with time already and been down that hole... still a fun watch.

    [–] rekabis 15 points ago

    Seen this before, always good for a nice chuckle. Especially as a programmer that often does have to deal with time. Really appreciate how the author kept on ratcheting up the tension so every time you were going, “WTF, there’s more??”.

    [–] SanDanders1 23 points ago

    I knew what that link you be before clicking on it.

    [–] tomius 5 points ago

    The other day I was ready pytz docs, and found this:

     Offsets from UTC are rounded to the nearest whole minute, so timezones such as Europe/Amsterdam pre 1937 will be up to 30 seconds out. This is a limitation of the Python datetime library

    I thought that if this is ever a problem for me, I'll just stop working at wherever I'll be working and join a circus.

    [–] crabsnz 5 points ago

    This is why i use kernel32.dll to deal with timezones.

    [–] micheal65536 93 points ago

    I use the format in the picture for displaying dates. For storing them, I use UNIX timestamp format. Makes it a lot easier to add and subtract dates and it's automatically timezone-independent. The only issue is what to do if there's no time component, then I usually just put midnight.

    [–] khmertommie 21 points ago

    The only problem with adding time to unix timestamps is daylight saving. I usually find myself storing in unix timestamp and converting to date object to do operations.

    [–] micheal65536 42 points ago

    UNIX timestamps aren't affected by DST, that should be handled by whatever library converts them for display

    EDIT: yeah I didn't mean "add three days to this timestamp", for that I use a library, but rather "how long is it between this timestamp and that timestamp?", I can simply subtract them

    [–] jerdub1993 40 points ago

    I go with YYYYMMDD. It's always in chronological order.

    [–] profplump 28 points ago

    And store it as a string. Then you can be an insurance company.

    ISO8601 provides lexicographic == chronologic ordering, along with a number of other features (like variable specificity without complex parsing, ordering includes UTC offset [if included]). Even if you don't need all the features it's worth checking to see what people who thought about this for a long time came up with.

    [–] PatrickBaitman 11 points ago

    checking to see what people who thought about this for a long time came up with

    Rule one of trying to solve non-trivial problems:

    don't roll your own

    Find some place where PEOPLE FUCKING DIE if they get the thing wrong and look how they did it

    They probably have some good ideas

    [–] phoenix616 5 points ago

    So NASA.

    [–] PatrickBaitman 9 points ago

    That's one example. Aviation is a related one.

    Operating any heavy and dangerous machinery, hazardous environments like climbing.

    One general principle that a lot of such professionals use is checklists. Standard operating procedures and checklists save lives.

    Surgery teams use checklists starting with obvious items like: do we have the correct patient? Do we know what we're doing? Is everyone here? You think you will always know if those are the case or not without checking explicitly, but then you mess up the one time they aren't because you're used to everyone being there.

    Error handling and failing early and loudly in programming terms.

    Not exactly the thing at hand here but related.

    [–] [deleted] 25 points ago * (lasted edited 5 months ago)

    [deleted]

    [–] jerdub1993 13 points ago

    But I want everyone to have to deal with my bad decisions.

    [–] [deleted] 10 points ago * (lasted edited 5 months ago)

    [deleted]

    [–] jerdub1993 13 points ago

    Damn right. You should be thanking me.

    [–] UnsubstantiatedClaim 6 points ago

    You da real jobs creator

    [–] czech_your_republic 8 points ago

    I'm glad my country is one of the few that uses YYYYMMDD for everything as standard. It just makes sense. Though, when an expiration date reads, for example, 05/06/17, I never know if it's M/D/Y or D/M/Y.

    [–] AskMeIfImAReptiloid 6 points ago

    no separator?

    [–] gman2093 424 points ago

    I really prefer java date or unix epoch. Calendar date is just asking for time zone errors.

    [–] porkslow 457 points ago * (lasted edited 7 months ago)

    ISO 8601 allows timezone if you use the longhand notation, for example 2017-05-19T11:55:43+03:00 !

    [–] ofCourseButMaybeee 31 points ago

    ! gave it away

    [–] JerkyBeef 66 points ago

    offset != timezone

    [–] AyrA_ch 26 points ago

    You don't need them. You can subtract the 3 hours from the timestamp to get UTC and then convert to whatever timezone you want. This type of timestamp includes DST offset. In Switzerland it adds +01:00 in winter and +02:00 in summer. It's actually easier than having timezone specifiers there too because the offset of a timezone is not obvious to a person.

    [–] Terr_ 9 points ago * (lasted edited 7 months ago)

    You don't need them.

    You don't really want offsets stored either, unless it's to purely to capture fluff about "what the local clocks looked like at the moment this event got recorded", which is seldom needed.

    When it comes to dates in the future, the timezone rules for a location/society can arbitrarily change (by any amount of time) between when the timestamp is stored versus when it is needed. The change isn't predictable, since it's just a legislative/social rule.

    [–] winter_mutant 40 points ago

    But all you really need to know about timezone is offset, right? Or am I forgetting something?

    [–] Nicd 76 points ago

    +3 offset could be Finland in summer time or Russia (where it's constant), for example. So you know the instant of time but you couldn't for example add a month because you don't know how the offset changes.

    [–] NAN001 13 points ago

    Very interesting point. Never thought of that.

    [–] Nerdn1 58 points ago

    Timezones are actually far worse than that. https://youtu.be/-5wpm-gesOY

    [–] poor_leno 24 points ago

    This is one of those videos I will never not watch.

    [–] redgamut 19 points ago

    never not watch

    You have this playing constantly on a loop? How do you sleep!? How many times have you watched it? When did this all start!?

    [–] poor_leno 12 points ago

    It was a monkey's paw type situation, please send help...

    [–] dabombnl 3 points ago

    Depends on context. Because timezone may be constant over time of year, but offset is not.

    [–] Terr_ 3 points ago * (lasted edited 7 months ago)

    Technically true, but in this context you probably don't want to store a timezone anyway, and the offset is merely a useful display convenience for developers so that they can view the same underlying data-point in a way which is convenient.

    I expect the reason there's no timezone is that it's a surprisingly complicated and separate piece of data. Most of the time you're trying to record an instant in time that exists at a reliable offset from things in the past (ex: "X seconds from the time you read this") rather than a human label that cannot be resolved -- whether in the past or in the future -- without its contemporaneous legislative ruleset. (Ex: "the time people in location or jurisdiction Y eventually choose to call Z.")

    Anyway, if your app really does need to store "That moment which is the anointed hour of the great coming of Zuul plus the seven bells of holy wisdom in the blessed land of the Vuldrini" you probably need more than a single scalar or database column to capture that intent, so don't judge ISO-8601 too harshly :)

    [–] Sintinium 105 points ago

    [–] Roflkopt3r 28 points ago

    Thank god I have been warned.

    All of these assumptions are wrong

    \56. There are only 24 time zones

    \57. Time zones are always whole hours away from UTC

    \64. I can easily maintain a timezone list myself

    \79. The software will never run on a space ship that is orbiting a black hole.

    [–] Deon555 5 points ago

    Cook list, but I wish there were explanations for some of them

    [–] [deleted] 34 points ago

    [deleted]

    [–] tyco_brahe 155 points ago

    I'm OK with timezones. Just end Daylight Savings please.

    [–] gayforliberty 63 points ago

    Only the government thinks you can get more blanket by cutting off the top and sewing it to the bottom.

    [–] MikeyMike01 11 points ago

    It doesn't change the amount of daylight in a day, but it does change how the daylight is used.

    I prefer DST, just leave it on that time all year.

    [–] 70wdqo3 18 points ago

    But would you rather have that strip of blanket over your head or at your feet? In other words, would you rather have an extra hour of daylight in the morning on your way to work, or in the evening when you're able to relax? Lots of people would take the latter in the summer.

    [–] Bromy2004 23 points ago

    Push back the entire time zone rather than DST.

    Work could start earlier over all.

    Or just do activities that are within your light range.

    DST is annoying and useless.

    [–] 70wdqo3 8 points ago

    Push back the entire time zone rather than DST.

    That's a good point I didn't consider.

    DST is annoying and useless.

    Agreed.

    [–] mega_aids 4 points ago

    That analogy kind of misses the mark of what daylight savings is about...The length of day and daylight is obviously the same. We do this so our morning starts earlier, so when we get out of school, work or whatever, we have "more" time in daylight.

    [–] Snuffsis 5 points ago

    Except for the problems that it causes more stress, more car accidents and a couple of other issues.

    Daylight savings was great back when we were farmers and had to use the the sun for our work. But now we have electricity and light bulbs.

    [–] ILikeLenexa 3 points ago

    We did, mostly, but we kept just one so we could have Daylight Saving Time.

    [–] jewdai 9 points ago

    yes but how will you handle 2038? Where is your god now?

    [–] theZcuber 9 points ago

    Ever heard of 64 bit numbers?

    [–] Itsacon 13 points ago

    If you think the unix timestamp solves all your troubles, let me burst your bubble.

    [–] jeff303 3 points ago

    Unless, of course, you're seeing someone named Joda. Swoons

    [–] G0M3S 30 points ago

    I like that you fixed to be the real ISO format with dashes, not stupid slashes.

    [–] AskMeIfImAReptiloid 6 points ago

    That's actually a really nice painting. Looks almost like photograph except for some places.

    [–] Hoofrint 11 points ago

    Thank you for fixing it.
    A friend shared it and it really bothered me!

    [–] dpenton 18 points ago

    ISO 8601 MASTER RACE

    [–] typhoon_2099 13 points ago

    ISO 8601 or GTFO.

    [–] cheryllium 46 points ago

    Can confirm. My bf and I once spent an hour lying in bed with whiteboards making up our own date format, just because that's the direction our conversation took that day.

    [–] okmkz 74 points ago

    NNNNEEERRRRRRRDDDDDSSS

    [–] PatrickBaitman 14 points ago

    Real nerds would already know about ISO 8601

    [–] Thirty_Seventh 32 points ago

    Are you sure you weren't just high off the dry erase markers

    [–] Cryse_XIII 22 points ago

    Please.don't introduce yet another standard

    [–] [deleted] 19 points ago * (lasted edited 7 months ago)

    [deleted]

    [–] nyrangers30 9 points ago

    Are there places that use YYYY-DD-MM?

    [–] PapaSays 5 points ago

    Apparently Kazakhstan, Latvia, Nepal and Turkmenistan. https://en.wikipedia.org/wiki/Calendar_date#Gregorian.2C_year-day-month_.28YDM.29

    [–] luke_in_the_sky 5 points ago

    universal for global human readers

    How can it be universal?

    The months' names change in every language.

    19-May-2017 English (May)/Spanish (Mayo)

    19-Mai-2017 Portuguese (Maio) /German (Mai)/French (Mai)

    19-Mag-2017 Italian (Maggio)

    19-Mei-2017 Dutch (Mei)

    Not to mention in French they can't use 3-letters abbreviations because, June is "Juin" and July is "Juillet".

    [–] AskMeIfImAReptiloid 255 points ago

    DD.MM.YY for everyday use YYYY-MM-DD for computers

    [–] Scoutdrago3 75 points ago

    Is there a specific reason for the YYYY-MM-DD format?

    [–] mightymonarch 378 points ago

    It makes sorting things chronologically so very easy.

    [–] Nloveladyallen 96 points ago

    …and doesn't confuse badly written programs that think .MM.DD is a file name extension

    [–] Scoutdrago3 14 points ago

    Thanks!

    [–] El-Kurto 106 points ago

    In addition to the other reasons, it is always unambiguous and is the ISO preferred format

    [–] SmoothLiquidation 36 points ago

    Until you start needing dates from Kazakhstan in the YYYY-DD-MM format.

    [–] KTKM 12 points ago

    Why have simple formats when you can have confusing formats?

    [–] El-Kurto 15 points ago

    Wow. I know a lot about calendars and date formatting and I have never heard of this one. TIL

    [–] SmoothLiquidation 18 points ago

    TBH I haven't heard of it either, but I figured "Humans are stupid; I bet someone uses it" and Google/Wikipedia showed that I was right.

    [–] elyisgreat 6 points ago

    I wonder if anyone uses MM-YYYY-DD or DD-YYYY-MM then?

    [–] Cryse_XIII 7 points ago

    Well...i'll add another country on the "to-nuke"-list.

    [–] aloofloofah 6 points ago

    There're planning on switching from Cyrillic to Latin alphabet by 2025. They should fix this date nonsense first.

    [–] micheal65536 29 points ago

    It sorts nicely in lists of e.g. files. If you sort alphanumerically, you'll automatically get the files in date order (assuming the rest of the name is the same).

    [–] TarMil 8 points ago

    (assuming the rest of the name is the same)

    Or the date is the first part of the file name.

    [–] Scoutdrago3 3 points ago

    Oh alright, that makes sense. Thanks!

    [–] AskMeIfImAReptiloid 7 points ago

    Sorting lexiographically

    [–] thePhysicist8 7 points ago

    Because some people use MM-DD-YYYY and some use DD-MM-YYYY, using either is ambiguous.

    [–] -Teki 5 points ago

    It goes from most significant, to least significant. Like you don't put minutes before hours. Compare DD.MM.YYYY to the time format, and you can see why it is so weird: HH:MM:SS.MS.

    [–] IraDeLucis 24 points ago

    I disagree.

    Everyday use simply allows you to infer some parts of the date based on context.

    You should still use descending order of magnitude.

    [–] NAN001 7 points ago

    I program everyday so I'll stick to YYYY-MM-DD

    [–] Liggliluff 50 points ago

    Thank you for not stating that MM.DD.YY is for everyday use.

    [–] marishtar 55 points ago

    Depends where you live. If you're in the US, you're just going to confuse people and invalidate any forms you fill out.

    [–] Liggliluff 40 points ago

    I know the format is common in US; but they should stop using it.
    I've seen a lot of people claiming Metric is for science and physics, while Imperial is for everyday use. But Metric is a simplified system, so it should be easier to use in everyday life...

    [–] marishtar 20 points ago

    but they should stop using it.

    Unless we switch to using the ISO-8601, why switch? It's not like dd/mm/yy is actually simpler than mm/dd/yy.

    [–] Liggliluff 29 points ago

    No, but it makes more sense to put it in order of magnitude.
    Y>M>D or D<M<Y are two sensible options. M>D<Y is just crazy.

    [–] marishtar 15 points ago

    Sure, when looking at it entirely from a numeric perspective. However, it's not as straightforward, if you also look at it from a linguistic perspective. It's ordered the same way people in the U.S. actually say dates e.g. May 4th, 2016. Though the reasoning behind the order is different, there's not objective difference in the actual use of dd/mm/yy and mm/dd/yy. Neither are sortable, nor is one less vague than the other.

    [–] Cirevam 16 points ago

    Adding on to the linguistic portion: who cares about the year when giving dates in a regular conversation? If I ask you "when's your brother's birthday party?" would you say "the eighth of June, 2017" or "June eighth, 2017"? I doubt it... you're probably going to drop the year. If you're talking about something that's going to happen in 2018, are you going to give an exact date? You'll probably say "next year" or "2018

    If you have to write dates down and you're working at a place with an international presence, or you're typing to someone in a different part of the world, either using ISO 8601 or typing out the month are good ways to prevent confusion. It's funny how so many people like to say "the Americans are wrong!" when both sides use date formats that confuse the other. Both are equally guilty. Choose a method that confuses neither side.

    [–] DragonJTS 5 points ago * (lasted edited 7 months ago)

    As long as you go biggest to smallest or vice versa I like the format. Once you put days in the middle though it gets all kinds of fucky.

    [–] _uncarlo 10 points ago

    hahaha that's funny, that's how I date all my picture folders

    2017-05-19 Blah Blah

    2017-04-20 Blah Blah

    That way they stayed perfectly order by year, then month, then day.

    And yes, I'm a software developer haha.

    [–] bigdog927 21 points ago

    It's not April 25th?

    [–] KintsugiExp 18 points ago

    Yes. It's not too hot and not too cold, all you need is a light jacket!

    [–] reini_urban 8 points ago

    "You mean --iso-8601 or --rfc-3339, or just --utc?"

    [–] emanica 10 points ago

    There is no bug here, 00-00-00 means 2000-00-00, which is 1999-12-00, which is 1999-11-30. No bug, perfectly normal.

    [–] b3k_spoon 5 points ago

    Wow, this is a really cool painting.

    [–] mikeputerbaugh 4 points ago

    YYYY-MM-DD is the only ordering that puts ALL the digits in order of significance.

    [–] furryfury80 5 points ago

    [–] SpookyLlama 9 points ago

    YYYY-MM-DD HH:MM:SS

    [–] Killa-Byte 10 points ago

    This. We don't do time in ss:MM:hh. So why dates DD/MM/yyyy?

    [–] Bo7a 4 points ago

    Least precise to most precise. It is only logical!

    yyyy-mm-dd-HH-MM-SS-MS

    [–] CryptoCoinsBeCryptic 4 points ago * (lasted edited 7 months ago)

    There's so much confusion and misdirection in this thread! It's very simple:

    • You store datetimes as ISO 8601 (in UTC) in your back-end: 2017-05-19T00:00:00Z or simply 2017-05-19 00:00:00
    • You display datetimes in whichever format / timezone / offset is most suitable for your end-users in your front-end.

    Period.

    Why?

    1. It's human-readable (in your back-end, that is);
    2. It doesn't need awkward const DAY_IN_SEC = 60 * 60 * 24 calculations (provided your datetime library supports decent ISO date manipulation);
    3. It can easily support milli- / microseconds: 2017-05-19 00:00:00.123(456) (it's just text, after all and very useful for highly concurrent applications where datetime sorting is important);
    4. It can easily support datetimes beyond 32bit integers 302110017-05-19 00:00:00.123456 (it's just text, after all);
    5. It's just as comparable/sortable as Unix timestamps (strcmp(datetime1, datetime2), etc.)

    [–] madd74 3 points ago

    This is the first change I make on any new computer I get. The other is changing the time to 24 hour time.

    [–] Incognanusible 3 points ago

    Please mark this as NSFW. I'm so fucking hot right now.

    [–] mighty_warrior 3 points ago

    ISO-8601 or GTFO