Gf: "Why are you such a typist"

Me: "I promise not to buy more keyboards with blue switches..."

Gf: "No, I mean like being racist or sexist, but you discriminate types"

Me: "Uhhh"

Gf: "You are always bitching about how awful date/time types are, with timezones, leap seconds and daylight savings"

Me: Face turns pale, thousand yard stare, vietnam-flashback to when I was writing a calendar scheduling/meeting/matching tool which used 3 databases, with timestamps in different formats, and web frontends for people in offices around the world.

Me, with a soft broken voice: "So?"

Gf: "You've been working on that palette tool this week, and you keep talking about how interesting all these colorspaces, white balances and conversion formulas are"

Me: 🤔

I startet at this company where they made a map where some locations where displayed on a map. It took like 30 seconds to load the locations - and it could only display ten at once. To cover this fact they made it impossable to zoom out...
I circumenvented their incredably bad orm and queried the DB directly, created some indices, and only shipped coordinates, type and label (whereas they shipped the whole datasets to the browser before) - and suddenly i could show all 30k
pins at once in microseconds having less traffic then before. That was quite a leap.

Needless to say the app never reached nearly production, I left the shit show soon after and the ceo is dead by now.

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...