Programming

17133 readers

420 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Logging Best Practices: The 13 You Should Know (2019) (www.dataset.com)

submitted 4 months ago by lysdexic@programming.dev to c/programming@programming.dev

7 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] nous@programming.dev 2 points 4 months ago (2 children)

You lose information when DST kicks in - which is not great. It is trivial to convert to any timezone so there is little point in logging in anything but UTC and keeps everything consistent. Especially when comparing dates from servers in different timezones.

[–] Alexstarfire@lemmy.world 1 points 4 months ago* (last edited 4 months ago)

My job would be much easier if everything was stored internally in UTC. But that boat sailed long before I started working there. Instead, I get to convert from local server time to UTC to local client time. 😭

[–] Fal@yiffit.net 0 points 4 months ago

You don't lose info as long as the offset is marked correctly