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.
wizardbeard@lemmy.dbzer0.com 2 hours ago
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.