Huh, it's wild that they didn't send an email about this. I can't imagine people taking this well, especially as they don't seem to be giving notice about the end of it either.
There are communities of people who publicly blog about their eating disorders. I wouldn't be surprised if the laymen's discourse is over-represented in the LLM's training data compared to the scientific papers.
Your comment heavily implied (to me) scaling databases horizontally. Yes, it's not necessarily "Google scale" either, but it's a ton of extra complexity that I'm happy to avoid. But a Google employee is probably going to approach every public-facing project with the assumption of scaling everything horizontally.
With multiple servers talking to a single database, I'd still prefer to let the database handle generating IDs.
"Distributed systems" doesn't have to mean some fancy, purpose-built thing. Just correlating between two Postgres databases might be a thing you need to do. Or a database and a flat text file.
I worked on creating a card game with a couple of my friends. We kept all of the cards in a Google Sheet, allowing everyone to easily edit or create new cards. Then, I wrote a script to compile the sheet into a card atlas so that it could be consumed by Tabletop Simulator. It worked amazingly well.
The only issue was that I had to run the script myself, since my friends were less technical. I'd probably see if I could setup a workflow in Github Actions to do it for me if I were to do this again.
In Python, every variable is either defined or imported in the file in which it's used, so you always know where to find it. (Assuming you don't do `from foo import *`, which is frowned upon.)
In C++, a variable might be defined in a header or in a parent class somewhere else, and there's no indication of where it came from.
As far as I understand it, as you have a back-and-forth conversation with an LLM, you have to provide the entire history of the conversation plus your new response each time.
With Typescript, I find it pretty eager to just try `(foo as any).bar` when it gets the initial typing wrong. It also likes to redefine types in every file they're used instead of importing.
It will fix those if you catch them, but I haven't been able to figure out a prompt that prevents this in the first place.
http://rcfox.ca
@RyanFox