There was a professor who believed he could identify future programmers on day one. Twenty-five questions. Done. Sorted. That paper has since been retracted, which honestly tracks — but the question it raised is still sitting there, unanswered: are certain people just wired for this, or does spending years inside code rewire you? Tim and James had thoughts. Also, a story about a calculator catching fire.
Column A, Column B
The episode opened with Tim refusing to fully pick a side, which is his most programmer move. Natural aptitude is real, he said, but it’s not “good at math.” It’s something harder to name: a tolerance — maybe even a preference — for things being broken. The curiosity that kicks in where most people’s frustration kicks out.
James made a more specific claim. He can read Markdown. Like, just read it. Raw. No preview. The characters look right to him in a way that would make an ordinary person think something was corrupted. He wanted to know: is that aptitude, or is that years of staring at structured text slowly rewiring what his brain considers beautiful?
Tim’s answer was essentially semantic HTML. Which is not a non-answer — it’s actually a pretty good one. The argument that HTML should have structure, meaning, hierarchy — not just a pile of divs — is the same argument as “Markdown is correct.” And to be fair, Tim noted, the semantic HTML side mostly lost. Everything is still a div. But the instinct is the same: form should follow function, structure should be legible, and if your Microsoft Word document has headers that are just big bold text with no actual hierarchy, something has gone wrong in your life.
“If you have no structure in your content, do you even… I’m gonna eat dinner for breakfast. Like, how can you do that?”
The Kids Who Lit Up
Tim used to run a nonprofit teaching HTML, CSS, and JavaScript to kids six to ten. Twenty bucks to attend — not for profit, just enough to make sure people showed up. Here’s what he saw in those rooms, consistently: one group of kids who were absolutely not interested. Another group who were pleasant but clearly going to pursue other things. And a third group — smaller, unmistakable — who suddenly had seven hundred ideas and no patience to wait until they were old enough to build them. Those were the ones.
The tell wasn’t skill. It was the response to something not working. Frustration means you’re done. Curiosity means you’re just getting started.
His brother called him one night during a CSS tutorial, convinced the browser was broken. Tim walked him through the dev tools. The element was there — just floating somewhere inexplicable on the page. “Do you see the element highlighting?” “Why the hell is it all the way down there?” And then, after a pause: Is this what you do all day? You just figure out why none of this works?
Yeah. That’s the job. And some people hear that and think: finally, and other people hang up.
The Part Where Things Catch Fire
James asked Tim if he was the kid who took things apart.
Tim melted a calculator as a child. He spliced in the wrong power cord — a learning experience about voltage, delivered via smoke and melted plastic. He also melted an AMD Thunderbird CPU in his first computer by overclocking it without additional cooling. Smoke billowed out. CPU fused to the heatsink. He’d saved all summer for that machine.
“What’s the worst that can happen?” This is, Tim and James agreed, the actual prerequisite for this career. Not math skills. Not IQ. Just a genuine comfort with the possibility that your intervention could make things worse, paired with the conviction that you’re going to learn something either way.
James burned through some electronics himself before the internet existed. Pre-Google, you went to the library. You figured it out or you didn’t. Either way, you tried.
Would You Rather: The Mind Palace Edition
James zero-indexed the would you rathers. Tim noticed. Immediately. This was not acknowledged as a bit — it was acknowledged as a completely natural instinct that James had simply failed to suppress.
Round 0: Someone who says hello in Slack and waits for a response before asking their question — OR someone who sends fifteen one-line messages in rapid fire?
Tim sends fifteen one-line messages. Unrepentantly. His Slack is pure stream of consciousness, thoughts arriving as they occur, no consolidation, no mercy. He defended the hello, though — it originated with the telephone as a way to confirm the connection was live. He uses it as an availability check: I’m about to hit you with fifteen notifications, are you present? James pointed out that this is exactly what one message would also accomplish. Tim did not adjust his position.
Round 1: Explain recursion to your family every Thanksgiving — OR let them explain what they think the cloud is, to you?
Tim tells people he works in retail. He got away with this for years after moving to Columbus. Then his wife mentioned IT, and suddenly every neighbor needed a printer fixed. He now has an informal gentleman’s agreement with the pediatrician across the street: he handles her tech support, she handles his kid questions. This is the natural economy of professional expertise.
James would rather hear his non-technical family explain AI back to him. Not because it’s accurate. Because it’s revealing.
Round 2: A name with weird characters or multiple parts that breaks every online form — OR born on February 29th?
Tim’s custom email domain has been rejected by form validators that assume everyone uses Gmail or Yahoo. He sympathized. James’s middle initial has screwed up his TSA PreCheck because airlines keep attaching it to his first name. Both agreed: the name problem is daily, the birthday problem is only annually catastrophic — so you just put February 28th and move on.
James’s mother was born February 28th. His sister was born March 1st. Both on a leap year. The family theory: the hospital just changed them to make life easier. His father has a friend who, through an immigration paperwork error, has two official birthdays and has decided that celebrating twice is genuinely preferable to the bureaucratic ordeal of fixing it.
Round 3: Always know exactly why something broke, but be unable to fix it — OR have everything magically fix itself, with no idea why?
Tim pointed out that option two is most of human history. The eclipse happens. People do a ritual. The eclipse ends. The ritual worked. Repeat for ten thousand years. It’s a highly functional system until you realize the ritual is why you’re throwing people into volcanoes.
The episode ended with Tim’s formal fifty-year prediction: by 2027, we will be offering sacrifices for AI tokens. We won’t know why the model stopped responding. The model will fix itself. We will attribute it to the ritual.
James noted that “Claude is unhappy” was already funnier as a sentence than most things they’d said that day.
The Takeaway
Some people are wired for this. Others develop the wiring. The actual prerequisite isn’t math — it’s the specific personality trait that causes a twelve-year-old to splice the wrong power cord into a calculator out of pure curiosity about what happens next. If you find broken things interesting rather than just frustrating, you’re probably fine. If you need to understand the structure before you can read the document, you’re already thinking like a programmer. And if your inbox gets deleted by a batch script every night at midnight — that’s not disorder. That’s engineering.
Tim has not yet set anything on fire this year. The AMD Thunderbird CPU is not available for comment.