TWIL April 24th 2026
- Having the same failure message for every cause of failed login may be good for security
- But it's pretty awful UX and can lead to a lot of false 'bug' reports
- Sometimes it's best to just slap a
@ts-expect-erroron everything and leave the big rewrite for later- Especially when being on old TS blocks a bunch of key dependency upgrades
- You don't always need a GIN index just cos it's a JSON column you're indexing
- e.g. if there are two values and the index is just for checking they're unique with respect to each other
- you can just index on the value of that column without deserializing it at all
- Almost everyone I talked to at the summit was using AI
- But all but a few were using it in a very supporting role, not just spinning up a bunch of agents and sending them off
- Having 3 different places to store user metadata across two applications can be confusing
- And despite adding the third to solve this, it's not a perfect fit for what I'm trying to add now
Links
- Expansion Artifacts - Matt Stromawn
AI as lossy compression is an interesting perspective, and this is a well written take on it.
- SolidGoldMagikarp - LessWrong
A bunch of weird artifacts in ChatGPT 3 which lead to unexpected/sometimes hilarious output when you ask it about things like SolidGoldMagikarp or �.