There is no right answer. The only hard rule i have is that if it only requires key-value pairs keep it real simple. I use a variety of databases and things I can used as a database. One project uses Google sheets. Another uses a bunch of CSVs on a NAS as document oriented type database. And then there are the usuals; SQLite, MySQL, PostgreSQL, Mongo, and some god awful MS Azure crap that uses KQL.

I see a turtle.

“During the gold rush, sells shovels model” Is a perfect analogy. It worse, OpenAi and similar companies don’t find using any sluice machines profitable. It is basically a gold rush were even the big operations don’t want to be involved with anything, other than selling shovels. This bubble is going to burst and there is an unimaginable about of money invested if this scam.

Don’t. Unless you are confident you are not adding hot garbage to the code base.

I was in a long term relationship with someone with a drinking problem. When a drunk person says something to you they fucking mean it. Their filter is weaker and, as I label it “they have the courage to say something that they were afraid to say sober.” When you figure this out everything is easier to understand.

How does it go when you remove them from a fully pressurized tire? I have only ever removed cores when the tire was empty or had a low amount of pressure.

I don’t remember his music ever being cool or edgy. It was like drinking lacroix when soda is available.