I’m treating this blog as future self-reference first. I consider keeping this digital garden well kept for myself will make it useful for others too.

I make use of RETURNING heavily when writing Postgres-based worker queues. It allows me to claim a job and immediately scan the returned row into a struct, unmarshall the payload based on the operation type, and dispatch it without a second round-trip to the database.

ThePrimeagen gloated about buying Micron stock when he learned that AI is very memory hungry, I didn’t really have my finger on the pulse to that degree.

As someone that appreciates digital sovereignty, moving back to thin clients is something I fear. We can play around in the FOSS inflatable pool, but unless we manage to open source fabbing our own silicon, it’s nothing more than LARP-ing as tech autarkists.

I own a Framework laptop, which is predicated on the idea of upgradability and repairabilty, but even they’ve stopped selling separate DDR5 modules

Also, Luke from LTT on RAM pricing:

1. DDR5 was mostly built with corporate clients in mind
2. A lot of manufacturers see the “bag” from selling to enterprise
3. Intel, Nvidia, etc. rerouting their capacity for enterprise instead of the consumer market
4. “Why deal with us annoying lowly people that don’t have money, when you can deal with the hyperscaler bros that have all of the money”

Get ready to bow down and sing praises to CXMT and YMTC (both Chinese manufacturers), cause they’re probably the only salvation you have for your homelab.

My second day without AI, it took me 4 hours to write a simple Express API

Most software engineering involves plumbing together the same 4 SaaS tools that corporate approved and negotiated contracts with. Most software engineers are mercenaries, typing away for cash. Most of the frustration software engineers face in the industry comes from the deadly impression that they’re actually artists.