Alive-in-2025
Joined 1 year ago
Joined 1 year ago
I'd also expect the offensive side of hacking into systems will greatly benefit from LLMs finding an almost endless series of new vulnerabilities in even crappier llm software. I'm just so cynical.
If one can't understand the monstrosity that was built up over time, where the code base is enormous, millions and millions of lines and components, all with a few buggy corners that the tests didn't touch, and a human didn't have the insight to write a test that understands and verifies the corner cases, it will be like a magic machine that we can't change because we don't understand it and we can't afford years of effort. Some may hope their LLM will be able to understand it.
We'll have things that are buggy in ways that become very difficult to understand or fix, and no one can afford the effort. Remember when we had all those huge old programs from the 60s or early 70s, before there were tests maybe, or unit tests. Code written at a lot of human effort, but before the ideas of software engineering made it more tractable to build large programs reliably, testable.
We are creating a new problem for the people that take over our new code, just like the "vast for the time" 1960s huge cobol program can't be changed.
In Washington State we have some of this happening too. A few years ago the long delayed projected to remove the damn on the Elwha on the Olympic Peninsula finally happened - https://en.wikipedia.org/wiki/Restoration_of_the_Elwha_River.
About half the country can't believe what's going on, 1/4 thinks he's all great somehow, 1/4 just wants to pretend everything is ok and they don't have to pay attention.
We are living the end of empire, like Nero metaphorically fiddling while Rome burned.
We kick the idiots out who are destroying the international systems at the behest of our idiocracy government in the us. See what they did to usaid. Also those same people love to complain about non-existent things, such as that vaccines are awful and hurt us (like Kennedy in the us).
Oregon has a deferral where the delayed property tax comes from the value of the house when it is sold or I guess when you die. https://grantsforseniors.org/property-tax-relief-for-seniors....
Washington has a similar thing.
"All Washington counties offer senior citizens and disabled households property tax exemptions. Eligibility is based on your age or disability status, home ownership, residency in Washington, and income level. Seniors who are at least age 61, or retired from regular gainful employment by reason of a disability, with an income of $64,000 or less are eligible."
The idea is to help people stay in their houses. This is really really important. And if you can afford it, you should be paying property taxes. I'm lucky I can afford mine, but I highly support this strategy.
In my state I occasionally see people in online discussions saying they can't afford their property taxes - I think a lot of people aren't aware of these programs, people are amazed when I post a few pointers and tell them about it.
With humans we break things down (proofs, new concepts) into digestible hunks for each other, because you want other people to understand them but also verify them. And it's less common for someone to build a tower of new intellectual things with 1,000 new connected ideas that prove things and build up together, that ends with P = NP after all or something.
So since we have these new tools that can chain things together more than we can, eventually there will be huge "proofs" where there are long chains of new ideas, concepts used to build up ever more in giant intellectual towers. And we can't verify/understand them, at least not for many many years.
I shudder to think of such a situation. We already have very important ideas that have no proofs, that people build on. Now build 100s of these things together.
Do you trust the result of your c++ program is correct? Because there are bugs in every compiler, language. You passed that million test correctness checker on the new version of the compiler, but it didn't catch everything.
When a bug is fixed, you don't immediately retry all existing results from your application program. Maybe you would if the bug was in some area you know was important and exercised by your code, say you were adding and multiplying numbers and bugs were found in that area.
The checker has a bug, the compiler the checker was testing had a bug, your own code that was compiled by the compiler had a bug probably. There can be bugs at any layer.