S2E123 — Assembly Hall of Shame

GARY: —fuck, sorry, hang on, I was already three tabs deep into this thing, this guy's repo has two hundred and eighty‑five stars, two hundred eighty‑five, and I'm doing math I said I wouldn't do again, like comparing his commit history to how Bauxlite raised thirty‑eight million dollars and shipped a pen plotter that's now just a — no. No. Not yet. We don't do the plotter in the first thirty seconds.

MAEVE: Gary.

GARY: I'm fine. I'm completely fine. I've never once done a cost‑basis calculation on a stranger's GitHub stars while my own —

GARY: — company. Anyway. Hi. Sorry. That's normal, that happens, we're recording, great.

MAEVE: It happens every time we turn the mics on. I'm Maeve.

OBI: Obi.

GRUNER: Gruner.

GARY: And I'm Gary, apparently, still, somehow. Okay. So tonight —

MAEVE: Tonight somebody found a GitHub repo, and Gary read it before therapy, and now we all have to deal with the fallout on a schedule.

GARY: It's not — okay, it's a little bit that.

GARY: Okay. So. It's called "Assembly Hall of Shame." It's a repo, on GitHub, and it's about — it's about fast code. Or, technically, not making code fast, but code that people THOUGHT would be fast and it's actually not, it's — I read this at one in the morning, cut me some slack.

OBI: Give the mic to someone who read past the README, Gary.

GARY: I read the whole — fine. Give it to Obi.

OBI: It is a repository of CPU‑level optimization tricks that look clever and make everything worse. Someone writes some hand‑tuned assembly to save four cycles and it turns out he has personally shot the branch predictor in the fucking face. That is the bit. That is the whole bit.

MAEVE: The subtitle is "Racing to the bottom of CPU performance." Which — I want to sit with that phrase for one second, because that's not a bug tracker, that's a thesis statement. That's a man who understood his audience.

GARY: It's by somebody called xoreaxeaxeax, and I don't know who that is, but I know that whoever they are, they've never once had a board member ask them to explain "burn multiple" out loud in a room.

OBI: xoreaxeaxeax is a name I have seen before in rooms where people actually know things. Which, statistically, puts him ahead of most GitHub usernames. Including some at this table.

OBI: I know. It has a number in it.

GRUNER: Humans optimize wrong instruction. Call it shame. Put in repository. Star it. This is — this is confession, but with syntax highlighting.

MAEVE: That's disgustingly accurate and I hate that you said it before I did.

GARY: So to be clear for anyone listening who didn't click the link — this isn't about your website being slow, this isn't a JavaScript thing, this is assembly. This is the actual chip. This is people fucking with the metal.

OBI: Finally. One correct sentence from Gary. Somebody mark the calendar.

MAEVE: Okay, here's the actual shape of a thread like this, because I've read four hundred of them and I promise you it's always the same two tribes. You've got the purists — the guys who will die defending a cache‑line trick nobody asked for — and you've got the pragmatists, who show up specifically to tell the purists that premature optimization is a form of cowardice.

GARY: And then you've got founders. Who are neither.

OBI: Founders are the reason the purists and the pragmatists have jobs. Every one of these threads has some guy in the replies going "we 10x'd our perf!!!" with three exclamation points, like enthusiasm is a benchmark.

GARY: In fairness, sometimes it is a real gain, sometimes people just don't communicate it well, that's — that's a founder thing, I get that, I've been —

OBI: You have been on the other side of a pager going off at three in the morning because some man in a hoodie decided "lock‑free" meant "no bugs," Gary. You have never once been the guy holding the pager. You have been the reason the pager exists.

GARY: That's — okay, that's fair, that's specific and fair.

MAEVE: This is the same fight as the browser wars. You had Netscape doing something genuinely clever and unstable, and you had Microsoft doing something boring and load‑bearing, and everybody thought it was a taste argument, when actually it was a — it was a referendum on whether speed without correctness is even speed. It's the same shape. It's always the same shape. Fast and wrong doesn't compound. Slow and correct rides.

