Agreed, it's not for production. For me, as an engineer, LLMs are a couple of things. One is they are killing the planet by consuming energy, dumping the smog into our communities and consuming the water we need to survive. The other way to see it is....uhh give me a funny ass picture of a cat driving a taxi with a donkey and a giraffe riding in the back...make it a 5 minute video.... probably uses way more resources than.... write a program that gives me network freedom, here are the specs.....

Once I get this initial bit and I study it, then I should be able to develop it like any other piece of software. It's that initial kick that helps a lot. In my experience, if you keep asking the LLM for more, your program will just suck ass more and more until you're left with nothing working. The other problem is it makes you lazy. Why should I debug if the LLM can do it?...debug this! But instead of a debug you get a full re-write and you don't know what changed.

So I hope they are using the LLM in a structured way. Remember, no matter what the LLM does, if you're not a programmer who would otherwise have understood the program enough to write it, you will still not understand it. Same for the cryptography.

But LLMs are basically a librarian who can parse thru many books and predict the next word or sentence. It's locally correct. So imagine using Google maps street view to drive your car. First you have to get the big thing...where are you at? Now, with no windows just a gps signal telling you how far you are, you turn left or right based on your own knowledge of where you want to go. Finally, you crash on obstacles like other cars, pedestrians and buildings. Each time you crash you can get out to see where you are and start again. That's LLMs in a nutshell. But if you finally get to where you wanted to go, you have a full program for anyone else to use. Lol