I just started reading this and it’s freaking hilarious

Based on old memories since I’ve been working in mongo lately, after making the UDT on the db side, you make a data table that has the same name, namespace (ie dbo/public), and the same schema as the UDT (better if that could be generated) and populate it in code. Then you execute the db query with the UDT type as a parameter.

This is better for a few reasons, including not building up a string, but also having the same text means that each query didn’t need to be re-parsed and can reuse execution plans. If the query text isn’t an exact match, it gets that whole pipeline each time.

Create a user defined table type and use that as a parameter. I’m not sure what the postgres name of that is.

There’s a book titled “The High Cost of Free Parking”. Here’s an article about it

https://usa.streetsblog.org/2015/03/30/donald-shoup-an-appreciation#.VRyCepJPGEY.twitter

I got 10/28, but I was crying after the 7th question

🫡

I haven’t used that, but I did rent a pocket wifi while on a trip once. It worked really well.

You’d probably be better following the hashtag on mastodon

I edited the link bc I tried to cross post, but the original was removed. So in case it didn’t update, here’s the link.

https://english.elpais.com/technology/2025-06-03/the-covert-method-meta-uses-to-track-mobile-browsing-without-consent-even-in-incognito-mode-or-with-a-vpn.html

Business logic should go into its own services/functions. Combining all of these will make maintenance, changes, and testing a nightmare.

Keep your responsibilities segregated. Follow command/query responsibility separation.