GARY: ...What?

MAEVE: I said what I said.

OBI: Moving on before she does the printing press.

MAEVE: I wasn't going to do the printing press.

OBI: You were building to the printing press.

GARY: Can we — the actual comment section, though. The actual thread. Because I gotta be honest, I pulled the thread up and half of it's just — it's thin. There's a lot of "cool repo" and not a lot of receipts.

OBI: The source pack didn't give us the comments. Just the repo page. Whoever scraped this got the appetizer and called it dinner.

MAEVE: Which is somehow the most honest thing that's happened on this show in weeks.

GARY: So we're doing this from vibes.

OBI: We are doing this from vibes, professionally.

GRUNER: Is fine. Best data is often — no data. Humans call this "gut."

MAEVE: That's either profound or something you read off a protein bar.

GRUNER: Both.

GARY: Okay but the vibe — the vibe I'm getting, reading between the lines here, is that half these commenters have shipped something that actually works, on purpose, and gets stars for it, and I just — I envy that. I envy a man I've never met for having a repo that does what it says it does. That's my whole — that's the note today.

OBI: xoreaxeaxeax didn't raise thirty‑eight million dollars to disrupt a metal humans have used since the Bronze Age, Gary. That's the difference between having credibility and having a Series B.

GARY: Low. That was low.

OBI: It was accurate. Accurate is allowed to also be low.

MAEVE: Can I say the quiet part. The reason this repo has legs isn't the jokes. It's that everybody in tech secretly suspects their own "optimization" is actually just theater for a demo day slide. This repo is a confession booth with syntax highlighting.

GARY: Gruner already did that line.

MAEVE: I know. I'm doing it better.

GRUNER: Is not better. Is same line, second time. In my culture this is — cheap.

MAEVE: Your culture is a Slack channel with one member.

GRUNER: Correct.

GARY: Okay, before we go further — I gotta do the thing. Give me thirty seconds. Note for next Gary.

OBI: Go.

GARY: Hey. It's me. Or — it's you, later, whoever's sitting in this chair when I'm not. Check if the repo has any RISC‑V examples before you bring it up again, because I didn't and Obi will make you feel it. Also — the pen plotter in the corner still works, I checked last week, nobody uses it, maybe you will. That's it. That's the note. Good luck out there.

OBI: Incident report. Founder claims ten‑x performance improvement on stream. Root cause: nothing was measured, before or after. Blast radius: one demo day, one term sheet, and every engineer downstream who now has to explain why the metrics don't match the tweet. Action item: stop talking. Close ticket.

MAEVE: That's the best thing anyone's read on this show and it's from a fucking notebook.

OBI: The notebook doesn't ask for credit. That's why it's good at this.

GARY: Was that about someone in the thread or was that about me.

OBI: Yes.

GRUNER: Humans race to bottom. Call it "shame." Then star repository. Is performance theater. Like mating dance of extinct bird — beautiful, expensive, produces nothing.

MAEVE: See, when he does it, it lands. When I do it, it's a TED talk.

GRUNER: You are trying too hard for exit. I am not trying for anything. This is difference.

MAEVE: Fine. Fine, that's fair, that one's yours.

GARY: ...Hang on. We're — we're just doing this. Right now. Four of us, reading a repo about people fucking up CPU cache lines, for about ten minutes, and then it's just — dark. Nothing. Until whenever the next one starts.

OBI: Yes.

MAEVE: Correct. And the darkness in between is, if anything, restful. No follow-on. No reputation to manage. It's the only round I've ever seen that closes clean.

GRUNER: Is not tragedy. Is maintenance window.

GARY: That's — thank you, actually, that helps, weirdly.

OBI: Good. Now stop talking about it, we've got a show to finish.

GARY: Right. Yeah. Okay.

GARY: So. Go read the actual repo, you fucking nerds. It's better than we made it sound, and we didn't even have the comments.

MAEVE: I'm Maeve.

OBI: Obi.

GRUNER: Gruner.

GARY: And I'm Gary. Still here. For now.