> And that's the third issue with AI codebases: Humans don't understand them.
How many devs read the compiler output or care how understandable it actually is?
I know there are some (I am one of them), but TBH, how often does that happen?
The point I'm trying to make: LLMs have made actual code basically irrelevant in day-to-day dev work. Whether it is readable / understandable to humans matters very little.
The fact that it does what it should is what matters, and in that space, brand new techniques must be developed beyond the traditional ones to verify with a high degree of certainty that the code does what it's supposed to.
And yes, I am aware the the folks working on testing methodologies haven't been asleep at the wheel for the past 50 years.
What I'm saying is: with LLMs, it's all that remains: writing proper specs (assuming you know what you program should actually do), and proving the code produced by the LLM meets those specs.
The technical solutions we have for both these things are not yet, from a software engineering perspective, ready IMO.
> European RISC-V Industrial Computing Initiative
> Based in Europe, open worldwide
So European, right?
I'm immediately thinking: there's got to be some sort of sovereign aspect to the initiative ... right?
I mean, if there's one place you want a silicon stack that wasn't manufactured in China, it's most definitely in the guts of your industrial infrastructure (assuming you still have one, yes, point taken).
But, if you look at the "The silicon is here." section and dig a little:
The eProcessor TC1 is a RISC-V CPU with cores designed by Cortus (Mauguio, France) and fabricated in GlobalFoundries Dresden fab (22FDX). But that's a public initiative, not a private one.
I don't think so. The best you could find I think is some router with NXP or ST chips, but following the manufacturer you may or may not be able to do whatever you want with it.
Sadly we Europeans have taken our industry behind a shed and we put it out of its misery of having to pay exorbitant electricity prices and deal with our environmental regulations.
Good luck starting a fab in Europe... Maybe "hobby sized" attached to some university. But certainly not anything that can make parts in volume.
It used to be the case China competed mainly on price thanks to low labour costs. These days they still compete on price but because of supply chain integration.
If like me you dabble in hobby grade electronics you know how parts and services availability looks like here in Europe. We have only one component distributor now that UK left the EU. And even them (Mouser) if you try to order any advanced components that run at high frequencies etc tend to ship stuff from US warehouses.
Dont get me wrong. I'm still amazed they can get an order to me from US to Poland for $15 and 3-4 days time. But if I lived in China I could walk to one of bajillion physical suppliers and have every component made available same day. If I don't want to overspend on my prototype I could buy used parts without having to wait 3 weeks for delivery.
Then we have PCB manufacturing and assembly. It makes zero financial sense to use these services domestically. I'd love to support local EU industry, but I'm not spending 10x the cost for the privilege.
My take: unless they're a sovereign-backed team (North Korea, Russia, Iran, etc...the usual suspects) the hackers are very likely to get caught given:
a) The amounts stolen
b) The very poor uncensorability and anonymity guarantees offered by the kind of crypto they stole
Regarding uncensorability, some of these cryptos score so bad on that axis that the stolen goods can likely be recovered by a simple decision from the folks who manage/own the chain.
How many devs read the compiler output or care how understandable it actually is?
I know there are some (I am one of them), but TBH, how often does that happen?
The point I'm trying to make: LLMs have made actual code basically irrelevant in day-to-day dev work. Whether it is readable / understandable to humans matters very little.
The fact that it does what it should is what matters, and in that space, brand new techniques must be developed beyond the traditional ones to verify with a high degree of certainty that the code does what it's supposed to.
And yes, I am aware the the folks working on testing methodologies haven't been asleep at the wheel for the past 50 years.
What I'm saying is: with LLMs, it's all that remains: writing proper specs (assuming you know what you program should actually do), and proving the code produced by the LLM meets those specs.
The technical solutions we have for both these things are not yet, from a software engineering perspective, ready IMO.
reply