EW Elliot Williams Editor at Hackaday covering hardware hacks, electronics and maker projects.

“As a consumer of the code and as a human being who thinks of code not just as instructions for a machine, but a way to convey ideas about how to do things to other humans, I find this to be a real problem with the LLM code. On the other hand, in terms of how quickly it let people iterate on ideas and how fast it let them spin things up and play around with them… it was absolutely astounding.”

Hackaday Podcast · Hands-On Engineering Podcasts · November 2026

“As a consumer of the code and as a human being who thinks of code not just as instructions for a machine, but a way to convey ideas about how to do things to other humans, I find this to be a real problem with the LLM code. On the other hand, in terms of how quickly it let people iterate on ideas and how fast it let them spin things up and play around with them… it was absolutely astounding.” — Elliot Williams, Hackaday Podcast

Context

In the Supercon wrapup, Elliot says many badge hacks were vibe coded or heavily LLM-assisted. He weighs the cost to readability against how fast people could build things.

Transcript

Hackaday Podcast Around 1:08:38 into the episode
Elliot Williams

…engineering a human. You're reverse engineering something else that wrote the code. And so it's been a really wild ride. And sometimes I'd ask people, you know, hey, that's really cool. How'd you do that? And they're like, yeah, I don't know. JLM did it for me. Yes. And that is unsettling. And I

Tom Nardi

had that exact experience several times. They're like, well, I don't know. I don't know how it did it.

Elliot Williams

And as a consumer of the code and as a human being who thinks of code not just as instructions for a machine, but a way to convey ideas about how to do things to other humans, I find this to be a real problem with the LLM code. On the other hand, in terms of how quickly it let people iterate on ideas and how fast it let them spin things up and play around with them and find corners of the code base they wouldn't have found otherwise and et cetera, it was absolutely astounding. So, huh? I mean, I think I've just summarized where we all are right now. And I don't know that there's anything particularly deep here. I just had never been confronted with this before. And now I've seen it. And now I know what all y'all software people have been talking about the last year. Yeah,

Tom Nardi

it's hard to be mad, I guess, for lack of a better word, because it did enable such incredible stuff on a ridiculous time scale that was more obvious to us because we had just been banging our head against the wall for the preceding 48 hours trying to even get to where we were, you know? So to see…

Elliot Williams

readability? What's that?

Tom Nardi

Yeah. Like, and there was things that were like, I just could not understand what would possess the thing, but nothing possesses it, right? Like, that's the answer. Like, there's that, you're trying to find logic in something that doesn't operate on the same parameters as you do. It's not, its goal…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from Hackaday Podcast