17,243 karma · joined July 13, 2009
Should be more explicit though and users should be able to opt out.
To me KISS is basically about how you’d write the code, the architecture, which is something that - at least currently - humans need to oversee when writing new code with LLMs.
But what does it have to do with AI discovering a ton of bugs in a lot of (open-source) software?
Phrased differently, contracts are to concepts what assert is to static_assert.
Which would support your argument, but I don’t think this is particularly new.
I do believe this will force the AI labs to eventually solve the bloat problem with AI, but we’re definitely not there yet.
I think it’s simply a matter of dogfooding and new feature development, they do have much higher velocity than companies of equivalent size and an unlimited token budget helps as well.
SpaceX made that even more clear by doing an explicit offering of shares to raise money just months after their IPO, which didn’t raise them any money at all but was just for investors and employees.
Additionally, some ETFs have built in protections to rule out businesses that are not yet profitable (like SpaceX and Anthropic), which I think is a great rule.
Or at least those of some models, and I wouldn’t be surprised that an LLM model is able to understand correlations between weights and behavior better than humans could ever do.
What Apple does is, for example, being able to have a connection over WiFi and 5G simultaneously, with different IPs and routes.
The more traditional server side multipath is that you have a network card with 4 ports (eg 4x 25gbit) and connect them to a router, and make those 4 physical ports (paths) behave like a single interface. This helps either load balancing or redundancy.
The latter is what this vulnerability is about.