* emmanuel () has joined #2600
The channel goes quiet for a second.
Emmanuel Goldstein. THE Emmanuel Goldstein. Founder of 2600 magazine. The magazine that gives the channel its name. The guy who organizes the hacker conferences. Who writes about the philosophy of hacking, not just the tools.
This is like meeting royalty.
Emmanuel Goldstein is in the same channel as me. Typing on the same network.
He has no @ status. Just a regular user. But that doesn't matter—everyone knows who he is.
I do it without thinking.
* SKa sets mode: +o emmanuel
He notices. He says my name.
My hands are shaking.
Silence in the channel.
My face is hot.
The conversation moves on. Emmanuel and d3fkon talking about things I don't understand. Terms I've never heard.
Five minutes later:
* emmanuel has left #2600
I look up at the ceiling and shake my head.
My fingers hover over the keyboard. DEFCon. Las Vegas. August. The biggest hacker conference in the world. Where everyone from this channel will be. Where Emmanuel will probably speak.
Where a fourteen-year-old high school freshman absolutely cannot go.
They buy it. I hope.
---
During the programming class final, I'm still thinking about how stupid I looked in the Emmanuel conversation.
"SKa, you want to walk us through your solution?"
I look up. Mr. Caldwell is standing at the front, pointing to the problem on the projector. We were supposed to write a function that sorts an array.
I hadn't been paying attention.
"Uh..."
I glance at my screen. I'd finished the assignment twenty minutes ago. But I'd been staring at IRC, replaying the Emmanuel conversation, not listening to the class discussion.
"Never mind." Mr. Caldwell's voice is neutral. "Ankit, how about you?"
Ankit walks through his solution. It works, but it's inefficient—bubble sort instead of quicksort. Caldwell points this out gently, explains why algorithmic complexity matters.
I'm barely listening.
The bell rings. Everyone packs up.
"SKa, hang back a minute."
Everyone files out. The lab empties. Just me and Mr. Caldwell.
He closes the door to his small office and gestures for me to sit.
"What's going on?" he asks.
"Nothing. I'm fine."
"You finished the assignment in twelve minutes. Then you sat there staring at your screen for thirty minutes. That's not fine."
I don't say anything.
"You're one of the best students in this class," Caldwell continues. "Not because you memorize syntax. Because you actually think about how systems work. You ask good questions. You understand the why, not just the how."
He leans back in his chair.
If you spot this story on Amazon, know that it has been stolen. Report the violation.
"But today you were somewhere else entirely."
I look at my hands. "Just had a rough day yesterday."
"Want to talk about it?"
I can't tell him about Emmanuel Goldstein. Can't explain that I embarrassed myself in front of a hacker legend by pretending to know things I don't.
"Just... realized I don't know as much as I thought I did."
Caldwell nods slowly. "That's actually a good realization. Most people never get there. They just keep faking it."
I look up.
"There's a difference," he says, "between knowing facts and understanding systems. You can memorize a bunch of facts, but if you don't understand, you're just parroting."
My chest tightens. That's exactly what I did.
"The people who really know their stuff," Caldwell continues, "they think from first principles. They ask: What is this system trying to do? How does it actually work? What are the fundamental constraints? Then they build up from there."
"You know how to change a tire?" he asks.
I blink at the subject change. "Yeah." I don't. I'm full of shit.
"Why do you loosen the lug nuts before you jack up the car?"
I open my mouth. Close it.
I've never changed a tire, but I've seen people do it on TV. I know you're supposed to loosen them first. But I don't actually know why.
"Because once the wheel's off the ground, it spins," Caldwell says. "Can't get leverage. You'll strip the threads or break something trying. But if you just memorize the steps—loosen nuts, jack up car, remove wheel—you don't know that. And the first time you do it in the wrong order, you're stuck on the side of the road with a stripped lug nut and no way to fix it."
He leans forward.
"Shortcuts work until they don't. You can memorize steps, memorize commands, memorize what other people say works. But when you hit something new—something you haven't seen before—you're stuck. The people who understand why things work can figure out new problems. The people who memorized tricks just... stop."
I think about Emmanuel. The way he moved on when I tried to sound smart. Not because I was wrong about one fact. Because I clearly didn't understand what I was talking about.
"Yeah," I say quietly. "I see it."
"You're smart enough to do this the right way. Don't sell yourself short by faking it."
I sit there for a moment.
"How do I... how do I learn to think from first principles?"
"Start asking better questions. Not 'does this work?' but 'why does this work?' Not 'what's the command?' but 'what is this command actually doing?'" He stands up. "And when you don't know something—really don't know it—say so. Then go learn it properly."
I nod.
"You good?"
"Yeah. Thanks."
"Go on. You'll be late for your next class."
I walk out of his office.
The hallway is empty. Everyone's already in their next period.
---
That night, I still couldn't let it go.
I want to believe that. That it's fine not to know everything. That I can just focus on what I'm good at—channel operations, bots, IRC networks.
But Emmanuel isn't beholden to this IRC world. He's a legend.
I connect to #mp3 and #warez and start watching.