She's 8 years old man cut her a little slack on the code aesthetics ;)

> A lot of code is being written and a lot of it is going to be a real future burden.

This assumes that the models of the future won't find it easier to just throw the code away and rebuild it

This also assumes that the same application build by humans wouldn't become a "spaghetti mess".

I wonder. I remember before emissions, what's underneath a car hood was relatively organized and simple. Then with emissions it became a maze of vacuum hoses and so much other nonsense.

then ... in some places (maybe cars that people care about working on) it became cleaner again. In the other places, they added a second hood to hide the mess.

There is some clean code out there, like maybe the seL4 kernel:

https://github.com/seL4/seL4/

https://en.wikipedia.org/wiki/SeL4

"with an explicit goal of enabling comprehensive formal verification..." (and lots more stuff)

maybe we can still have niches like this.

> Meanwhile, one peak at the code and you can already see the state starting to become a bit of a spaghetti mess.

That is how compiler-generated assembly looks to humans, as well. Human-produced is typically much more readable. Yet, here we are. Most programmers only know the very basics of assembly programming, but the world keeps spinning just fine.

Picking over the theoretical maintainability of one-off tools and toys that were generated in minutes by what will soon be an outdated model, feels very...missing the forest for the trees, when it comes to speculating about the future impact of this stuff.

That's the kind of thing I learned actual programming for, at the same age.

Yes but it’s far better than anything anyone, let alone a small child, could make in 15 minutes

On the other hand an engineer might take a couple hours and build this in a clean way with the right prompting

These “got ‘em” ai criticism comments are getting so old

[dead]