Welcome to the first episode of Breaking the Build, a podcast that exists because two people in tech thought it would be more fun to talk about tech than to be professional about it. Tim wanted to make it. James is also here. His mom asked to be a guest. She did development for many years, and the Senior Center crowd in Morrisville, North Carolina remains an untapped podcast demographic.
No sponsors. No agenda beyond approximately 30 minutes of material. The iPad isn’t going to pay for itself, but they’re doing it anyway.
JavaScript Turns 30 (It’s a Millennial Now)
JavaScript was born in 1995, which makes it thirty years old and, per Tim, officially a millennial. Young millennial — not elder — though both Tim and James quietly identify as elder millennials at best.
The early history is weirder than most people remember. Netscape invented JavaScript. Microsoft, not wanting to be outdone, built their own version called JScript — a copy of JavaScript, but technically distinct enough to avoid intellectual property issues. This is also why, for years, front-end developers had to write separate code paths for each browser, sometimes beginning files with lengthy comment blocks specifying which browser hacks applied to which engine. And it was actually Microsoft that invented the DOM. Netscape had the BOM. These were different things, and forgetting that distinction could ruin your afternoon.
James started setting up the podcast recording software and discovered it refused to work with Firefox. “Your browser’s not compatible — please use Chrome.” He hadn’t seen a message like that since the IE days. He changed his user agent string and it worked fine, which he acknowledged might mean it isn’t recording properly. It was recording.
Tim misses one specific Internet Explorer bug where the CSS box model produced margins, padding, and borders at values like 9.99, 19.99, and 0.99 respectively. Nobody could explain it. Nobody could reproduce it on purpose. “You’ve broken it in a way you can’t figure out how it’s broken. And it was kind of beautiful.” This is a reasonable thing to feel nostalgic about.
The interview story: Tim once asked a developer candidate about their hardest technical challenge. The developer leaned in gravely and said: “Have you ever had to do HTML emails?” and began explaining table layouts as if delivering hard news. Tim had written CSS before CSS existed. He let the person finish.
TypeScript has now overtaken JavaScript in GitHub code volume, which some people are calling a major shift. James’s hot take: TypeScript is JavaScript. It’s a superset. You’re still writing JavaScript, just with a linter that makes you follow rules. Tim’s objection is more personal — duck typing was fun. If it walks like a duck and quacks like a duck, it’s a duck, and the interesting things you could do with that flexibility were genuinely enjoyable. TypeScript’s arrival was JavaScript finally getting a build job. A 401k. Dental.
The Space Shuttle Question
This came up naturally: JavaScript now runs everywhere — browser, server, database. Tim has always wanted to write JavaScript that launches an actual rocket. A space shuttle. Would you get in it?
James: no. Too many abstraction layers between the code and execution. Every step is another place something could go wrong.
Tim: would get in a hand-coded plain vanilla JavaScript space shuttle, written by someone who’s been doing this for thirty years. No compile step. No NPM. Just the code.
James’s counterpoint: he’d take the JavaScript space shuttle coded by hand over a C space shuttle that was entirely vibe-coded with AI. “At least someone looked at it.”
For the record, no one would get in the PHP space shuttle. The thruster is a plugin. The plugin costs $7 a year for the paid version. The free version gives you everything except the thrust.
The Apple space shuttle: clean lines. One button. All ports removed. Everything is Bluetooth. One small window.
AI: Brilliant or Frustratingly Incompetent?
James tried to make a birthday banner for his sister using AI. First prompt: a cartoon version of her at a hibachi table by a lake. The result was spectacular. Genuinely impressive. He was ready to frame it.
Prompt two: can you fix the spelling on “happy birthday” and remove the glasses, she doesn’t wear glasses?
The table disappeared. The lake became an ocean.
Twelve rounds later: the shirt color got changed to red and shrimp appeared to be flying through the air for reasons that were never explained. “By the twelfth time, I’m calling it the dumbest idiot I’ve ever worked with.” The banner never made it to the birthday.
Tim had a similar experience asking an AI to draw an elephant. It drew an elephant without tusks. He asked for two tusks. It gave the elephant four tusks. He asked for just two. It gave the elephant antlers.
“At that point I’m like, this is no longer saving me time. We are at an impasse.”
The more subtle version of this problem: AI will hallucinate method names in code. Close to the right name. Plausibly the right name. Wrong. If you’re not checking, you get some very confusing bugs. Tim’s metaphor: if you’ve never seen a shed before, buying a shed kit with a picture doesn’t guarantee you’ll understand why the two-by-fours shouldn’t sit directly on the ground. The kit helps. The foundational knowledge still matters.
James observed that AI competence is relative to the judge. Backend developers think AI is better at UI because they can’t evaluate the UI code critically. Frontend developers think AI is better at backend for the same reason. The people who actually know an area are more likely to catch where it falls short — which means the people most confident in AI’s output are often the least qualified to evaluate it.
The deeper thing, per Tim: AI behaves like a dad from thirty-five years ago, before Google. If a kid asked who invented gasoline, dad just said something. Confidently. “Greg. Greg invented gasoline.” AI does the same thing — it dislikes not having an answer, so it produces one, and it sounds certain. This is fine in the same way dads making things up was fine. It’s funny. You just shouldn’t navigate by it.
“It broke the magic of computers. We want our cold robots back.”
The Air Bud bit: if you could talk to dogs and discovered they lied constantly — not maliciously, just in the way a high schooler says “my uncle is Tony Hawk” — it would ruin dogs. You’d watch Air Bud and think: I bet that dog cheats.
Would You Rather: First Episode Edition
Round 1 (improvised live): Work with overconfident human coworkers OR overconfident AI, knowing both make a lot of mistakes?
Tim chose AI, immediately. His reasoning: when you tell overconfident AI it’s wrong, it says “you’re right, I’m so sorry, I’ll do better.” When you tell an overconfident human coworker they’re wrong, they explain why you’re mistaken using the same wrong information, more slowly, making eye contact. The AI has humility baked in.
James’s counterpoint: AI can be gaslighted into surrendering even when it’s right. Tell it it’s wrong enough times and it gives up. He wants something that occasionally pushes back when he’s the one who’s wrong.
Tim: “I need AI to literally respond, check yourself before you wreck yourself.”
Round 2: Spend 50% of your time doing code reviews with consistently bad code — OR work on a team where all productivity is measured in lines of code and story points?
Both chose code reviews. James admitted he “paraphrased” the metrics question in a way that made his answer obvious. Tim acknowledged that in thirty years he has never seen a system for measuring human performance that couldn’t be gamed, and no system that produced reliably good outcomes. If you want to look like an all-star by gaming story points, the tools are available. He still prefers the code reviews. At least someone’s learning something.
The Takeaway
JavaScript is thirty years old, has a build pipeline and dental coverage, and is now running on servers, in databases, and possibly in future space shuttles. AI can produce something genuinely impressive on the first try and something actively bizarre on the twelfth. Neither of these things has replaced the need to actually know what you’re doing. And the people most convinced that the technology is revolutionary are often the ones least equipped to notice when it isn’t.
Also: CSS Zen Garden was exciting. You had to be there.
Episode two is planned for two weeks out. Tim suggested recording it tomorrow. James was editing this one. It’s possible both happened.