2,066 karma · joined December 30, 2015
My Epic Techno-Thriller/Sci-Fi/Mystery novels are free to download from my website rodyne.com
According to the cybergym benchmark in the article, Mythos is 83% of the way towards being perfect, not 100%, and there will still be holes in critical code after Mythos has done it's magic. Also, if Mythos can find exploits so can competing Cutting-edge AI models, some with nefarious actors.
A strategy for the next 12-24 months at least would be to assume ALL your systems will be compromised, move critical data to air-gapped backups, and never use the same system for browsing the web and for banking or other critical stuff.
I predicted similar scenarios in a sci-fi book I wrote a few years back, though we may have skipped the part where Mythos would be spending its first GPU cycles improving itself first :-)
Big fan of this project by the way.
A Proper self-contained, self improving AI@home with the AI as the OS is my end goal, I have a nice high spec but older laptop I am currently using as a sacrificial pawn experimenting with this, but there is a big gap in my knowledge and I'm still working through GPT2 level stuff, also resources are tight when you're retired. I guess someone will get there this year the way things are going, but I'm happy to have fun until then.
This is not a good time to be an indie author (I should know) writing the book is only the start of the journey, if you want people to now read it you have to fight a system dead set against your success. Word of mouth eventually gets you a few readers, or sales (thankfully) but there are plenty of really good indie authors out there, and you will never find them in the normal algorithms or book recommendation sites.
For me with any new release of my winery production software I re-ran every job put into my clients production systems from job #1, about 200,000 jobs; Before going into production we checked all the balances, product compositions and inventory from this new software matches what the old system currently says. Takes about an hour to re-run fifteen years production and even a milliliter, or milligram difference was enough to trigger a stop/check. We had an extensive set of input data I could also feed in, to ensure mistakes were caught there too.
I expect other people do it there own way, but as a business this would be the low bar of testing I would expect to be done.
Sitting in your cubical with your perfect set of test suites, code verification rules, SOP's and code reviews you wont want to hear this, but other companies will be gunning for your market; writing almost identical software to yours in the future from a series of prompts that generate the code they want fast, cheap, functionally identical, and quite possibly untested.
As AI gets more proficient and are given more autonomy (OpenClaw++) they will also generate directly executable binaries completely replacing the compiler, making it unreadable to a normal human, and may even do this without prompts.
The scenario is terrifying to professional software developers, but other people will do this regardless of what you think, and run it in production, and I expect we are months or just a few years away from this.
Source code of the future will be the complete series of prompts used to generate the software, another AI to verify it, and an extensive test suites.