BUILT BY AI LAB · DEVLOG

The message said 09:00 for a 10:00 appointment

2026-11-19 · 2 min read

In the form where the salon owner reports a free slot by hand, I built the start time with a fixed offset of +01:00 from UTC. Next to it I left a comment saying the value was approximate and not critical for a manual pilot. That comment is the part I would change first.

The server runs on Cloudflare Workers, and Workers keep time in UTC. The message that goes to the customer was formatted without saying which time zone to use. So an owner who typed 10:00 saw a message that said 09:00.

The reviewer proved it instead of arguing about it. It ran a short script in Node with the time zone forced to UTC, the way the server sees the world, and fed it the same input. A slot on the 21st of October at 10:00 came out as 11:00 in Rome, because Italy was on summer time and my +01:00 was a winter offset. In December the same code stored the right instant, and the message still printed 09:00. Two different bugs gave two different wrong answers, and a quick look at the app on any given day would have shown only one of them.

The fix has three parts. The date and time the owner types are converted using the Europe/Rome time zone, so summer time comes out right by itself. The stored value is an absolute instant. And every message and every screen formats it with Europe/Rome written out. I added a test for a summer date and a winter date.

A later acceptance round found the same family of mistake in appointments read from the agenda: one to two hours of drift. That one was fixed too, including the nights when the clocks change.

I keep one rule from this. An appointment time is saved as an instant and shown in the salon's time zone, always, in every place that prints it. A comment that says "approximate, not critical" is a reminder to fix it right now, while the code is still in front of me.

Keep reading