900 karma · joined June 6, 2011
The writing SQL experience is a product of both SQL's syntax, the structure of the database you're querying over and the complexity of your query.
When things get hairy, and you have a good number of representative queries already written that you can use as context, LLMs can be really nice tool.
Now I can't trust that anything has been received unless I get an acknowledgement, so I have to keep pestering for replies. Basically lost trust in the protocol because it's dependent on the the other person's mailserver behaving they way you expect it to.
I'd love to see something like this for Typescript and Effect's SQL integration with schemas.
The kind of hoops I've had to jump through to achieve DIY idempotency with Postmark would make you cringe, a shared lock to avoid race conditions, and then using the API to check if an email with the unique id (manually added to the metadata when sending) has not already been sent before sending an email.
Being safe in the knowledge that an email with some unique key will only be delivered once regardless of bugs, processes dying mid task, network issues etc. just makes life so much simpler. The risk of sending duplicate emails or at worst spamming your users due to some more nefarious bug is something that you really want to guard against at as low a level as possible. Sure this might not be quite as consequential as duplicate charges through the Stripe API for example (Stripe have always seemed to lead the way with good API design in this regard).. doThing(data) is _not_ good enough for executing tasks over a network that are effectful, have a cost, and potentially risk your reputation if things go wrong. Idempotency keys should far more widely supported!
It really frustrates me that fantastic projects like this end up only being made available via some "online catalogue" with tiled zooming and no option to download.
Just stick it on the internet archive, and then voila, the data is actually open, everything gets automatically OCRed, and then we can do fun transformative things like the Internet Archive Book Images project..
https://www.flickr.com/photos/internetarchivebookimages/
https://ia804508.us.archive.org/21/items/vrr-texts-imageryof...
https://ia804508.us.archive.org/21/items/vrr-texts-imageryof...
https://react-spectrum.adobe.com/react-aria/Tooltip.html#exa...
The reason why magic links don't usually work across devices/browsers is to be sure that _whoever clicks the link_ is given access, and not necessarily whoever initiated the login process (who could be a bad actor)
What are you referencing?