... fucking timezones

Fuck fucking timezones!

Me: Anytime 9am - 12 my time suits me fine.

Him: Sure, noon our time suits us fine.

Me: *talking to myself* I said no later than 12 my time, theres a 2 hour difference. FFS, uh, I'll have to cancel this, move that around, skip that, ARGH!!! fucking hell jackass ... FINE!!!

...

Him: That calendar invite is for 4pm our time, thats a little too late for us.

Me: ...... but they are 2 ..... 2 hours ahead so ..... oh, thats 10am my time .... oh shit

Well, if your tests fails because it expects 1557525600000 instead of 1557532800000 for a date it tells you exactly: NOTHING.

Unix timestamp have their point, yet in some cases human readability is a feature. So why the fuck don't you display them not in a human readable format?

Now if you'd see:

2019-05-10T22:00:00+00:00

vs the expected

2019-05-11T00:00:00+00:00

you'd know right away that the first date is wrong by an offset of 2 hours because somebody fucked up timezones and wasn't using a UTC calculation.

So even if want your code to rely on timestamps, at least visualize your failures in a human readable way. (In most cases I argue that keeping dates as an iso string would be JUST FUCKING FINE performance-wise.)

Why do have me parse numbers? Show me the meaningful data.

Timestamps are for computers, dates are for humans.

I hate time.

Yes, that dimension which unidirectionally rushes by and makes us miss deadlines.

Also yes, that object in most programming languages which chokes to death on formatting conversions, timezones, DST transitions and leap seconds.

But above all, I hate doing chronological things from the point of view of code, because it always involves scheduling and polling of some kind, through cron jobs and queues with workers.

When the web of actions dependent on predicted future and passed past events becomes complicated, the queries become heavy... and with slow queries, queues might lock or get delayed just a little bit...

So you start caching things in faster places, figure out ways to predict worker/thread priorities and improve scheduling algorithms.

But then you start worrying about cache warming and cascading, about hashing results and flushing data, about keeping all those truths in sync...

I had a nightmare last night.

I was a watchmaker, and I had to fix a giant ticking watch, forced to run like a mouse while poking at gears.

I fucking need a break. But time ticks on...

I work in a multinational ..time stamps everywhere without fucking Timezones..fucking Jira shit why is there no TZ on this shit…utter cunts who configured it or the software itself

2 fucking AM. My phone rings.
-Hi! Oh sorry did I wake you?
-Yes...
-But its only 7 PM!! Why are you a sleep so soon???!
-Grrr... Coz we are in different timezones dumbass!
*call disconnected*

So today's the day the child leaves the babysitter.

Today's the fucking day that I learn why the fuck everybody says date's are a fucking headache. Or was it yesterday? I don't know.

Fucking dates, timezones, time calculations...

FUCKING TIMEZONES. FUCKING JAVASCRIPT.

Date.parse("2019-01-01") = local time
Date.parse("2019-01-01T00:00") = UTC

Why? How's that supposed to make sense? Am I stupid? I just want UTC to be assumed for everything. Anyone? Any suggestions?