Braiden Blog
do not disturb

Being a Student and a Founder at the Same Time

The honest version of juggling classes, client work, and running a couple of companies.

People sometimes ask me how I "do it all." I get why they ask. From the outside it probably looks like I've got some system figured out, a perfect calendar or a morning routine or a productivity app that does the heavy lifting.

The honest answer is that I don't do it all. Not at once, and definitely not all well. Some weeks the work gets my best hours. Some weeks school does. Most weeks, something gets whatever's left over at 11pm.

I figured it'd be worth writing down what this actually looks like, partly for anyone else trying to do the same thing, and partly so future me can look back and remember how chaotic this stretch was.

What's on the plate

On the school side, I've got a mix of classes that each want something different from me. There's my Tech Support Internship class, which is probably the one that lines up most with what I already do. There are papers, like a child development assessment I've been working through. There's a documentary project on child safety online that I'm doing solo, which means every part of it, from planning to the final cut, is on me. And college is coming up soon, which is its own whole thing.

On the other side, there's LatchID. That's the big one. I'm working toward a public release after Q2 2027, and building an identity platform is not the kind of project you can half-do. Auth has to work. If a login flow breaks, people can't get into the things they need. There's also my work with HeightNodes, and a pile of self-hosted services I keep running because I apparently enjoy being my own on-call rotation.

Until this fall, I was also making kettle corn at Richardson Adventure Farm. I handled making it and the operations side, like getting it stocked in stores. That was my last season, since I'm heading to college, and I'll be honest, I'm going to miss it more than I expected. There's something nice about a job where the work ends when you clock out.

The part nobody says out loud

You lose things. That's the part that doesn't show up in the "student founder" posts that make it look like a cool aesthetic.

Sleep is the obvious one, but it's not the only one. Some of my projects move a lot slower than I want them to. Ideas I'm genuinely excited about sit in a notes file for months because there's just no room for them yet. I've turned in assignments that were "done" instead of "good." I've shipped features that were the same.

There's also a weird mental cost to always having two lists running in your head. When I'm in class, part of my brain is thinking about something I need to fix. When I'm deep in code, part of my brain is remembering a paper that's due. It's hard to be fully present in either place, and that's something I'm still working on.

I used to feel guilty about all of this. Like if I were smarter or more disciplined, I'd be able to give both sides 100%. I don't really believe that anymore. You can't max out two big things at the same time. You pick which one gets the extra effort this week, and you try to be fair about it over the long run.

Deadlines are not all the same

The biggest thing that helped me was realizing that not every deadline is actually a deadline.

A paper due Friday can't move. A grade is a grade. A thing that's broken and affecting people can't wait either. But a refactor I want to do on my own code? That can wait. A new feature I'm excited about? That can wait. A blog post? (Hi.) That can definitely wait.

Most of the stress I used to feel came from treating everything like it was urgent. Once I started sorting things into "can't move" and "would be nice," the weeks got a lot more manageable. Not easy, but manageable.

The tricky part is that the "would be nice" pile is usually where the fun stuff lives. The new ideas, the side experiments, the things that made me want to build in the first place. So I try to give that pile some time when I can, even if it's just an hour on a weekend. If I let it go to zero for too long, I start resenting everything else.

The two sides feed each other more than I expected

I went into this thinking school and building things were basically competing for the same time. They are, but they also help each other in ways I didn't see coming.

Writing documentation is basically writing essays for people who'd rather not read them. You have to be clear, organized, and get to the point. That's helped my papers more than any writing tip from a teacher.

Going the other way, explaining things in class has made me better at explaining things in general. When I'm walking someone through how an auth flow works, it's not that different from explaining a concept to a classmate who's stuck. You figure out what they already know, start there, and build up.

My TSI class has honestly been a big part of why I want to teach. Helping someone get unstuck is one of the best feelings there is, whether it's a printer that won't connect or a concept that finally clicks. That class changed how I think about the support side of everything I build, too. Every confusing error message is a person on the other end getting frustrated.

Automate the boring stuff

My background is IT and DevOps, so I have a pretty low tolerance for doing the same thing by hand over and over. If I have to do something more than a couple of times, I'll script it, put it in a container, or hand it off to a cron job.

That's saved me more time than any calendar app ever has. Backups run on their own. Deploys don't need me babysitting them. Monitoring tells me when something's actually wrong, so I'm not checking things just to make myself feel better.

The same idea works for school, sort of. I can't automate an essay, but I can set up templates, keep notes organized in one place, and stop rebuilding my study setup from scratch every time. Every little bit of friction you remove is a little more energy for the stuff that actually needs it.

"Not right now" is not "no"

This one took me a while. I'm the kind of person who gets an idea and wants to start building it immediately. I've got a list of projects I want to make, from a ticketing system to a browser game where you play as an F1 race director. If I chased every one of them the second I thought of it, nothing would ever get finished.

So I've gotten better at saying "not right now." Writing the idea down, getting it out of my head, and letting it wait. It's not saying no forever. It's just saying it's not this semester's thing.

The weird bonus is that ideas usually get better when they sit for a while. By the time I come back to something, I've thought about it in the background, and I have a much clearer picture of what I actually want to build.

Taking breaks without feeling guilty

I'm still bad at this, so take it with a grain of salt. But the weeks where I push through with zero downtime are almost always the weeks where my work gets sloppy. I make dumb mistakes in code, I reread the same paragraph four times, and I get short with people.

Taking a night off, playing a game, watching a race, or just not looking at a screen for a bit isn't wasted time. It's what keeps the rest of the week from falling apart. I know that. I just don't always act like it.

Would I recommend it?

Kind of?

If you're a student and you want to build something, do it. You'll learn more from shipping one real project than from reading about a hundred of them. You'll learn how to deal with real users, real bugs, and real deadlines, and that stuff sticks with you.

Just go in knowing it's a trade, not a hack. There's no secret system that lets you do everything perfectly. Something is always giving a little. The trick is choosing what gives on purpose, instead of letting it happen by accident and wondering why you're burnt out.

And be honest with yourself about why you're doing it. If it's because you love building things, great, that'll carry you through the rough weeks. If it's because it looks cool, the rough weeks are going to feel a lot rougher.

What's next

I'm heading into college to study secondary education, with the goal of teaching history or science. So the balance is about to shift again, probably in ways I'm not ready for. New schedule, new workload, new everything.

I'll probably write a follow-up once I find out how badly I underestimated that.