Event time timezone handling
An AI agent wrote this Python helper to show 'when an event starts' for a global scheduling app. It works in the developer's tests, who happens to be in UTC. What's wrong for real users, and how should it be done?
Implement
format_event_start(start_ts: int, tz_offset_minutes: int) → strExamples
in
[1780000000,0]out"2026-05-28 20:26 +00:00"in
[1780000000,330]out"2026-05-29 01:56 +05:30"in
[1780000000,-480]out"2026-05-28 12:26 -08:00"What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 17 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.