- 48comments
- 277comments
- 26comments
- 211comments
- 709comments
- 35comments
- 58comments
- 2comments
- 5comments
- 18comments
- 40comments
- 1comments
- 70comments
- 48comments
- 32comments
- 30comments
- 36comments
- 109comments
- 3comments
- 83comments
- 112comments
- 93comments
- 32comments
- 7comments
- 92comments
- 17comments
- 33comments
- 21comments
- 118comments
- 4comments
good lord, now we have LLM-speak "footguns" in article titles. what have we come to.
what about the load bearing real unlocks of the footguns?!??!?
https://i.programmerhumor.io/2026/09/09db9203bc618d8704855e1...
? Footguns as a synonym for "caveat" or "gotcha" were in use long before LLMs. I hate Claude speak too but there's no need to knee-jerk blame everything on LLMs.
While that is true (the LLMs surely had to learn it from pre-existing content), I think it's been so thoroughly overused and turned into a cliche that the term has been ruined for the foreseeable future.
I think most of the confusuion comes from "AT TIME ZONE" being the syntax for both the conversion from _and_ to timezone'd timestamps. Maybe it would have been more intuitive had the two operations gotten different wordings, e.g.:
timestamp to timestamptz: AS ZONED AT TIME ZONE ...
timestamptz to timestamp: AS LOCAL AT TIME ZONE ...
Postgres 'at time zone' is confusing, but it's internally consistent. Once you understand what it's doing, you can work with it and it will reliably behave the way it's designed to.
https://oneuptime.com/blog/post/2026-01-25-postgresql-timezo...