You mean the one I just downloaded and updated my laptop with? It installed OK.
I usually use MacOS and Linux, it's just that some software is Windows only, and I run MacOS on Apple Silicon - the windows program I needed only uses x86-64 architecture, so I can't use parallels (AFAIK).
I'm kind of hoping I get an update that bricks my laptop so I can install Debian over this MS Windows hellscape and run windows on a VM when needed. I may do it anyways after I get fed up with nagging MS messages and workarounds.
SQL is great. I've used it to implement knapsack optimization for Daily Fantasy Sports at scale. I use it in Big Data tools and RDBMS. It's pervasive in data tech.
Feel free to innovate and bring forth other RDBMS/Data query languages and tools, perhaps something may succeed and stick as long as SQL has.
Interesting. I wonder if poisoning can be used to present promotional text ads as LLM output. Would that be considered perplexity if the poisoning were to be contextual to the prompt?
Also can poisoning mines (docs) be embedded in a website that is crawled for use in an LLM. Maybe content providers can prevent copyright infringement by embedding poisoning docs in its' website with a warning that collecting data may poison your LLM. Making poisoning the new junkyard dog.
Interesting information that they chose modernc.org/sqlite over mattn/go-sqlite3 as a Quality-of-Life improvement. Going forward I guess I'll do the same for new projects.
The NATS Jetstream use case is something I'm curious about.
I wonder if there are any studies of professional chefs and their long-term health. I see video after video of chefs cooking in close proximity to oil cooked food, wood burning setups (BBQ), waiting for cooking oil to smoke, even smoking while cooking, etc.
If there should be a cohort that would be the canary in the coal mine, it would be professional chefs, who day-in and day-out cook for a living over several hours per day. Yet, I have not heard of any studies raising alarms for the profession.
Some excellent ideas presented in the article. It doesn't matter if they all pan out, just that they expand our thinking into the realm of AI and its role in the future of business startups and operations.
Revenue per employee, to me, is an aside that distracts from the ideas presented.
I did this with Claude over the holidays. Putting Claude in the role as a guesser and comparing the guess to another experience human player. It turns out they both matched each other.
I really enjoyed the introduction. Hopefully I can bring myself to read the rest of the paper, or as far as is reasonable for someone unfamiliar with the subject.
I use GnuCash for business accounting and it does what I need. I don't use QuickBooks as VC's recommend in blog posts. QB has some convenient features, but that is not enough for me to pay the price QB is asking. I don't need VC money or a CPA.
I haven't tried using GnuCash with Sqlite, but I would like to experiment when I get the time. Is it reliable?
I used to be a technical/functional engineer for Oracle EBS, so I dealt with very complex schemas that interlinked with each other especially in the sub-ledgers.
I've always toyed with the idea of adding Revenue Recognition functionality to GnuCash but am too busy to do so. Perhaps after seeing the schema in Sqlite I can take a shot at it.