Braiden Blog
do not disturb

From help desk to classroom

A tech support internship class was supposed to make me better at fixing things. It ended up showing me I want to teach.

Most people who know me know me as the IT guy. I run my own servers, I build auth systems, I break things at 2 a.m. and fix them by 3. So when I tell people I'm going to college to major in secondary education, I usually get the same look: wait, not computer science?

Nope. And a big part of the reason is a class called TSI, the Tech Support Internship.

What TSI is supposed to be

On paper, TSI is about tech support. You learn to troubleshoot, deal with tickets, fix devices, and help people who are having a bad day with their technology. It's a hands-on, real-world class, and it's exactly the kind of thing I thought I'd love because it's what I already do.

And I do love it. But not for the reason I expected.

The part that isn't about the computer

Here's what nobody tells you about tech support: the computer is usually the easy part.

The hard part is the person. Someone walks up frustrated, a little embarrassed, and convinced they broke something. Fixing the problem takes five minutes. Making sure they leave understanding what happened, and feeling a little less scared of it, is the real job.

That's when it clicked for me. Every good support interaction is a tiny lesson:

  • Figure out what they already know. You don't explain DNS to someone who isn't sure what a browser is, and you don't talk down to someone who's already tried rebooting three times.
  • Explain it in their words, not yours. Jargon makes you sound smart and makes them feel dumb. Neither helps.
  • Let them do it. If I click the button, they learn nothing. If I walk them through clicking it, they can handle it next time.
  • Check for understanding. "Does that make sense?" doesn't count. "Okay, show me how you'd do it" does.
  • Be patient on the fortieth time. Every person asking is asking for the first time, even if you've heard the question all week.

Read that list again and replace "ticket" with "student." It's basically teaching.

The best fix is the one they can do themselves

In DevOps, the goal is to automate yourself out of a task. In support, the best tickets are the ones that never come back, because the person learned how to handle it.

That's what I want to do more of. I don't just want to fix someone's problem. I want them to understand it well enough that they don't need me next time. That's a teacher's whole job: making yourself a little less necessary every day.

Why not just stay in tech?

I'm not leaving tech. I don't think I could if I tried. LatchID and the rest of my projects aren't going anywhere.

But I've noticed that the moments I enjoy most aren't when I ship something. They're when I explain how something works and see it land: when someone goes from "I'm just bad with computers" to "oh, that's actually not that hard."

You can't automate that feeling. I want it to be my job.

What I want to bring to a classroom

Here's the twist for anyone expecting me to teach computers: I want to teach history or science.

That might sound like a left turn, but it isn't. Both subjects are about the same thing troubleshooting is about: asking why something happened. History is figuring out how we got here, which is basically reading the logs of the whole world. Science is forming a hypothesis, testing it, and changing your mind when the evidence says you're wrong, which is exactly what good debugging looks like. I'd much rather teach students how to think through a problem than which buttons to click.

I haven't settled on which one yet. But I know what kind of teacher I want to be, and a lot of it comes straight out of support work:

  • Treat confusion as normal, not as failure. Nobody walks into a help desk because they're doing great. Nobody walks into a classroom already knowing the material. That's the point.
  • Meet people where they are. Every student starts somewhere different. So does every ticket.
  • Show, then let them try. Hands on the keyboard beats a lecture almost every time.
  • Stay calm. If the person helping is stressed, everyone's stressed. If they're calm, the problem feels smaller.
  • Say "I don't know, let's find out." Faking an answer is worse than admitting you need to look it up. Students can tell, and so can users.

Where this goes

TSI started as a class about fixing technology. It ended up being the class that showed me what I actually want to do with my life.

College is next. I'll keep building, keep self-hosting, and keep breaking things at 2 a.m. But the long game is a history or science classroom, helping students get past "I can't" to "oh, I get it now."

More as it comes together.