If you work at a company where all of its offices are in the same time zone and you’re time-stamping logs, then it’s more expedient for understanding and placing an event in time against other things to use local time.
Unless everything is already standardized as GMT with offset I guess, but I feel like down that route lies madness.
“I got your email at 20:37:45-7:00” is a few more steps than “I got your email at 1:37PM”.
It’s not a big hurdle, but I try to design for the newest member on the team scrambling in panic rather than a calm cool professional already familiar with conventions.
Now, as soon as we do start dealing with multiple time zones I would just cut my custom time formatting string down to the shorthand to have the scripting language output in the full ISO 8601 format. But until then, being able to easily sort the the date properly and having the time be more human readable is a more “workable” compromise.
Seeing how often I get meeting invites for the wrong time because coworkers ignore my 11 a.m. CDT, and invite me in their timezone, I feel like communicating everything in UTC would be easier, because there could be no confusion.
If you work at a company where all of its offices are in the same time zone
coworkers ignore my 11 a.m. CDT, and invite me in their timezone
PLEASE read the comment you are replying to before submitting your reply.
Even in a single-timezone organization, I think it is still useful to use UTC+offset because it avoids DST confusion and lets the company expand to a second timezone without the team members there feeling second-class. But, GMT+offset does have costs with dealing with people that don’t really think about timezones when scheduling, and those costs might overwhelm any advantages.
Now, as soon as we do start dealing with multiple time zones I would just cut my custom time formatting string down to the shorthand to have the scripting language output in the full ISO 8601 format. But until then, being able to easily sort the the date properly and having the time be more human readable is a more “workable” compromise.
How so, out of curiosity?
If you work at a company where all of its offices are in the same time zone and you’re time-stamping logs, then it’s more expedient for understanding and placing an event in time against other things to use local time.
Unless everything is already standardized as GMT with offset I guess, but I feel like down that route lies madness.
“I got your email at 20:37:45-7:00” is a few more steps than “I got your email at 1:37PM”.
It’s not a big hurdle, but I try to design for the newest member on the team scrambling in panic rather than a calm cool professional already familiar with conventions.
Now, as soon as we do start dealing with multiple time zones I would just cut my custom time formatting string down to the shorthand to have the scripting language output in the full ISO 8601 format. But until then, being able to easily sort the the date properly and having the time be more human readable is a more “workable” compromise.
Seeing how often I get meeting invites for the wrong time because coworkers ignore my 11 a.m. CDT, and invite me in their timezone, I feel like communicating everything in UTC would be easier, because there could be no confusion.
PLEASE read the comment you are replying to before submitting your reply.
Even in a single-timezone organization, I think it is still useful to use UTC+offset because it avoids DST confusion and lets the company expand to a second timezone without the team members there feeling second-class. But, GMT+offset does have costs with dealing with people that don’t really think about timezones when scheduling, and those costs might overwhelm any advantages.
Did you actually read beyond the first line?