5 ms·
You’ve never worked across time zones have you? I find it’s a lot easier to say “that commit from 2 hours ago” than do the mental math during a code review or d
by oakmad 6y ago
You’ve never worked across time zones have you? I find it’s a lot easier to say “that commit from 2 hours ago” than do the mental math during a code review or debug session. However I do think it should be opt in as I understand your POV and in my experience it’s never an issue until it’s a big one. In our ui we show ago, local and point of origin for all time zones we deal with in a popover.
- stinos 6y agoYou’ve never worked across time zones have you? Actually I have, and then we all use GMT when communicating timestamps. But it's like another commenter mentions: yes, 'that commit from 2 hours ago' is still doable (though if it matters we communicate SHAs), but when it goes to 'a day ago' it doesn't really work out anymore.
- user5994461 6y ago"GMT" That alone hints you're either working in the UK or you're confusing GMT with UTC, or both.
- phaemon 6y agoOr, nobody cares about fractions of a second when organising a meeting, so to all intents and purposes they are the same.
- user5994461 6y agoPoint being, they are not the same. There is one hour difference between UK Time, GMT and UTC for half of the year, due to daylight saving time.
- alanpearce 6y agoGMT stays the same throughout the year. The UK switches to BST for the summer. https://en.wikipedia.org/wiki/British_Summer_Time https://en.wikipedia.org/wiki/British_Summer_Time
- user5994461 6y agoCrazy enough your statement is equally right and wrong. There is really a lot of confusion between GMT, BST, UK time and Greenwich time. ^^ Greenwich is a borough in East London, there is an old museum with the line on the ground that defined the meridian. You can visit if you come across London. GMT, namely Greenwich Meridian Time is not actually the time of the meridian of Greenwich for half of the year. When you find yourself working with GMT, you really need to think about how you got there because it's wrong. 90% of the time you meant to use UTC and the other 10% you meant Europe/London timezone.
- bitdivision 6y agoI don't understand why his statement was wrong. GMT does not change according to daylight savings time as far as I know?
- user5994461 6y agoGMT = Greenwich Meridian Time The time at the greenwich meridian = not GMT See the problem here? I know it sounds like a bad pun but it's a real problem that every developer in the UK struggled with. To make thing worse, Greenwich the location is right next to the financial district of London where thousands of developers make financial software that are one hour wrong.
- ljm 6y agoI have to say that the level of confidence you have while being so misinformed is rather comical. I lived in Greenwich, I don't remember entering a new space-time continuum when getting off the DLR at Cutty Sark. You know, compasses spinning eratically, GPS going haywire, cuckoo clocks spinning out of control, because the bubble around the Greenwich Meridian transcends the mortal plane. GMT is the timezone we have between the end of October and the end of March. Between the end of March and the end of October, it shifts an hour ahead and becomes BST, or GMT/UTC+1. Greenwich is also South East London, not East London, as it is south of the Thames.
- deleted 6y ago[deleted]
- qw 6y agoThe time displayed by git or other programs could simply be converted to the timezone you feel comfortable with?
- nlitened 6y agoFrom my experience, implementation of time zone conversions is too often wrong. I work with many time zones, and strongly prefer either GMT+0 or “x hours ago”.
- IggleSniggle 6y agoThis is always such a ball of yarn, but working in a UI where both “absolute” and “relative to the locale of where it happened” are important contextual information, I’ve come to the conclusion that it is actually quite sensible to show both UTC and “local to where the event occurred” time at the same time, every time.
- monadic2 6y agoI write a lot of incident reports with timestamped logs. I think about these date formats a lot. I don't mind the informal formatting if you can click through to get a precise timestamp (either UTC or with timezone). However, in my experience, this is rare.
- Benjamin_Dobell 6y agoI work across time zones daily. If I'm using a UI, I expect dates to be displayed in my time zone. If I'm communicating with someone in another time zone, then I'll use relative time. However, in their head, they're still going to be converting that to local time. I don't see why you wouldn't just want to skip the middle man.
- throwaway894345 6y ago> I find it’s a lot easier to say “that commit from 2 hours ago” than do the mental math during a code review or debug session Unless you have half a dozen commits from 2 hours ago, which is pretty common in active repositories. It's never been very hard for me to tell whether a time stamp was a month ago, a day ago, or a few minutes ago, but it's impossible to figure out the roughly what time the commit from "1 day ago" was.